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

0 Members and 3 Guests are viewing this topic.

Offline exciler

  • Supporter
  • ****
  • Posts: 3
Re: Sniffing the Rigol's internal I2C bus
« Reply #3550 on: September 23, 2014, 06:46:36 am »
FYI: My DS1054Z has FW 00.04.01.SP2
 

Offline Magnum

  • Regular Contributor
  • *
  • Posts: 195
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #3551 on: September 23, 2014, 12:56:23 pm »
FYI: My DS1054Z has FW 00.04.01.SP2
Thanks. Hopefully I'll receive mine tomorrow.
 

Offline farzadb82

  • Contributor
  • Posts: 12
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3552 on: September 23, 2014, 02:57:16 pm »
FYI: My DS1054Z has FW 00.04.01.SP2

Have you tried using the DS1000z hacks as yet ?  If so, do they work ?

I'm curious because I have the MSO1074Z-S and none of the DS1000Z hacks currently work. Prior to getting the MSO1074Z-S, I had a DS1074Z-S with the older 00.04.00 (I think) firmware and the hacks did work on that scope. I'm suspecting that the firmware image is the same for all DS/MSO1000Z models. From what I can tell, by looking at the firmware image I have, they have changed the way the license keys are generated in 00.04.01.SP2.
 

Offline Magnum

  • Regular Contributor
  • *
  • Posts: 195
  • Country: de
Re: Sniffing the Rigol's internal I2C bus
« Reply #3553 on: September 24, 2014, 12:32:17 pm »
FYI: My DS1054Z has FW 00.04.01.SP2
Same firmware here, codes work.
 

Offline toni31

  • Contributor
  • Posts: 19
Re: Sniffing the Rigol's internal I2C bus
« Reply #3554 on: September 24, 2014, 01:31:23 pm »
i think a new thread for 1054z it helps
 

Offline pierre288

  • Newbie
  • Posts: 8
Re: Sniffing the Rigol's internal I2C bus
« Reply #3555 on: September 25, 2014, 11:31:15 am »
Hi,
I recently got a  MSO1074Z-S which is at version 00.04.01.SP2
I tried to add features but did not work either for me.

Any hope to get a rigol utility update soon ?

thanks
 

Offline rmd79

  • Contributor
  • Posts: 18
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #3556 on: September 25, 2014, 11:46:17 am »
Hi,
I recently got a  MSO1074Z-S which is at version 00.04.01.SP2
I tried to add features but did not work either for me.

Any hope to get a rigol utility update soon ?

thanks

I've got a memory dump of my MSO1074Z-S if anyone wants to have a look into it.  PM me if you're interested.  Its about 8MB compressed.
 

Offline alank2

  • Super Contributor
  • ***
  • Posts: 2185
Re: Sniffing the Rigol's internal I2C bus
« Reply #3557 on: September 25, 2014, 09:33:13 pm »
There was a time when the DS2302 (300MHz) mode was buggy with the 00.02.01.00.03 firmware.  Did the 00.03.00.01.03 version correct the issues?  Is there a downside to running it as a ds2302 compared to a ds2202 any longer?
 

Offline hammy

  • Supporter
  • ****
  • Posts: 465
  • Country: 00
Re: Sniffing the Rigol's internal I2C bus
« Reply #3558 on: September 26, 2014, 08:26:38 am »
I've got a memory dump of my MSO1074Z-S if anyone wants to have a look into it.  PM me if you're interested.  Its about 8MB compressed.

Your serial number starts with "DS1ZD" and my serial with "DS1ZC". The following six numbers are the same, except for the last three numbers.
I suppose the "D" is for the model with the signal generator (MSO1074Z-S) and the "C" is for the model without sig-gen (MSO1074Z).

 :-/O
« Last Edit: September 26, 2014, 09:43:32 am by hammy »
 

Offline Gandalf_Sr

  • Super Contributor
  • ***
  • Posts: 1729
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3559 on: September 26, 2014, 01:15:11 pm »
There was a time when the DS2302 (300MHz) mode was buggy with the 00.02.01.00.03 firmware.  Did the 00.03.00.01.03 version correct the issues?  Is there a downside to running it as a ds2302 compared to a ds2202 any longer?

I 'upgraded' my MSO2072A to a MSO2302A; so far I have had no issues.  The I2C decode seems slow, you can't look at the decode real time, you have to capture a single shot and then you can see it go past doing the decode.  In this respect, having such a large memory is clearly an advantage, I have a Tektronix MDO2024 at work and it's annoying that you can capture a section of I2C with decode but when you start scrolling through the message chain, it quickly craps out because it's run out of memory.  I'll check on the software versions on my MSO2302A and update this post.
If at first you don't succeed, get a bigger hammer
 

Offline bistopepmol

  • Newbie
  • Posts: 4
  • Country: gb
Re: Sniffing the Rigol's internal I2C bus
« Reply #3560 on: September 27, 2014, 02:03:11 am »
Hey there,

Got my new scope a couple of days ago,  DS2072A ( to replace my Poorly Tektronix 2430a (trig fault) ) Hardware ver 1.0.2.0.2 and firmware 00.03.00.01.03, I followed the great posts on here and now I have a DS2302 and all is well, thank you so much guys for the brilliant posts,  :-+  :-+ 

What ever you do, don't let the magic smoke out !!
 

Offline alank2

  • Super Contributor
  • ***
  • Posts: 2185
Re: Sniffing the Rigol's internal I2C bus
« Reply #3561 on: September 27, 2014, 11:47:03 pm »
I 'upgraded' my MSO2072A to a MSO2302A; so far I have had no issues.  The I2C decode seems slow, you can't look at the decode real time, you have to capture a single shot and then you can see it go past doing the decode.  In this respect, having such a large memory is clearly an advantage, I have a Tektronix MDO2024 at work and it's annoying that you can capture a section of I2C with decode but when you start scrolling through the message chain, it quickly craps out because it's run out of memory.  I'll check on the software versions on my MSO2302A and update this post.

Thanks for the info, anyone else, especially those running earlier DS2072 hardware versions having good or bad luck with the 2302 mode with FW 00.03.00.01.03?

Also, I thought I saw discussion about upgrading the bootloader and being unable to downgrade below certain firmware or something.  Was that for the DS2000 series or something else?
« Last Edit: September 28, 2014, 12:23:20 am by alank2 »
 

Offline Jog

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3562 on: September 28, 2014, 09:49:05 am »
Hi together,

good news & bad news.... |O

Scope DS2072a FW 03. SP1, HW2.0

Memory dump with: echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
works fine. 12,9MB. :-+

rigup DS2072A DS2072A_sdram.bin > opt.txt
works also fine and generates 4 different keys (only all options, 100MHz full option, 200 & 300) and I try all but they sems not to fit.
PS: also rigup scan DS2072A_sdram.bin > ec_decoded.txt works also fine an generates valid entries :-+

BUT entering the key over:
a) Scope directly = 0 reaction
b) over Ultra Sigma SCPI command ":SYSTem:OPTion:INSTall key" = 0 reaction
c) over Ncat via LAN "echo :SYST:OPT:INSTALL A_KEY_FROM_OPTIONS_WITHOUT_DASHES | ncat -i 1 SCOPE_ADDRESS_HERE 5555" = also 0 reaction

 :(

Any ideas/hints why it fails?

Update: Scope was blocked by to many false tries to enter unknown Options. After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys

 :D :D :D :D IT works!  ;D ;D ;D ;D

many thanks to all!
« Last Edit: September 28, 2014, 10:42:40 am by Jog »
 

Offline Gandalf_Sr

  • Super Contributor
  • ***
  • Posts: 1729
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3563 on: September 28, 2014, 11:28:09 am »
@Jog

Glad to hear you got your DS2072A 'upgraded', I was unaware of the factory reset procedure until you posted it.
If at first you don't succeed, get a bigger hammer
 

Offline farzadb82

  • Contributor
  • Posts: 12
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3564 on: September 29, 2014, 02:51:21 am »
Hi together,

good news & bad news.... |O

Scope DS2072a FW 03. SP1, HW2.0

Memory dump with: echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
works fine. 12,9MB. :-+

rigup DS2072A DS2072A_sdram.bin > opt.txt
works also fine and generates 4 different keys (only all options, 100MHz full option, 200 & 300) and I try all but they sems not to fit.
PS: also rigup scan DS2072A_sdram.bin > ec_decoded.txt works also fine an generates valid entries :-+

BUT entering the key over:
a) Scope directly = 0 reaction
b) over Ultra Sigma SCPI command ":SYSTem:OPTion:INSTall key" = 0 reaction
c) over Ncat via LAN "echo :SYST:OPT:INSTALL A_KEY_FROM_OPTIONS_WITHOUT_DASHES | ncat -i 1 SCOPE_ADDRESS_HERE 5555" = also 0 reaction

 :(

Any ideas/hints why it fails?

Update: Scope was blocked by to many false tries to enter unknown Options. After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys

 :D :D :D :D IT works!  ;D ;D ;D ;D

many thanks to all!

Hi Jog. Do you know if the factory reset procedure is the same for all Rigol scopes ?  I have a MSO1074Z-S scope and I keep getting a message that states I'm unable to enter any more keys for 12 hours.


-- Farzad
 

Offline Jog

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3565 on: September 29, 2014, 02:53:19 pm »
Hi, I am not sure but I found it  as pdf on the rigol hp directly. You can search. Rg Jog
 

Offline LoyalServant

  • Regular Contributor
  • *
  • Posts: 65
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3566 on: September 29, 2014, 06:39:40 pm »
This method worked for me with a tweak, see below....

Hi together,

good news & bad news.... |O

Scope DS2072a FW 03. SP1, HW2.0

Memory dump with: echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
works fine. 12,9MB. :-+

rigup DS2072A DS2072A_sdram.bin > opt.txt
works also fine and generates 4 different keys (only all options, 100MHz full option, 200 & 300) and I try all but they sems not to fit.
PS: also rigup scan DS2072A_sdram.bin > ec_decoded.txt works also fine an generates valid entries :-+

BUT entering the key over:
a) Scope directly = 0 reaction
b) over Ultra Sigma SCPI command ":SYSTem:OPTion:INSTall key" = 0 reaction
c) over Ncat via LAN "echo :SYST:OPT:INSTALL A_KEY_FROM_OPTIONS_WITHOUT_DASHES | ncat -i 1 SCOPE_ADDRESS_HERE 5555" = also 0 reaction

 :(

Any ideas/hints why it fails?

Update: Scope was blocked by to many false tries to enter unknown Options. After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys

 :D :D :D :D IT works!  ;D ;D ;D ;D

many thanks to all!

One small tweak:
I changed...
Quote
echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1 SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin
To:
Quote
echo :SYST:UTIL:READ? 15441920,13262848 | ncat -i 1s SCOPE_ADDRESS_HERE 5555 > DS2072A_sdram.bin

The scope is not answering fast enough for some reason so ncat was dropping an empty file.

Confirming the 300Mhz key did NOT work for me.
The output of rigup said it was untested and unconfirmed.. so confirming at least for me it was a no go.
The 200Mhz key did work.

Cheers guys.

 

Offline Jog

  • Newbie
  • Posts: 4
Re: Sniffing the Rigol's internal I2C bus
« Reply #3567 on: September 30, 2014, 04:26:43 am »
Hi Rf, normaly not necessary to change the ncat -i 1 to 1s because -i stands for idle time. For me it was no different because the file size was the same. But know you have a 200mhz. Have fun
 

Offline LoyalServant

  • Regular Contributor
  • *
  • Posts: 65
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3568 on: September 30, 2014, 04:00:30 pm »
Hi Rf, normaly not necessary to change the ncat -i 1 to 1s because -i stands for idle time. For me it was no different because the file size was the same. But know you have a 200mhz. Have fun

Yes, it is the idle time... but the -i option without any additional parameters is assumed to be milliseconds.
That means ncat needs to have some data coming at it within 1 millisecond.... that's cutting it close which is why I had trouble.
Just posted for others that might not know what ncat is or how to use it.

I am curious about the feature that Rigol has in this scope to dump the ram like that...
 

Online Fungus

  • Super Contributor
  • ***
  • Posts: 16711
  • Country: 00
Re: Sniffing the Rigol's internal I2C bus
« Reply #3569 on: September 30, 2014, 05:30:25 pm »
Quote
After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys...

Is there a secret 'reset' button like this for the DS1000Z ?

 

Offline farzadb82

  • Contributor
  • Posts: 12
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3570 on: September 30, 2014, 06:36:26 pm »
Quote
After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys...

Is there a secret 'reset' button like this for the DS1000Z ?

Unfortunately, there's nothing "officially" documented, that I was able to find. I attempted the procedure above, but had no success.

Without any official documentation or insider information, I think the only way to discover or find features like this would be to disassemble the firmware image and trace code paths. I'm taking a stab at this right now, but have a steep learning curve ahead.


-- Farzad
 

Offline Gixy

  • Regular Contributor
  • *
  • Posts: 232
  • Country: fr
Re: Sniffing the Rigol's internal I2C bus
« Reply #3571 on: October 01, 2014, 04:31:27 pm »
http://beyondmeasure.rigoltech.com/acton/attachment/1579/f-02f4/1/-/-/-/-/file.pdf

Reset procedure for DS2000/4000/6000, to be confirmed for DS1000 series.
 

Offline seronday

  • Regular Contributor
  • *
  • Posts: 93
  • Country: au
Re: Sniffing the Rigol's internal I2C bus
« Reply #3572 on: October 03, 2014, 12:52:52 pm »
DS4000 series Bandwidth (model type) Option Codes.

For those who have an interest in the DS4000, I have found the option codes for selecting the bandwidth .
This also sets the model type.

For example the code FAB9 will select 500Mhz, (DS405x), with all Decoders enabled.

The attached file contains all the details.

There are also two un-documented, possibly future, options called "Power Analysis" and "MA".

The option codes have been tested with firmware ver 00.02.00.00.04 and ver 00.02.01.00.03.

*EDIT*
 Attached updated PDF document to include the option selection codes for LIN and 1553B decode.
Also included are two possible future options,  Power Analysis and I2S decode.
Power Analysis has been listed for some time, but the I2S decode is relatively recent.
The original un-documented "MA" option has become the 1553B decode option.
« Last Edit: June 19, 2016, 05:54:05 am by seronday »
 
The following users thanked this post: manu, rsjsouza, Andrew8086

Offline Gallymimus

  • Regular Contributor
  • *
  • Posts: 178
  • Country: us
Re: Sniffing the Rigol's internal I2C bus
« Reply #3573 on: October 03, 2014, 01:21:52 pm »
Well thats cool, how did you find these extra ds4000 options? Why do you think they weren't discovered before?
 

Online Fungus

  • Super Contributor
  • ***
  • Posts: 16711
  • Country: 00
Re: Sniffing the Rigol's internal I2C bus
« Reply #3574 on: October 03, 2014, 03:58:14 pm »
Quote
After factory reset (multipress left gray button #6 multiple during booting) and retry to enter generated keys...

Is there a secret 'reset' button like this for the DS1000Z ?

Unfortunately, there's nothing "officially" documented, that I was able to find. I attempted the procedure above, but had no success.

I tried the above and it reset all the options and went back to Chinese (seems just like "Storage->Default" but it resets the language as well).

Luckily it starts up in a state where it says "Language" on the menu...easy to go to a different language.
« Last Edit: October 03, 2014, 04:03:24 pm by Fungus »
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf