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

0 Members and 3 Guests are viewing this topic.

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3400 on: July 09, 2014, 07:55:44 am »
Thank you, Teneyes. From the link you provided, it looks like FW#00.03.00.01.03 is the latest version. Is this version compatible with the keys generated by Riglol, or do I need to use an older version of the firmware for that?
for me  FW#00.03.00.01.03 installed and keeps the options that were installed before, and allows  'CAN'

Ok, so sounds like a safe method would be to uninstall the option keys, generate new keys using the correct option code, install those keys, upgrade the firmware, and do the post-update settings reset mentioned in the post you linked?
 

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3401 on: July 09, 2014, 08:30:49 am »
Thank you, Teneyes. From the link you provided, it looks like FW#00.03.00.01.03 is the latest version. Is this version compatible with the keys generated by Riglol, or do I need to use an older version of the firmware for that?
for me  FW#00.03.00.01.03 installed and keeps the options that were installed before, and allows  'CAN'

Ok, so sounds like a safe method would be to uninstall the option keys, generate new keys using the correct option code, install those keys, upgrade the firmware, and do the post-update settings reset mentioned in the post you linked?

Disregard my last question - I did exactly what I said there, and it is running the latest firmware with the options enabled. Unfortunately, I noticed that it locked up already once (in the System/Info screen, it locked up and wouldn't exit this). I am now wondering if there is some actual hardware issue with my scope...

In any event, thank you for your help.
 

Offline ted572

  • Frequent Contributor
  • **
  • Posts: 399
  • Country: us
  • Radio Communications Equipment/System Design Engr.
Re: Sniffing the Rigol's internal I2C bus
« Reply #3402 on: July 09, 2014, 10:58:49 am »
Re. Post #3442 by 'motocoder':

Disregard my last question - I did exactly what I said there, and it is running the latest firmware with the options enabled. Unfortunately, I noticed that it locked up already once (in the System/Info screen, it locked up and wouldn't exit this). I am now wondering if there is some actual hardware issue with my scope...

In any event, thank you for your help.
[/quote]
---------------------------------------------------------------------------------------------------------------------
Reply from 'Ted572' for 'motocoder'

My recommendation....

1. Your DS2000 settings should be set for Power = 'Default', NOT 'Last'.  This way when you have a lockup, etc. and you reboot (Power cycle Off/On) your issue will be cleared.  Otherwise you can end up in a endless loop of unsuccessful reboots.
2. Clear the DS2000's FRAM to be sue this isn't an issue.  To do this:  Press and hold down the left-hand side F6 key during a reboot.
3. Do Not use the 300MHz BW Option!  If you have it selected for a DS2000 non A (it is OK for the DS2000A) get rid of it.  Uninstall All Options with UltraSigma and then add them back in without 300MHz BW.  If you are not sure how to do this please feel free to ask me for a procedure.

      Regards, Ted572.

Edit: Changed from F7 (wrong) to F6 (correct) in item 2. above.
« Last Edit: July 10, 2014, 11:24:01 am by ted572 »
 

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3403 on: July 10, 2014, 02:02:01 am »
Re. Post #3442 by 'motocoder':

Disregard my last question - I did exactly what I said there, and it is running the latest firmware with the options enabled. Unfortunately, I noticed that it locked up already once (in the System/Info screen, it locked up and wouldn't exit this). I am now wondering if there is some actual hardware issue with my scope...

In any event, thank you for your help.
---------------------------------------------------------------------------------------------------------------------
Reply from 'Ted572' for 'motocoder'

My recommendation....

1. Your DS2000 settings should be set for Power = 'Default', NOT 'Last'.  This way when you have a lockup, etc. and you reboot (Power cycle Off/On) your issue will be cleared.  Otherwise you can end up in a endless loop of unsuccessful reboots.
2. Clear the DS2000's FRAM to be sue this isn't an issue.  To do this:  Press and hold down the left-hand side F7 key during a reboot.
3. Do Not use the 300MHz BW Option!  If you have it selected for a DS2000 non A (it is OK for the DS2000A) get rid of it.  Uninstall All Options with UltraSigma and then add them back in without 300MHz BW.  If you are not sure how to do this please feel free to ask me for a procedure.

      Regards, Ted572.
[/quote]

Thanks, Ted. Did you mean to say clear FRAM by holding the F6 key during boot, or is it actually F7? The instructions that Teneyes linked to above say F6. I didn't notice any messages about clearing FRAM - does it do anything to indicate that's actually happened?

Regarding the 300MHz BW option, I do indeed have that enabled. I even forked over some money for the 300MHz probes, so it is very disappointing to learn that it causes issues...
 

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3404 on: July 10, 2014, 02:09:27 am »
Re. Post #3442 by 'motocoder':

Disregard my last question - I did exactly what I said there, and it is running the latest firmware with the options enabled. Unfortunately, I noticed that it locked up already once (in the System/Info screen, it locked up and wouldn't exit this). I am now wondering if there is some actual hardware issue with my scope...

In any event, thank you for your help.
---------------------------------------------------------------------------------------------------------------------
Reply from 'Ted572' for 'motocoder'

My recommendation....

1. Your DS2000 settings should be set for Power = 'Default', NOT 'Last'.  This way when you have a lockup, etc. and you reboot (Power cycle Off/On) your issue will be cleared.  Otherwise you can end up in a endless loop of unsuccessful reboots.
2. Clear the DS2000's FRAM to be sue this isn't an issue.  To do this:  Press and hold down the left-hand side F7 key during a reboot.
3. Do Not use the 300MHz BW Option!  If you have it selected for a DS2000 non A (it is OK for the DS2000A) get rid of it.  Uninstall All Options with UltraSigma and then add them back in without 300MHz BW.  If you are not sure how to do this please feel free to ask me for a procedure.

      Regards, Ted572.
[/quote]

Also, what is the option code for all options except 300MHz? I used "DSHH" last time, which is all options AND 300 MHz.
 

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3405 on: July 10, 2014, 02:12:31 am »
I uninstalled all options, and was re-entering a code. It locked up while entering the code! So seems my lock-ups are not related to the 300 MHz option...
 

Offline Sparky

  • Frequent Contributor
  • **
  • Posts: 450
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3406 on: July 10, 2014, 04:33:59 am »
Is the DP832 firmware 00.09.01 still un-hackable at this stage?

Sort of correct; the latest firmware is actually 00.01.09.00.01 (date 12/27/2013) and bootloader 01.06 (date 12/27/2013).

Yes, still un-hackable. (No further investigation that I'm aware of since the original hack.)
 

Offline josem

  • Regular Contributor
  • *
  • Posts: 63
  • Country: gb
Re: Sniffing the Rigol's internal I2C bus
« Reply #3407 on: July 10, 2014, 06:36:37 am »
Is the DP832 firmware 00.09.01 still un-hackable at this stage?

Sort of correct; the latest firmware is actually 00.01.09.00.01 (date 12/27/2013) and bootloader 01.06 (date 12/27/2013).

Telonic in the UK and already listing 00.01.10 as the latest firmware for the DP832.

http://www.rigol-uk.co.uk/ProductDetails.asp?ProductCode=FIRMTEST#.U74xXq5QZ3s

Not sure if this is 100% accurate and what changes it would include...
 

Offline ted572

  • Frequent Contributor
  • **
  • Posts: 399
  • Country: us
  • Radio Communications Equipment/System Design Engr.
Re: Sniffing the Rigol's internal I2C bus
« Reply #3408 on: July 10, 2014, 11:30:34 am »
Re. Post #3442 by 'motocoder':

Thanks, Ted. Did you mean to say clear FRAM by holding the F6 key during boot, or is it actually F7? The instructions that Teneyes linked to above say F6. I didn't notice any messages about clearing FRAM - does it do anything to indicate that's actually happened?

Regarding the 300MHz BW option, I do indeed have that enabled. I even forked over some money for the 300MHz probes, so it is very disappointing to learn that it causes issues...

Yes, you are correct the Clear FRAM key is F6 (not F7).  I'm sorry for the error, and thank you for catching it.  I also edited my information above with the correct key reference.
 

Offline Rigby

  • Super Contributor
  • ***
  • Posts: 1476
  • Country: us
  • Learning, very new at this. Righteous Asshole, too
Re: Sniffing the Rigol's internal I2C bus
« Reply #3409 on: July 10, 2014, 01:15:26 pm »
Is the DP832 firmware 00.09.01 still un-hackable at this stage?

Sort of correct; the latest firmware is actually 00.01.09.00.01 (date 12/27/2013) and bootloader 01.06 (date 12/27/2013).

Telonic in the UK and already listing 00.01.10 as the latest firmware for the DP832.

http://www.rigol-uk.co.uk/ProductDetails.asp?ProductCode=FIRMTEST#.U74xXq5QZ3s

Not sure if this is 100% accurate and what changes it would include...

Until there is a very good reason to upgrade, I don't think upgrading would be a great idea.
 

Offline marmad

  • Super Contributor
  • ***
  • Posts: 2979
  • Country: aq
    • DaysAlive
Re: Sniffing the Rigol's internal I2C bus
« Reply #3410 on: July 10, 2014, 01:49:03 pm »
3. Do Not use the 300MHz BW Option!  If you have it selected for a DS2000 non A (it is OK for the DS2000A) get rid of it.  Uninstall All Options with UltraSigma and then add them back in without 300MHz BW.  If you are not sure how to do this please feel free to ask me for a procedure.

To clarify some things:

First of all - in respect to using the "300MHz" BW option - it makes NO difference if you have a DS2000 or DS/MSO2000A - other than you have the 50 ohm input impedance choice. Aside from that, as far as I've seen, Rigol did not make any major changes to the front-end.

Secondly, to all the people who believe they are magically getting a perfectly-capable "300MHz" DSO just because they put in some option codes: look at all the DSO models from highly-respected test-equipment manufacturers (Agilent, Hameg, Tektronix, etc) - do you see any 2GSa/s DSOs with a higher than 200MHz BW? No, you don't - because there are mathematical reasons why it doesn't really work well. Rigol (and the other Chinese companies) have not invented some new wonderful method for squeezing more BW out of less sample rate - they are, in fact, delivering DSOs that will have problems reproducing those kind of BW waveforms accurately at certain settings (i.e. both channels on) - period.

As long as you understand these problems, fine. But again: they are identical for both DS2000 and DS2000A - it doesn't matter which model you have.
« Last Edit: July 10, 2014, 02:35:08 pm by marmad »
 

Offline ted572

  • Frequent Contributor
  • **
  • Posts: 399
  • Country: us
  • Radio Communications Equipment/System Design Engr.
Re: Sniffing the Rigol's internal I2C bus
« Reply #3411 on: July 10, 2014, 02:54:17 pm »
Re. Post #3442 by 'motocoder':

Disregard my last question - I did exactly what I said there, and it is running the latest firmware with the options enabled. Unfortunately, I noticed that it locked up already once (in the System/Info screen, it locked up and wouldn't exit this). I am now wondering if there is some actual hardware issue with my scope...

In any event, thank you for your help.
---------------------------------------------------------------------------------------------------------------------
Reply from 'Ted572' for 'motocoder'

My recommendation....

1. Your DS2000 settings should be set for Power = 'Default', NOT 'Last'.  This way when you have a lockup, etc. and you reboot (Power cycle Off/On) your issue will be cleared.  Otherwise you can end up in a endless loop of unsuccessful reboots.
2. Clear the DS2000's FRAM to be sue this isn't an issue.  To do this:  Press and hold down the left-hand side F7 key during a reboot.
3. Do Not use the 300MHz BW Option!  If you have it selected for a DS2000 non A (it is OK for the DS2000A) get rid of it.  Uninstall All Options with UltraSigma and then add them back in without 300MHz BW.  If you are not sure how to do this please feel free to ask me for a procedure.

      Regards, Ted572.

Thanks, Ted. Did you mean to say clear FRAM by holding the F6 key during boot, or is it actually F7? The instructions that Teneyes linked to above say F6. I didn't notice any messages about clearing FRAM - does it do anything to indicate that's actually happened?

Regarding the 300MHz BW option, I do indeed have that enabled. I even forked over some money for the 300MHz probes, so it is very disappointing to learn that it causes issues...
[/quote]

Reply rfom Ted572:

Apparently 300MHz BW Option MAY NOT (?) be a problem for the DS2000 as was previously reported.  Anyway I'm going to reinstall the 300MHz BW Option in my unit, as I didn't have any issues with it before, other than the technical BW/2GHz Sampling limitations 'marmad' had previously brought to all of our attention.

DS2000, D2000A Device BW Options:  DSAJ - 100MHz BW,  DSAS - 200MHz BW,  DSEZ - 200MHz BW and all Options,  DSCA - 300MHz BW.
 

Offline Teneyes

  • Frequent Contributor
  • **
  • Posts: 498
  • Country: ca
Re: Sniffing the Rigol's internal I2C bus
« Reply #3412 on: July 10, 2014, 03:29:29 pm »
So at this point, it's unknown if it's just a bug that exists in v.3 with certain settings - or is linked to 300MHz option being installed. But I have to say, before I ever used the 300MHz option, I rarely had the DS2000 crash - but it's happened many more times with it installed. But more info is definitely needed to pinpoint the source of the problem.
I agree with Marmad that the accuracy of 300MHz is questionable with only 1GSa/s,

I have installed the 300MHz option.  ( I do like 1nsec/div)
Unlike Marmad, I do not use my DSO very much (retired) and it is not required to be 100% available.
I am willing to use 300MHz in order to isolate the conditions that causes the DSO to HANG. 

I have seen in FW 00.03.00.00.00 where the Math function 'lg(' would HANG the DSO ,but that does not occured (Fixed) in FW 00.03.00.01.03. This does indicate that often Rigol has not tested new firmware changes thoroughly.

PS  , My DSO is back to S/N= DS2A000000001 with DS2302, but easy to reset
« Last Edit: July 10, 2014, 07:47:13 pm by Teneyes »
IiIiIiIiIi  --  curiosity killed the cat but, satisfaction brought it back
 

Offline ted572

  • Frequent Contributor
  • **
  • Posts: 399
  • Country: us
  • Radio Communications Equipment/System Design Engr.
Re: Sniffing the Rigol's internal I2C bus
« Reply #3413 on: July 10, 2014, 07:39:20 pm »
Install - Uninstall Rigol's Options using UltraSigma
 

Offline motocoder

  • Supporter
  • ****
  • Posts: 769
  • Country: us
  • Electrical Engineer
Re: Sniffing the Rigol's internal I2C bus
« Reply #3414 on: July 11, 2014, 06:04:06 am »
Install - Uninstall Rigol's Options using UltraSigma

Thanks, Ted
 

Offline aurel

  • Contributor
  • Posts: 16
  • Country: fr
Re: Sniffing the Rigol's internal I2C bus
« Reply #3415 on: July 17, 2014, 06:52:47 pm »
Like many of you, I received a brand new DP832 power supply a few weeks ago, with firmware 1.09 installed. Which means no working keygen and no possibility to downgrade...

Well... Not anymore !

I've spent quite some time reverse engineering the new firmware, and I discovered that they didn't change the signing algorithm, and not even the private key. Overall, they only added some bits shuffling (ie. obfuscation) on the final license string and they changed the options coding.

So I took the latest riglol version I found (from http://gotroot.ca/rigol/), and added support for generating license for this new DP832 firmware. It works exactly the same as before. You just need to specify different options string depending on your DP832 firmware version. Executing riglol without parameters will list the valid options depending on firmware version.

I also found other valid options strings but they do not seem to have any effect. And as it seems there is no way to uninstall options on the DP832 (am I wrong ?), I can't check if those unknown options actually activates the same features as some other options. Anyway, here is the list of unknown options, if somebody wants to play with: FPLT, FTLT, F2PT, F4PT.

I compiled this new riglol version for linux, osx and windows, as well as the web version. It would be nice if the persons handling http://gotroot.ca/rigol/riglol/ and http://riglol.3owl.com/ could update their online version.

Enough talk ? You want some action ? Here you go: riglol-20140717.zip
SHA1 of this file: 662b9f460eb618856567587e39827104f22049ca

And last but not least, huge thanks to everybody involved in this riglol hack, and especially to cybernet and zombie28 !
 

Offline mcinque

  • Supporter
  • ****
  • Posts: 1129
  • Country: it
  • I know that I know nothing
Re: Sniffing the Rigol's internal I2C bus
« Reply #3416 on: July 17, 2014, 07:56:04 pm »
I've spent quite some time reverse engineering the new firmware, and I discovered that they didn't change the signing algorithm, and not even the private key.

Nice work!

But by revealing details you're just suggesting them how to improve the next version ;)
 

Offline sotos

  • Frequent Contributor
  • **
  • Posts: 257
  • Country: gr
Re: Sniffing the Rigol's internal I2C bus
« Reply #3417 on: July 17, 2014, 10:06:46 pm »
I've spent quite some time reverse engineering the new firmware, and I discovered that they didn't change the signing algorithm, and not even the private key.

Nice work!

But by revealing details you're just suggesting them how to improve the next version ;)



Maybe, his working for them. ;)
 

Offline hematose

  • Newbie
  • Posts: 8
Re: Sniffing the Rigol's internal I2C bus
« Reply #3418 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?
 

studio25

  • Guest
Re: Sniffing the Rigol's internal I2C bus
« Reply #3419 on: July 18, 2014, 05:22:11 pm »
It would be nice if the persons handling http://gotroot.ca/rigol/riglol/ and http://riglol.3owl.com/ could update their online version.

I have http://riglol.3owl.com/ updatet. Thank you for your work.
« Last Edit: July 18, 2014, 05:23:47 pm by studio25 »
 

Offline probez

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3420 on: July 18, 2014, 10:37:11 pm »
Thanks a lot Aurel, it rocks :-+

Like many of you, I received a brand new DP832 power supply a few weeks ago, with firmware 1.09 installed. Which means no working keygen and no possibility to downgrade...

Well... Not anymore !

 

Offline anson80

  • Contributor
  • Posts: 10
Re: Sniffing the Rigol's internal I2C bus
« Reply #3421 on: July 21, 2014, 09:49:54 am »
Like many of you, I received a brand new DP832 power supply a few weeks ago, with firmware 1.09 installed. Which means no working keygen and no possibility to downgrade...

Well... Not anymore !

I've spent quite some time reverse engineering the new firmware, and I discovered that they didn't change the signing algorithm, and not even the private key. Overall, they only added some bits shuffling (ie. obfuscation) on the final license string and they changed the options coding.

So I took the latest riglol version I found (from http://gotroot.ca/rigol/), and added support for generating license for this new DP832 firmware. It works exactly the same as before. You just need to specify different options string depending on your DP832 firmware version. Executing riglol without parameters will list the valid options depending on firmware version.

I also found other valid options strings but they do not seem to have any effect. And as it seems there is no way to uninstall options on the DP832 (am I wrong ?), I can't check if those unknown options actually activates the same features as some other options. Anyway, here is the list of unknown options, if somebody wants to play with: FPLT, FTLT, F2PT, F4PT.

I compiled this new riglol version for linux, osx and windows, as well as the web version. It would be nice if the persons handling http://gotroot.ca/rigol/riglol/ and http://riglol.3owl.com/ could update their online version.

Enough talk ? You want some action ? Here you go: riglol-20140717.zip
SHA1 of this file: 662b9f460eb618856567587e39827104f22049ca

And last but not least, huge thanks to everybody involved in this riglol hack, and especially to cybernet and zombie28 !

Thanks Aurel,This is great :-+
 

Offline rodpp

  • Frequent Contributor
  • **
  • Posts: 307
Re: Sniffing the Rigol's internal I2C bus
« Reply #3422 on: July 21, 2014, 05:27:11 pm »
First, congratulations for all involved in this work, it´s amazing!

Knowing the hack method for Rigol DS1000Z, DS2000, DG4000, DSA800 could this help in hacking the DG1000Z series?

Does anyone tried to hack the Rigol DG1000Z Arbitrary Waveform Function Generators?

EDIT: AWF model number correction DG100Z -> DG1000Z.
« Last Edit: July 22, 2014, 06:43:05 am by rodpp »
 

Offline ve7xen

  • Super Contributor
  • ***
  • Posts: 1193
  • Country: ca
    • VE7XEN Blog
Re: Sniffing the Rigol's internal I2C bus
« Reply #3423 on: July 22, 2014, 04:30:57 am »
Enough talk ? You want some action ? Here you go: riglol-20140717.zip
SHA1 of this file: 662b9f460eb618856567587e39827104f22049ca

And last but not least, huge thanks to everybody involved in this riglol hack, and especially to cybernet and zombie28 !

Great work! I have updated my mirror at http://gotroot.ca/rigol/ . The old version also remains for posterity.
73 de VE7XEN
He/Him
 

Offline Weisserrabe

  • Newbie
  • Posts: 4
  • Country: at
Re: Sniffing the Rigol's internal I2C bus
« Reply #3424 on: July 22, 2014, 07:15:42 pm »
I've spent quite some time reverse engineering the new firmware...


 :-+ great thanks to you  :clap:
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf