Products > Test Equipment
New Rigol DS7000
CookieMonster:
--- Quote from: drhex on May 02, 2021, 12:53:23 am ---And managed to brick the scope. Somehow it didn't persist settings through reboot, so tried to install the latest from the website (v00.01.02.00.06), no change. The patched appEntry from v01.01.02.00.06 doesn't work with that, patching it with the same patch bricks the scope - ssh doesn't come up when it gets stuck at appEntry, at least for me. Now I can't reinstall from the bootloader after pressing "single" on power on, says the package is invalid? Doesn't seem to use the USB really, at least not for an extended time before complaining about the package. Does anybody have an idea?
--- End quote ---
Hi All,
I currently have the same issue as @drhex.
Had the same FW version and used hin patch file. Unfortunately I'm now getting stuck at the boot screen with the loading bar.
I tried restoring the firmware with the hidden menu, but it sais 'Upgrading firmware failed, please check the package."
I am using a 2gb usb stick as suggested, but no luck. I tried FAT and FAT32 formats.
Any Ideas ?
CookieMonster:
I managed to find and fix the problem.
I tapped into the UART port in the device to get the log while updating.
--- Code: ---Firmware upgrading
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1: USB EHCI 1.00
scanning bus 1 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
reading ds5000update.gel
** Unable to read file ds5000update.gel **
** Unable to read file ds5000update.gel **
0x4000000:0x2000000:fw4uboot.sh:
File not found fw4uboot.sh
Error:tar 0x4000000 0x2000000 fw4uboot.sh
--- End code ---
as one can see, u-boot is looking for a file called "ds5000update.gel" even though this is a 7000 and the update file is called "ds7000update.gel".
I renamed the file into "ds5000update.gel", the update then preceded flawlessly.
rsjsouza:
Congratulations in finding the solution!
If you haven't skipped any prior firmware updates (as the name of the file might have been changed in the boot code), this clearly shows the amount of testing Rigol invested in the firmware update. |O
tv84:
--- Quote from: rsjsouza on September 01, 2021, 09:51:57 am ---If you haven't skipped any prior firmware updates (as the name of the file might have been changed in the boot code), this clearly shows the amount of testing Rigol invested in the firmware update. |O
--- End quote ---
Let's say that Rigol never advertised the use of the bootloader update menu. Since they must be aware of that part internally, I don't think there is a major error here.
BTW, nice find. As I did all my initial researches in the 5000, never had noticed that "small" detail.
The name seems impossible to change via update since our opinion is that you cannot update the bootloader via a FW update package (almost sure).
CookieMonster:
Alrighty, the hack worked on the second try.
All options are now enable.
That being said, there is another problem.
I think you guys all have the MSO7000, whereas I only have the DS7000 (no function gen and no logic analyser). Yet, with the hack, these features are showing up on the UI.
I guess one would need a different patch to disable these options.
Does anyone have any experience with this ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version