Products > Test Equipment
Sniffing the Rigol's internal I2C bus
wilheldp:
I really apologize if this has been answered already in this thread, but I'm late to the game and pouring over 141 pages of posts is a bit daunting. But are there firmware limitations on the use of Keygens on Rigol equipment (namely the DP832 and DS1074Z)? For instance, do the keys not work with newer firmwares, and has anyone lost keygen activated features after upgrading the firmware on the equipment?
Rigby:
--- Quote from: wilheldp on December 23, 2013, 12:39:47 am ---I really apologize if this has been answered already in this thread, but I'm late to the game and pouring over 141 pages of posts is a bit daunting. But are there firmware limitations on the use of Keygens on Rigol equipment (namely the DP832 and DS1074Z)? For instance, do the keys not work with newer firmwares, and has anyone lost keygen activated features after upgrading the firmware on the equipment?
--- End quote ---
One of the most commonly stated rules in this thread is that you should update your firmware to the latest release before you apply a keygen-created key.
wilheldp:
--- Quote from: Rigby on December 23, 2013, 12:42:53 am ---One of the most commonly stated rules in this thread is that you should update your firmware to the latest release before you apply a keygen-created key.
--- End quote ---
So it's not a good idea to update the firmware until the sniffers of the I2C have figured out if it borks the keys?
true:
The only firmware that was known to have a problem was the early version of the DS2000, which would cause reset serial numbers (like it did for my unit).
For DP832, I believe I may have (mis?)read that .08 has problems; use .06 to apply the keys then update.
Otherwise, yes, you want to update first.
alank2:
--- Quote from: true on December 23, 2013, 02:19:42 am ---The only firmware that was known to have a problem was the early version of the DS2000, which would cause reset serial numbers (like it did for my unit).
--- End quote ---
I used to believe the S/N could not be mangled with 00.01.01.00.02, but I was wrong. Not sure how I did it, playing around with keys, but mine did get mangled on 00.01.01.00.02.
Thanks,
Alan
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version