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

0 Members and 2 Guests are viewing this topic.

Offline stormbr

  • Regular Contributor
  • *
  • Posts: 50
  • Country: br
Re: Sniffing the Rigol's internal I2C bus
« Reply #1200 on: October 19, 2013, 02:20:44 am »
Hi Bugware,

1.  Generates both Windows-Apps correct licenses?

You can use the synapsis version and hit 300mhz too, as the user Niffler explain. But i have sure that the two versions works fine.

2. Are there more possible to activate?

Others users says for me that private key with 14 digits (8EEBD4D04C3771) not work 100% with ds2072a and i not tried uninstall the update yet (not have sure if i going to do this).

My case - with the same software/hardware/mcu version.

Unlock method: studio25 (last post) by windows prompt.
model: 2202 (after update)
serial number: not change
time base: 2ns
bw filter/limit - options: off - 20m - 100m - (not have 200m)
50ohm option: not unlock

Note:

The keygen of studio25 works well (thanks for your work) with all other options unlocked, but i not hit 300mhz.

3. Does anyone know what the difference is to the MCU 02.12?

I think that it's not important because just the software version (not fpga) is updated.

http://www.gotroot.ca/rigol/

Good luck.
« Last Edit: October 19, 2013, 03:00:55 am by stormbr »
 

Offline AndreaEl

  • Contributor
  • Posts: 40
  • Country: it
Re: Sniffing the Rigol's internal I2C bus
« Reply #1201 on: October 19, 2013, 08:03:27 am »
It's normal that my DS2072 when i start it the fan run with low noise, but after 1 min it run at full power and never slow the speed.
My equipment:

Multimeter: HP 34401A, HP 3478A, HP 3466A, Fluke 115
Oscilloscope: Rigol DS2072 (DS2202)
Function generator: SRS DS335
Electronic load: Maynuo M9811
Power supply: TDK-Lambda ZUP 20-20, 2x Atten TPR3602A, Atten APR1505A, Atten APR12001A, Atten AT1001D
 

Offline Carrington

  • Super Contributor
  • ***
  • Posts: 1202
  • Country: es
Re: Model: DS2302
« Reply #1202 on: October 19, 2013, 02:29:25 pm »
Hi,

I just used the KeyGen (ver 2.0b1) to generate a license key.
Before doing so i made sure i had the latest firmware version 00.01.01.00.02

System information before using license key:

Model:   DS2072
Serial:  DS2A1515xxxxx
Software version:  00.01.01.00.02
Hardware version:  1.0.2.0.0
FPGA version:
                   SPU  03.01.05
                   WPU  00.06.05
                   CCU  12.29.00
                   MCU  00.05

The license key was generated using Option code: DSAZ (all options, DS2202, License Type: Official)
After restart the options page shows all options install and official with 200M BandWidth option.
I can now set horizontal scale down to 1nsec and bandwidth limit to 20M, 100M and 200M.
Se attached image.

It sems like my scope thinks it is a 300 MHz version  :-+  unfortunate i don't have anything to test its bandwidth with.
Have any body seen this before ?

PS, Thanks for all your hard work in this forum, great read.
All this is very strange, does not match with anything known until now.
https://www.eevblog.com/forum/testgear/rigol-ds2000-hardware-version-2-0/msg270500/#msg270500
https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg264041/#msg264041

Range for Probes:
https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg265546/#msg265546

It is disconcerting, it also becomes in a DS2302...
Niffler, please could you check the BW?
« Last Edit: October 19, 2013, 05:45:25 pm by Carrington »
My English can be pretty bad, so suggestions are welcome. ;)
Space Weather.
Lightning & Thunderstorms in Real Time.
 

Offline Carrington

  • Super Contributor
  • ***
  • Posts: 1202
  • Country: es
Re: Sniffing the Rigol's internal I2C bus
« Reply #1203 on: October 19, 2013, 02:32:47 pm »
It's normal that my DS2072 when i start it the fan run with low noise, but after 1 min it run at full power and never slow the speed.
The same thing happens with mine, and I think that with all.
My English can be pretty bad, so suggestions are welcome. ;)
Space Weather.
Lightning & Thunderstorms in Real Time.
 

Offline eurofox

  • Supporter
  • ****
  • Posts: 873
  • Country: be
    • Music
Re: Sniffing the Rigol's internal I2C bus
« Reply #1204 on: October 19, 2013, 02:45:36 pm »
It's normal that my DS2072 when i start it the fan run with low noise, but after 1 min it run at full power and never slow the speed.
The same thing happens with mine, and I think that with all.

The Rigol Hacker virus in action, next step is erase the firmware and destroy all electronics  :-DD :-DD :-DD
eurofox
 

Offline AndreaEl

  • Contributor
  • Posts: 40
  • Country: it
Re: Sniffing the Rigol's internal I2C bus
« Reply #1205 on: October 19, 2013, 09:55:44 pm »
I have try another time for have a DS2302 but nothing...

This time i have install the key from USB connection:
Seed: 1
All Option + 200MHz

After install key i have:
Model: DS2202
time base: 2ns
BW options: off - 20m - 100m (NO 200MHz)
ONLY 1MOhm


we have other ideas for try to have a ds2302??

The people that have a 2302 can explain step by step what they do for have a 2302??
My equipment:

Multimeter: HP 34401A, HP 3478A, HP 3466A, Fluke 115
Oscilloscope: Rigol DS2072 (DS2202)
Function generator: SRS DS335
Electronic load: Maynuo M9811
Power supply: TDK-Lambda ZUP 20-20, 2x Atten TPR3602A, Atten APR1505A, Atten APR12001A, Atten AT1001D
 

studio25

  • Guest
Re: Sniffing the Rigol's internal I2C bus
« Reply #1206 on: October 19, 2013, 10:16:47 pm »
 

Offline AndreaEl

  • Contributor
  • Posts: 40
  • Country: it
Re: Sniffing the Rigol's internal I2C bus
« Reply #1207 on: October 19, 2013, 10:34:59 pm »
My equipment:

Multimeter: HP 34401A, HP 3478A, HP 3466A, Fluke 115
Oscilloscope: Rigol DS2072 (DS2202)
Function generator: SRS DS335
Electronic load: Maynuo M9811
Power supply: TDK-Lambda ZUP 20-20, 2x Atten TPR3602A, Atten APR1505A, Atten APR12001A, Atten AT1001D
 

studio25

  • Guest
Re: Sniffing the Rigol's internal I2C bus
« Reply #1208 on: October 19, 2013, 10:44:49 pm »
http://riglol.3owl.com/

Perfect!!! Any update in this release?

No, only minimal changes such as a version number, and minor cleanup.
 

Offline Bugware

  • Contributor
  • Posts: 20
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #1209 on: October 20, 2013, 12:23:47 am »
Hi to all,

Thank you for reply stormbr.

1.  Generates both Windows-Apps correct licenses?

You can use the synapsis version and hit 300mhz too, as the user Niffler explain. But i have sure that the two versions works fine.
I was not interested in more BW and 50ohm option than more in CAN trigger/decode for the future.
But it is nice to see the challenge how to get maybe all option free. That is like a TV Thriller… ;)

The first question I posed was only because I got my DS2072 only a week ago. So I cannot decide to unlock the licenses immediately or later. I want check the device at first. Or send it back and wait for the DS2072A...


2. Are there more possible to activate?

Others users says for me that private key with 14 digits (8EEBD4D04C3771) not work 100% with ds2072a and i not tried uninstall the update yet (not have sure if i going to do this).

My case - with the same software/hardware/mcu version.

Unlock method: studio25 (last post) by windows prompt.
model: 2202 (after update)
serial number: not change
time base: 2ns
bw filter/limit - options: off - 20m - 100m - (not have 200m)
50ohm option: not unlock

Note:

The keygen of studio25 works well (thanks for your work) with all other options unlocked, but i not hit 300mhz.
The second point I wanted to see how the TV Thriller continues, and perhaps to give some ideas to rekindle the “research fire” to continue.

And it’s true, there was something like 13 and 14 digit of serial numbers with the DS2072 (without the “a”. Or do you get already a new one DS2072A?). I think, that problem was solved in reply#567 ff on page 38. But it was not really clear to me, is it a general problem that been solved or the 13/14 chars long serial/lic1/lic2 or whatever problem…? Very confusing.


3. Does anyone know what the difference is to the MCU 02.12?

I think that it's not important because just the software version (not fpga) is updated.
 
The third point was not only to know, what is the change in MCU 02.12. I'm interested in, but also in how the MCU (or even FPGA) can get new Software? With a new Firmware? If the Firmware update 00.01.01.00.02 include the new MCU Version, why nobody get them? My Rigol was shipped with the new Firmware but with MCU 02.12. Where is the difference between the shipped version and the update version of the “same” Firmware (or does the Firmware never change the MCU Version?)? Maybe there are different versions of the same Firmware 00.01.01.00.02? Could I clearly express what I want to say? ;)

This is all very exciting!
Bugware
« Last Edit: October 20, 2013, 03:27:11 am by Bugware »
 

Offline Bugware

  • Contributor
  • Posts: 20
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #1210 on: October 20, 2013, 12:34:21 am »
Hi AndreaEl,

I have try another time for have a DS2302 but nothing...

This time i have install the key from USB connection:
Seed: 1
All Option + 200MHz

After install key i have:
Model: DS2202
time base: 2ns
BW options: off - 20m - 100m (NO 200MHz)
ONLY 1MOhm


we have other ideas for try to have a ds2302??

The people that have a 2302 can explain step by step what they do for have a 2302??

I think you can try 100 times but don't get a 2302 with the actual KeyGen. Niffler has only luck by get a DS2302. What conditions enabled that is not clear yet...
 

Offline Bugware

  • Contributor
  • Posts: 20
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #1211 on: October 20, 2013, 12:36:33 am »
http://riglol.3owl.com/

Perfect!!! Any update in this release?

No, only minimal changes such as a version number, and minor cleanup.

Version number! Nice! Thank you! :)
 

Offline jsykes

  • Contributor
  • Posts: 31
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #1212 on: October 20, 2013, 06:45:15 am »
I just noticed something with the DSA815 KeyGens. Unlike the DS2, the DSA keygen always generates the same key for a particular serial number no matter how many times the generate action is initiated. The keys are the same whether using the Linux, Windows GUI, or the DOS command line versions with the exception of the AAAC (advanced measurement kit) key. The same key is always returned no matter how many times that AAAC key is generated but the DOS command line KeyGen returnes a different key than the Windows or Linux Keygens do only for that adv measurement kit. I'm sure the Windows or Linux keys generated for that function work but I don't know if that different command line generated key does.
I cannot test the web based generator because it doesn't work for me using either Iexplorer or Firefox. In Iexplorer after entering the serial, private key and function, nothing happens when clicking generate. I have enabled active x permissions without success but since the other KeyGens work I don't need it. I'm just wondering if the different AAAC key returned by the command line KeyGen version is valid.
 

Offline stormbr

  • Regular Contributor
  • *
  • Posts: 50
  • Country: br
Re: Sniffing the Rigol's internal I2C bus
« Reply #1213 on: October 20, 2013, 01:03:23 pm »

1-) Or send it back and wait for the DS2072A...

DS2072A = DS2072 Hardware version 2.0

Quote
2-)The second point I wanted to see how the TV Thriller continues, and perhaps to give some ideas to rekindle the “research fire” to continue.

And it’s true, there was something like 13 and 14 digit of serial numbers with the DS2072 (without the “a”. Or do you get already a new one DS2072A?). I think, that problem was solved in reply#567 ff on page 38. But it was not really clear to me, is it a general problem that been solved or the 13/14 chars long serial/lic1/lic2 or whatever problem…? Very confusing.

I not have any idea about this, prefer leave this question for the hardcore users.

 
Quote
3-) The third point was not only to know, what is the change in MCU 02.12. I'm interested in, but also in how the MCU (or even FPGA) can get new Software? With a new Firmware? If the Firmware update 00.01.01.00.02 include the new MCU Version, why nobody get them? My Rigol was shipped with the new Firmware but with MCU 02.12. Where is the difference between the shipped version and the update version of the “same” Firmware (or does the Firmware never change the MCU Version?)? Maybe there are different versions of the same Firmware 00.01.01.00.02? Could I clearly express what I want to say? ;)

You've need the last firmware for update your device and it's necessary send to rigol a request form for download the new firmware.

I don't know anything about how to do update the firmware to ds2072 and not found the firmware on rigol web site.






 

Offline Pinkus

  • Frequent Contributor
  • **
  • Posts: 773
Re: Sniffing the Rigol's internal I2C bus
« Reply #1214 on: October 20, 2013, 01:09:23 pm »
Quote
Niffler has only luck by get a DS2302. What conditions enabled that is not clear yet...

I assume Niffler does not want to make his serial public but maybe he can send his serial # and the produced license # to Cybernet so he (Cybernet) can find out what specific circumstances are needed to produce exactly this serial #. This might then lead to a revised code which brings all 2072 to 300 Mhz and maybe a CAN bus interpreter.
 

Offline true

  • Frequent Contributor
  • **
  • Posts: 329
  • Country: us
  • INTERNET
Re: Sniffing the Rigol's internal I2C bus
« Reply #1215 on: October 20, 2013, 04:56:22 pm »
...or the DOS command line versions...
...but the DOS command line KeyGen...
lol, who compiled it for DOS?
 

Offline Bugware

  • Contributor
  • Posts: 20
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #1216 on: October 21, 2013, 02:13:30 am »

1-) Or send it back and wait for the DS2072A...

DS2072A = DS2072 Hardware version 2.0

This is not proven. I don't believe that, until someone makes a teardown of the new model DS2072A. Sure, in the DS2072 HW 2.0 are many new parts, that not be used (e.g. the 50ohm with the relay and other stuff - Yes I've seen the pics of PA0PBZ here). But maybe that is only the first step to the DS2072A. Maybe they designed a new PCB and started with the production of the HW 2.0 but after that they found some missing "things" that not sufficient with the requirements of the DS2072A but with DS2027. So they don't change the PCB for the DS2072, because of cost, and we get HW 2.1 with the DS2072A. Why they don't called the HW 2.0 at the very beginning DS2072A?
Maybe there are only some jumpers on the HW 2.0 to change it to the "A"-Model. Maybe they only need new Firmware.

There are too many "Maybe's" so we will wait and see what happen. These are just guesses of some people here that DS2072A = DS2072 Hardware version 2.0, but nobody knows it 100%.

Clearly I would be happy if it is only a Firmware Upgrade and my DS2072 HW 2.0 becomes an A-Model! ;)


3-) The third point was not only to know, what is the change in MCU 02.12. I'm interested in, but also in how the MCU (or even FPGA) can get new Software? With a new Firmware? If the Firmware update 00.01.01.00.02 include the new MCU Version, why nobody get them? My Rigol was shipped with the new Firmware but with MCU 02.12. Where is the difference between the shipped version and the update version of the “same” Firmware (or does the Firmware never change the MCU Version?)? Maybe there are different versions of the same Firmware 00.01.01.00.02? Could I clearly express what I want to say? ;)

You've need the last firmware for update your device and it's necessary send to rigol a request form for download the new firmware.

I don't know anything about how to do update the firmware to ds2072 and not found the firmware on rigol web site.

Yes, normally you need to contact Rigol to get a new Firmware.

But marmad collects the new Firmware in the Review-Thread here. There are also described how the Firmware update works...
« Last Edit: October 21, 2013, 02:26:16 am by Bugware »
 

Offline darrylp

  • Regular Contributor
  • *
  • Posts: 127
  • Country: gb
Re: Sniffing the Rigol's internal I2C bus
« Reply #1217 on: October 21, 2013, 09:48:48 am »
I did, but sure others did as well. However mine was from the very first few releases of the code base.

Darryl

 

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 #1218 on: October 21, 2013, 12:32:13 pm »
...or the DOS command line versions...
...but the DOS command line KeyGen...
lol, who compiled it for DOS?

Pretty sure that it was compiled for Windows command-line, not DOS.  Some people call this "DOS" even though it isn't DOS.
 

Offline olsenn

  • Frequent Contributor
  • **
  • Posts: 993
Re: Sniffing the Rigol's internal I2C bus
« Reply #1219 on: October 21, 2013, 01:03:19 pm »
So nobody has been able to get the 300MHz bandwidth out of the DS2000 yet?
 

Offline cosmos

  • Regular Contributor
  • *
  • Posts: 110
  • Country: 00
Re: Sniffing the Rigol's internal I2C bus
« Reply #1220 on: October 21, 2013, 01:32:54 pm »
ve7xen seems to have confirmed it?

Link does not work, get the one two posts down.
https://www.eevblog.com/forum/testgear/sniffing-the-rigol's-internal-i2c-bus/msg239833/#msg239833

« Last Edit: October 21, 2013, 02:51:56 pm by cosmos »
 

Offline olsenn

  • Frequent Contributor
  • **
  • Posts: 993
Re: Sniffing the Rigol's internal I2C bus
« Reply #1221 on: October 21, 2013, 02:12:03 pm »
That confirms that the device is capable of having a 300MHz bandwidth, but I'm referring to unlocking the option in the firmware (similar to the 50-ohm input) without hardware modifications
 

Offline arvidj

  • Contributor
  • Posts: 32
  • Country: us
 

Offline jsykes

  • Contributor
  • Posts: 31
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #1223 on: October 21, 2013, 11:11:05 pm »
...or the DOS command line versions...
...but the DOS command line KeyGen...
lol, who compiled it for DOS?

Pretty sure that it was compiled for Windows command-line, not DOS.  Some people call this "DOS" even though it isn't DOS.

 Thanks, Rigby
That's exactly what I was referring to. I'm from the pre-windows generation so I called the windows command line simulation of DOS, just that. Anyway, the subject of the post was about AAAC returning a different key only when generated with the command line version. Just wanted to report that observation.
 

Offline cosmos

  • Regular Contributor
  • *
  • Posts: 110
  • Country: 00
Re: Sniffing the Rigol's internal I2C bus
« Reply #1224 on: October 22, 2013, 03:12:39 pm »
Found something for the DS4000 that was new to me.

The key sequence for getting extended version info also open other stuff.
to enter and exit : Trig menu -> edge. then in one quick sequence  F7 + F6 + F7 + Utililty

EDIT: (Clarification)
to enter and exit :
Trig menu -> edge.
then in one quick sequence  [MENU7_R] + [MENU6_R] + [MENU7_R] + [Utililty]
(from marmads post earlier in tread)
/EDIT

Now I have:
extended version info under Utility -> system -> System info 
extended power info under Utility -> system -> SelftestInfo
a new sub menu under Utility(2) (second screen) called Project
under project there is now

screen #1:
Screentest
Key test
AuxTest
Gain1
Gain2
-
-

screen #2:
-
EqualCal
DealyCal
-
-
Resumecal

screen #3:
Probecal
Factory
-
-
-
-
-
return

I wonder if there might be even more interesting menus to be activated like this ... how did people find the unlocking key sequence in the first place?

« Last Edit: October 26, 2013, 10:58:41 am by cosmos »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf