Author Topic: Sniffing the Rigol's internal I2C bus  (Read 1923962 times)

0 Members and 6 Guests are viewing this topic.

Offline m-joy

  • Contributor
  • Posts: 45
Re: Sniffing the Rigol's internal I2C bus
« Reply #2025 on: December 17, 2013, 06:02:11 pm »
Quote


 As soon as someone gets a dump of the firmware on the device of a DS2000A scope, it is very likely that the keygen will be modified to accommodate the newer model.


Maybe it will, maybe not...
 

Offline cybernet

  • Regular Contributor
  • *
  • Posts: 247
  • Country: 00
  • pm deactivated, use the search function ...
Re: Sniffing the Rigol's internal I2C bus
« Reply #2026 on: December 17, 2013, 06:57:30 pm »
___________________
"all rights reversed :-)"
R0=-0x18;
UNLINK;
RTS;
 

Offline barnacle2k

  • Regular Contributor
  • *
  • Posts: 53
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #2027 on: December 17, 2013, 09:20:54 pm »
You have more reading to do.  As soon as someone gets a dump of the firmware on the device of a DS2000A scope, it is very likely that the keygen will be modified to accommodate the newer model.

Just take the time and read this entire thread.  It will take a while, yes.  You will learn many things if you don't rush it.

Rigol DS2072A - check
FTDI JTAG thingy - check

Now if anyone could get me short instructions which SW and commands i should use.
Since i am not sure what exactly gets URJtag or gdb to create the dump you guys need.
 

Offline fcab100

  • Newbie
  • Posts: 7
Re: Sniffing the Rigol's internal I2C bus
« Reply #2028 on: December 17, 2013, 11:17:00 pm »
barnacle2k you have a DS2072A congrats on your new scope.  I was wondering if you could tell me what the jumper pins are set to on your scope.  Wanted to know if the its has changed.


Thanks Chris
 

Offline bobn4burton

  • Newbie
  • Posts: 7
Re: Sniffing the Rigol's internal I2C bus
« Reply #2029 on: December 18, 2013, 12:13:05 am »
So I just got my DS2102 and was preparing to use the keygen and unlock all options to get me to a DS2202.  I noticed that the 'all-options' code is now listed as DSHH??

I must have missed something in the last few weeks...but I believe the previous 'all-options' code was a DSAZ?

Which code should I be using to fully unlock my DS2102?

Also...most people are upgrading from a DS2072...I shouldn't  have any problems starting from a DS2102 should I?

Thanks in advance!
 

Offline fcab100

  • Newbie
  • Posts: 7
Re: Sniffing the Rigol's internal I2C bus
« Reply #2030 on: December 18, 2013, 12:25:14 am »
So I just got my DS2102 and was preparing to use the keygen and unlock all options to get me to a DS2202.  I noticed that the 'all-options' code is now listed as DSHH??

I must have missed something in the last few weeks...but I believe the previous 'all-options' code was a DSAZ?

Which code should I be using to fully unlock my DS2102?

Also...most people are upgrading from a DS2072...I shouldn't  have any problems starting from a DS2102 should I?

Thanks in advance!


Use DSHH as it unlocks 300mhz with can decoding  Make sure you have the latest fw update. The Fw (00.02.01.00.03) can be found at https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/
« Last Edit: December 18, 2013, 12:37:39 am by fcab100 »
 

Offline Bugware

  • Contributor
  • Posts: 20
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #2031 on: December 18, 2013, 12:28:18 am »
There is no problem to start from DS2102.

Use DSAZ for Firmware 00.01.01.00.02 to get 200MHz and all options.

Use DSHH for the brand new Firmware 00.02.01.00.03 (you can get it from  here but read careful) to get 300MHz and all Options incl. CAN capability.
 

Offline bobn4burton

  • Newbie
  • Posts: 7
Re: Sniffing the Rigol's internal I2C bus
« Reply #2032 on: December 18, 2013, 12:32:02 am »
WOW...apparently I did miss something!

We can upgrade to 300Mhz now???

Has this been verified to be truly 300Mhz capable?

Sorry if I'm re-hashing...just haven't had to time stay up to date on this thread the last few weeks and thought I better check in before updating.  And good thing I did...as we apparently got an even better upgrade than what I was planning...
 

Offline alank2

  • Super Contributor
  • ***
  • Posts: 2196
Re: Sniffing the Rigol's internal I2C bus
« Reply #2033 on: December 18, 2013, 12:36:37 am »
Why not DSGH ?  has anyone found out what the DSBA bit does yet?
 

Offline MrsR

  • Regular Contributor
  • *
  • Posts: 118
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #2034 on: December 18, 2013, 02:11:17 am »
Hi! Guys,
Can someone HELP me.
I went right back through the thread and found the instructions to update my DS2072 to 200mHz.
I had to upgrade my FW used the one on the site and tried to change the trigger and speed it up.
Unfortunately it didn't work Just got incorrect code  at the bottom of the screen on entering APPLY.

I have the memory updated to 56 megs purchased from EMONA before this thread started.
My Hardware Ver. is 1.000
and updated FW from 1.000.05 to 1.000.00.3 Zeros not accurately shown as I didn't copy it down from DSO.
CAN YOU HELP ME
Rachael
 

Offline MrsR

  • Regular Contributor
  • *
  • Posts: 118
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #2035 on: December 18, 2013, 02:24:39 am »
I forgot to add,
I lost my trial versions I don't know what I did but I didn.t use the scope for about a month and when I switched it back on the Trial versions came back The funny thing is I have used the scope for more than 2 hours and the trial version time hasn't changed started at 2032 and still at 2032.????????

THANKS
Rachael
 

Offline cidcorp

  • Supporter
  • ****
  • Posts: 105
  • Country: ca
Re: Sniffing the Rigol's internal I2C bus
« Reply #2036 on: December 18, 2013, 03:12:22 am »
Well I personally can't explain the suspended time trials, but I'm guessing if you are going to do a full unlock that this isn't going to be an issue.

I have a DS2102, all I did was upgrade to the new 00.02.01.00.03 firmware via the boot upgrade (ie. USB Key, Power, Help Key), not the process where the scope sees the newer firmware
on the USB key and asks if you want to upgrade.  Made sure to reset to factory settings during first boot with newer firmware using the Left F6 key (repetitively pushing during boot).  Then used the CAN & 300Mhz key codes generated by key generator (rigLOL website, you can link from here: http://rigol.avotronics.co.uk/mirrors/riglol/) to preserve the existing codes I already had (as with your 56M). 

To generate a key, simply add your serial number (for your scope) to the text box called serial: DS12345678901, then add the option you want a key for, let's say DSHH for all options, leave the private key box empty, then hit the GENERATE key - Use this key in the Options Setup Screen on the scope.

I 'assume' you can use the DSHH code with your Scopes serial and be up and running with all the options without having any effect on the 56M option. 

Just my 0.02

Chris
« Last Edit: December 18, 2013, 03:20:50 am by cidcorp »
 

Offline staze

  • Frequent Contributor
  • **
  • Posts: 820
  • Country: us
  • I _might_ have a problem...
    • Everybody Staze...
Re: Sniffing the Rigol's internal I2C bus
« Reply #2037 on: December 18, 2013, 04:29:12 am »
Okay, just upgrade my formerly 2072->2202 to the 2302 via uninstall, then clear FRAM, upgrade (via help), clear FRAM, install new key.

One thing interesting... I'm seeing weird "glitches" with the 1ns timebase, where it will show persistence, but then every once half second (or less) flick to no persistence for a frame or two, then back to persistence.

Scope is HW2, non-A. Key seemed to work just great. And now that I look at it, several of the timebases are showing this behavior. Looks like it might just be a function of the lower persistence times. Is that what others see? What do others leave their's at normally?
“Give a man an answer, he’ll keep his job for a day. Teach a man to Google, and he’ll be employed for a lifetime”
 

Offline tlu

  • Regular Contributor
  • *
  • Posts: 145
Re: Sniffing the Rigol's internal I2C bus
« Reply #2038 on: December 18, 2013, 05:07:52 am »
I was have Marmad check it out and send it to Drieg as a bug if this is really the case.
 

Offline MrsR

  • Regular Contributor
  • *
  • Posts: 118
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #2039 on: December 18, 2013, 06:00:49 am »
Well I personally can't explain the suspended time trials, but I'm guessing if you are going to do a full unlock that this isn't going to be an issue.

I have a DS2102, all I did was upgrade to the new 00.02.01.00.03 firmware via the boot upgrade (ie. USB Key, Power, Help Key), not the process where the scope sees the newer firmware
on the USB key and asks if you want to upgrade.  Made sure to reset to factory settings during first boot with newer firmware using the Left F6 key (repetitively pushing during boot).  Then used the CAN & 300Mhz key codes generated by key generator (rigLOL website, you can link from here: http://rigol.avotronics.co.uk/mirrors/riglol/) to preserve the existing codes I already had (as with your 56M). 

To generate a key, simply add your serial number (for your scope) to the text box called serial: DS12345678901, then add the option you want a key for, let's say DSHH for all options, leave the private key box empty, then hit the GENERATE key - Use this key in the Options Setup Screen on the scope.

I 'assume' you can use the DSHH code with your Scopes serial and be up and running with all the options without having any effect on the 56M option. 

Just my 0.02

Chris

Thanks Chris, Could you tell me where I can get a copy of the FW 00.02.01.00.03.

Rachael :-+
 

Offline staze

  • Frequent Contributor
  • **
  • Posts: 820
  • Country: us
  • I _might_ have a problem...
    • Everybody Staze...
Re: Sniffing the Rigol's internal I2C bus
« Reply #2040 on: December 18, 2013, 06:03:40 am »
“Give a man an answer, he’ll keep his job for a day. Teach a man to Google, and he’ll be employed for a lifetime”
 

Offline bobn4burton

  • Newbie
  • Posts: 7
Re: Sniffing the Rigol's internal I2C bus
« Reply #2041 on: December 18, 2013, 06:21:06 am »
Just updated my DS2102 to the all option DSHH!

Couldn't have been easier...

A HUGE thanks again to all the effort put in from everyone on here.

Now off to enjoy some advanced triggering!!!
 

Offline darrylp

  • Regular Contributor
  • *
  • Posts: 127
  • Country: gb
Re: Sniffing the Rigol's internal I2C bus
« Reply #2042 on: December 18, 2013, 05:49:36 pm »
can confirm, had left my upgraded 2072 as 2202, updated to the version 2.x.x.x firmware ( did the F6 to clear FRAM on bootup ) was then able to still see my 2202, and apply the 300MHz and CAN option, to turn those features on as well

so i'd say no need to uninstall any keys already applied on an older firmware.
 

Offline manticore00

  • Regular Contributor
  • *
  • Posts: 52
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #2043 on: December 18, 2013, 06:26:58 pm »
Just upgraded my DS2072 with the DS2202 options up to the 300MHz and CAN option as well, went perfectly and had zero issues.
Aut viam inveniam aut faciam
 

Offline cyr

  • Frequent Contributor
  • **
  • Posts: 252
  • Country: se
Re: Sniffing the Rigol's internal I2C bus
« Reply #2044 on: December 18, 2013, 08:14:46 pm »
download, rename to DS4000Update.GEL -> http://www.filedropper.com/ds405xupdate

This download seems to be broken, anyone have a mirror?

I have had my DS4014 for several hours already, it desperately needs some unauthorized modification  :)
 

Offline AndersAnd

  • Frequent Contributor
  • **
  • Posts: 572
  • Country: dk
Re: Sniffing the Rigol's internal I2C bus
« Reply #2045 on: December 19, 2013, 01:24:58 am »
You have more reading to do.  As soon as someone gets a dump of the firmware on the device of a DS2000A scope, it is very likely that the keygen will be modified to accommodate the newer model.

Just take the time and read this entire thread.  It will take a while, yes.  You will learn many things if you don't rush it.

Rigol DS2072A - check
FTDI JTAG thingy - check

Now if anyone could get me short instructions which SW and commands i should use.
Since i am not sure what exactly gets URJtag or gdb to create the dump you guys need.
Try to PM cybernet and ask for instructions.
 

Offline barnacle2k

  • Regular Contributor
  • *
  • Posts: 53
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #2046 on: December 19, 2013, 01:39:22 am »
You have more reading to do.  As soon as someone gets a dump of the firmware on the device of a DS2000A scope, it is very likely that the keygen will be modified to accommodate the newer model.

Just take the time and read this entire thread.  It will take a while, yes.  You will learn many things if you don't rush it.

Rigol DS2072A - check
FTDI JTAG thingy - check

Now if anyone could get me short instructions which SW and commands i should use.
Since i am not sure what exactly gets URJtag or gdb to create the dump you guys need.
Try to PM cybernet and ask for instructions.

Quote from: cybernet's profile
pm deactivated, use the search function ...

I know how to setup and connect urjtag or gdb but i would need some info on the rest of the process.
« Last Edit: December 19, 2013, 01:42:18 am by barnacle2k »
 

Offline cybernet

  • Regular Contributor
  • *
  • Posts: 247
  • Country: 00
  • pm deactivated, use the search function ...
Re: Sniffing the Rigol's internal I2C bus
« Reply #2047 on: December 19, 2013, 02:39:58 am »
use the gdb bfin proxy from bfin uclinux

when u have patched it up (see DG4000 thread, first few posts) - its the same pinout.

start with something like:
Code: [Select]
./bfin-gdbproxy --debug bfin --frequency=6000000(lower frequency might be needed, i kept it very short in terms of cablelength to get 6mhz)

then use the bfin-gdb - connect to remote target (e.g. target remote localhost:2000)
and u should be able to do what u want.

stuff thats needed:
one dump when its sitting in the bootloader (as the booted application image overwrites stuff in RAM)
and one dump when its booted up - it helps if u do that dump once u entered a easy to find license key ala "AAAAAAAAAAA..."

check http://www.analog.com/static/imported-files/processor_manuals/ADSP-BF52x_hwr_rev1.2.pdf page 115&116 - memory map, and dump everything thats listed there with gdb dump ... as binary.
« Last Edit: December 19, 2013, 02:43:49 am by cybernet »
___________________
"all rights reversed :-)"
R0=-0x18;
UNLINK;
RTS;
 

Offline tirulerbach

  • Contributor
  • Posts: 33
Re: Sniffing the Rigol's internal I2C bus
« Reply #2048 on: December 19, 2013, 06:32:24 pm »
Before the keygens or the ATtiny85 hack, the way that many of us owners were getting around the problem of expired options was by using a clock reset/self-cal exploit to restart the trial minutes.

[...]

Manual:

Make sure System -> Startup is Default.
Set the clock to 2099, 31 Dec, and 23:58 hour.
Wait a few minutes for the clock to rollover past 00:00 (you can see it in the normal screen at the bottom right),
Put the clock back to the correct date and time.
Reboot
Wait at least 30 minutes for warm-up, then do a self-calibration.
After the scope is finished, it will reboot once.
Make sure System -> Startup is Default.

Then you just have to wait for awhile. The options will come back sometime when you boot up between ~3 to 60 hours later.

This procedure didn't worked for my DS2202_A_. However, I noticed it lost somehow its calibration when the date rolled over. But the trial licences are not reset.

So maybe I made a fault?

However, it would be nice, if a non-A-owner will remove his keys and try this procedure with the newest firmware (which is for both scopes, "a" and "non-a") to check if it still works. Because smashing the trial minutes only to check that the trick will not work for "a"-scopes is a waste...


 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #2049 on: December 19, 2013, 06:57:53 pm »
This procedure didn't worked for my DS2202_A_. However, I noticed it lost somehow its calibration when the date rolled over. But the trial licences are not reset.

It lost it's calibration after you did a self-calibration? Because that's the next step after the date rolls over and you reset the time.

Also, have you waited ~3 days?

Because smashing the trial minutes only to check that the trick will not work for "a"-scopes is a waste...

It would be silly to do it at all until the trial minutes are finished - and you want more trial minutes. Then nothing is lost/wasted either way.
« Last Edit: December 19, 2013, 07:00:55 pm by marmad »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf