| Products > Test Equipment |
| Bricked Siglent SDG 1032X |
| (1/5) > >> |
| Omega Glory:
I recently purchased a Siglent SDG 1032X arbitrary waveform generator. On my Siglent oscilloscope I captured a waveform and stored it to a .CSV file and then attempted to import it to my arbitrary waveform generator. While importing the waveform, I was given a warning not to turn the machine off until it completed. However, the importing process hung at 35%, so I attempted to reboot the machine. When I did so, I was greeted with a black screen saying: EEPROM: failed() FPGA: failed() ds2301: failed() I was then able to press any key to exit the failure screen and arrive at the main UI. However, now the tool will no longer output anything. I attempted to update the firmware via USB flash drive, and it successfully read the device and rebooted, but I still arrived at the failure screen. I've seen somewhere else that people have had to open up their devices and reflash an internal SD card, or something. Does anybody know anything about that? Thanks - Omega Glory |
| tautech:
--- Quote from: Omega Glory on January 25, 2024, 07:14:38 pm ---I recently purchased a Siglent SDG 1032X arbitrary waveform generator. On my Siglent oscilloscope I captured a waveform and stored it to a .CSV file and then attempted to import it to my arbitrary waveform generator. While importing the waveform, I was given a warning not to turn the machine off until it completed. However, the importing process hung at 35%, so I attempted to reboot the machine. When I did so, I was greeted with a black screen saying: EEPROM: failed() FPGA: failed() ds2301: failed() I was then able to press any key to exit the failure screen and arrive at the main UI. However, now the tool will no longer output anything. I attempted to update the firmware via USB flash drive, and it successfully read the device and rebooted, but I still arrived at the failure screen. I've seen somewhere else that people have had to open up their devices and reflash an internal SD card, or something. Does anybody know anything about that? Thanks - Omega Glory --- End quote --- Please don't at this time. Contact me via PM with your email and we'll try the Siglent USB recovery package. |
| Omega Glory:
Thank you very much, the recovery files worked perfectly and smoothly! I really appreciate your help. - Omega Glory |
| tautech:
:-+ Do you know what FW version was in use when you had these troubles ? Trusting you have also checked the latest version is now installed ? |
| Omega Glory:
Before I bricked it, I had updated to the latest version (1.01.01.33R3). Before that update, I don't recall which version it was, but I believe it was just the previous version (1.01.01.33R1B10). After I updated to the newest version, I didn't have a problem until I attempted to move a waveform over from my scope to the signal gen. Yes, now after things have been recovered, I am running (1.01.01.33R3). I suppose I could see if I can reproduce the error (though even though I have the recovery tools you sent me, somehow this doesn't seem like the wisest decision...). |
| Navigation |
| Message Index |
| Next page |