Products > Test Equipment

Sniffing the Rigol's internal I2C bus

<< < (689/899) > >>

AndersAnd:

--- Quote from: studio25 on July 18, 2014, 05:22:11 pm ---
--- Quote from: aurel on July 17, 2014, 06:52:47 pm ---It would be nice if the persons handling http://gotroot.ca/rigol/riglol/ and http://riglol.3owl.com/ could update their online version.

--- End quote ---

I have http://riglol.3owl.com/ updatet. Thank you for your work.
--- End quote ---

--- Quote from: ve7xen on July 22, 2014, 04:30:57 am ---Great work! I have updated my mirror at http://gotroot.ca/rigol/ . The old version also remains for posterity.
--- End quote ---
Avotronics's UK mirror has been updated too.

Original made by studio25: http://riglol.3owl.com
Canadian mirror hosted by ve7xen: http://gotroot.ca/rigol/riglol/
UK mirror hosted by Avotronics: http://rigol.avotronics.co.uk/mirrors/riglol/

0xPIT:
Hi,

I'm new to the forum, thanks for your great work.

So I've got a new 2072A and I am currently trying to dump the beast,
I soldered a cable for my USB Blaster and started Dumping according to
post #2433, the Bfin is recognized nicely.

Dumping seems to work, but when it's finished, gdb spits out

--- Code: ---dump binary memory ~/sdram.bin 0x00000000 0x07FFFFFF
Ignoring packet error, continuing...
Reply contains invalid hex digit 116

--- End code ---

and even as the process takes hours and I can see gdbproxy's debug out
to iterate over the address space, no file is written.

I've already increased gdb's remotetimeout without any change.

As the BF-Toolchain was not available for Mac and did not compile on first try,
I used a current Ubuntu on my old Atom Netbook to do the dump.

Update:
Now also tried with same '116' problem on my MacBook Pro in a Ubuntu 14.04 VirtualBox.
I've even tried several toolchains and gdbproxy/gdb combinations

Update 2 (solved using workaround):
I managed to extract a dump and generate Keys using this workaround:
in gdb, I used
    set debug remote 1
and
    set remotelogfile /tmp/log

Then I started a new dump, which failed at the end with the stated '116' error, but all responses from the Blackfin were logged as ascii hexdump in the logfile.

I then awk'd the logfile to include only lines starting with +r $ and then removed this string using vi (:%s/^r\ +$//g)
Now I used xxd -p -r to convert the hexdump to binary and ran rigup on it, which worked fine.


Greetings,
  - pit

asgard20032:
Im about to buy a DS1074z or a MSO1074z (maybe the -s variant), but I want to know if anyone here successfully hacked the MSO one/

AndersAnd:

--- Quote from: asgard20032 on August 08, 2014, 03:04:37 pm ---Im about to buy a DS1074z or a MSO1074z (maybe the -s variant), but I want to know if anyone here successfully hacked the MSO one/

--- End quote ---
Same firmware. Makes no difference if it's DSO or MSO, or even S variant.

asgard20032:
Its because of that I ask :


--- Quote from: Loeti on July 24, 2014, 08:55:59 pm ---
--- Quote from: hematose on July 18, 2014, 01:56:05 pm ---Does anyone here know if the same upgrade codes are used for DS1000Z and MSO1000Z units? Would Riglol work for MSO1000Z?

--- End quote ---

Hello,

I got my MSO1104Z-S today. Even if the Rigol order codes for the options are the same for the DS1000Z and MSO1000Z series,
unfortunately Riglol doesn't work for the MSO1000Z at the moment. The firmware version of the MSO1000Z is also V04.00,
but there must be something different. Different private key, different option code or something like this. I've tried some other
option codes like "MSAB" instead of "DSAB", or "DSBB" or "DSHB" like other models use but I haven't succeeded yet.

Michael

--- End quote ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod