Products > Test Equipment
DS2000A Upgrade Utility
marmad:
--- Quote from: Gandalf_Sr on August 02, 2014, 12:04:55 pm ---I need the I2C/SPI protocol analysis function. I was considering buying a DS2072A and doing this upgrade but I can see a lot of hits on the Internet saying there are decode bugs with SPI/I2C/UART on Rigol scopes.
Can anyone confirm or deny the existence of this problem or point me to more info?
--- End quote ---
I've used the I2C protocol decoding regularly with no problems (I can't speak about the SPI or UART since I haven't used them). It's certainly not a full-featured logic analyzer (but neither is any MSO I've tried), but it does what it says it does - and with the latest FW, it finally does protocol decoding on recorded segments too.
And I wouldn't lump all Rigol scopes together - from what I understand (at the moment), except for the protocols which normally really require more than 2 channels, the protocol decoding is best implemented on the DS2000 series.
Teneyes:
--- Quote from: Gandalf_Sr on August 02, 2014, 12:04:55 pm ---I need the I2C/SPI protocol analysis function. I was considering buying a DS2072A and doing this upgrade but I can see a lot of hits on the Internet saying there are decode bugs with SPI/I2C/UART on Rigol scopes.
--- End quote ---
We did find a bug in RS 232 decoding (was using 56000 instead of 56kb= 57600), but that was corrected. I also tested the CAN protocol decode to be good. And decoding of recorded data was corrected in FW 00.03...... .
JAmerican:
--- Quote from: airs on July 29, 2014, 05:46:40 pm ---Just tried this utility and it worked perfectly the first time. One thing to note is you need to be patient when CH1 is flashing - the FW update took quite a while for me (5 minutes?)
Btw, my unit came with Software: 00.03.00.SP1 and Hardware: 2.0
I used a 8GB USB 2.0 Kingston Data Traveler stick, formatted as FAT32 with Default Allocation Size. It had nothing on it other than the .GEL file.
Thank you so much for this!!
--- End quote ---
I agree with you. I just received mine end of July 2014 and it had 00.03.00.SP1 on it. I thought I would be banned from using the utility. I used the utility and flashed the custom firmware as per the instructions. It took a few minutes and when it was done, some of the lights turned on.
I used a 2GB USB stick with the FAT32 format and Default Allocation Size (named the volume DSO). I had taken a screenshot from the Rigol before flashing it to see if it would save to the USB stick before using it to flash the firmware.
After the flash to the custom firmware, I had version 00.02.00. I was able to unlock all options and get 300MHz using the utility. Once I was done, I went back to my original 00.03.00.SP1 firmware.
Some people mentioned that their measurements were out of calibration. I had this issue when I downgraded with the custom firmware but once I returned to my original firmware, my scope's voltage offset issues were fixed. I think the issue was that people were testing in the firmware that they downgraded to. You need to return to the firmware you originally had on your scope and then test from there.
I did not self-calibrate during this whole process.
I'm very happy with the results. :-+ :clap:
conte_vlad:
:-+ very good. What hardware version has your scope? 2.0 or 2.2? let us know :) (it is displayed on scope just after firmware version)
JAmerican:
--- Quote from: conte_vlad on August 03, 2014, 03:49:54 am --- :-+ very good. What hardware version has your scope? 2.0 or 2.2? let us know :) (it is displayed on scope just after firmware version)
--- End quote ---
I have HW ver. 2.0. Didn't know there was a 2.2 version.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version