Siglent SDS1102CML+ non-responsive: Any ideas?

[dclaar]

I have a SDS1102CML+, about 3 years old. Hadn't used it in a while, and when I fired it up, it was non-responsive:
None of the buttons or knobs work.

I can connect via rs-232 and EasyScopeX, but none of the commands (e.g. *RST) do anything. Plugging in a USB drive gets a response on the screen that it was plugged in, but I can't do anything with it.

I tried the "hit the math button a bunch of times at boot", but--since none of the buttons work--nothing happened.
I contacted Siglent, and they sent me a zip file "System Recovery by U-disk", but the unit doesn't seem to see the USB drive until it is booted, and doesn't read the files. They said that I should just use a FAT-formatted USB drive, which I did.

Any ideas? At this point it is pretty much a paperweight. Siglent will take a look at this $300 scope for only $200 + S&H.

I've included a picture of what's on the screen after it boots.

Thanks! [ Attachment Invalid Or Does Not Exist ]

[tautech]

I have a SDS1102CML+, about 3 years old. Hadn't used it in a while, and when I fired it up, it was non-responsive:
None of the buttons or knobs work.

I can connect via rs-232 and EasyScopeX, but none of the commands (e.g. *RST) do anything. Plugging in a USB drive gets a response on the screen that it was plugged in, but I can't do anything with it.

I tried the "hit the math button a bunch of times at boot", but--since none of the buttons work--nothing happened.
I contacted Siglent, and they sent me a zip file "System Recovery by U-disk", but the unit doesn't seem to see the USB drive until it is booted, and doesn't read the files. They said that I should just use a FAT-formatted USB drive, which I did.

Any ideas? At this point it is pretty much a paperweight. Siglent will take a look at this $300 scope for only $200 + S&H.

I've included a picture of what's on the screen after it boots.

Thanks! (Attachment Link)

Welcome to the forum.

Any ideas?

A few.

First the USB drive should be formatted as FAT32. Please confirm.

the unit doesn't seem to see the USB drive until it is booted, and doesn't read the files.

Do you have an activity LED in the USB drive in order to see this ?

Did you take note the recovery package instructions say not to use a 16GB stick ?

Do you have proof of purchase date for a possible warranty claim just in case USB recovery fails ?

[dclaar]

I used a 1GB drive, FAT32 formatted. It has a little light on it (those are getting harder to find!), and that light starts blinking very late in the boot process, a split second before the "stuck display" image and USB drive recognition pop-up comes up.

I would expect it to hit the drive a lot earlier in the process if it were going to recover the unit, but that's just based on other small systems, not on any real-world experience with this unit.

As the unit was purchased in Dec 2016, it is a few months out of warranty.

[tautech]

I used a 1GB drive, FAT32 formatted. It has a little light on it (those are getting harder to find!), and that light starts blinking very late in the boot process, a split second before the "stuck display" image and USB drive recognition pop-up comes up.

I would expect it to hit the drive a lot earlier in the process if it were going to recover the unit, but that's just based on other small systems, not on any real-world experience with this unit.

As the unit was purchased in Dec 2016, it is a few months out of warranty.

OK good you've done everything correct. 
I guess you tried more than once.

Send me the SN# via PM and I'll make some inquiries.

[dclaar]

Sent PM. Thanks for your help!

[StillTrying]

Did you ever get it working, or have you now got a fancy door stop.

[dclaar]

Nah, even though I got it for Christmas--and it was slightly out of the 3 years--they said that it was manufactured earlier, so they wouldn't extend the warranty.

This is where I feel like a bit of a chump. If I would have "jailbroken" the scope and helped myself to the advanced features and enhanced speed, I would probably have a better chance at recovery: At least, I might be able to login and poke around. But I respected their business model, and now I'm hosed. I mean, they are totally within their rights to respond as they did, but I'm bummed.

[StillTrying]

"it was slightly out of the 3 years--they said that it was manufactured earlier"
"As the unit was purchased in Dec 2016"

Mine was bought (in the UK) around 6 weeks before yours, shall we compare serial numbers.

As you seem to have nothing to lose I assume you've tried all the MATH pressing, it's probably worth carefully opening it and checking for at least the very basics, such as a loose data or even power cable.

[tv84]

If you have nothing to loose, I suggest opening it and try find a UART output to see any boot log.

Don't remember if these BF machines have boot log... must be from the virus. 

[NoisyBoy]

And it all else fails, and the scope is otherwise in good shape, sell it to someone who may be able to fix it and recoup some of your cost so it is not a total lost. 

Sorry to hear about this happening to you, hope you can find a quick resolution.

[BobRyan]

If you have nothing to loose, I suggest opening it and try find a UART output to see any boot log.

Don't remember if these BF machines have boot log... must be from the virus. 

I couldn't find any serial output from mine

[ratmole]

If anyone has problems with stuck logo on boot, try this:

1. Remove the back cover of the SDS1102CML+ oscilloscope,
2, Remove the metal back of the cage
3. Connect RX,TX serial cables on the unpopulated J11 connector. Solder TX to the second pad and RX to the third pad.
4. Connect to serial: Baudrate 115200
5. Boot the oscilloscope, now you will see the boot log. If not, swap the RX,TX cables to your serial adaptor.
6. Unzip the contents of the P21R2.zip in a fat32 formated usb stick. Also unzip the SDS1000_arm.zip and copy the SDS1000_arm.app to the root of the usb flash drive.
7. Connect the usb flash drive to the oscilloscope and power off and the on the oscilloscope.
8. Let the oscilloscope to perform the FW Recovery.
9. Remove the usb flash drive and Reboot
10. done!

If  the oscilloscope still hangs on the boot logo
Start the oscilloscope without the usb flash drive.
When the boot is complete, but still on logo
Insert the usb flash drive and type in the serial console:

Code: [Select]

mount /dev/sda1 /mnt
mount / -o remount,rw
cp /mnt/SDS1000_arm.app /usr/bin/siglent/SDS1000_arm.app
chmod +x  /usr/bin/siglent/SDS1000_arm.app
mkdir -p /usr/bin/siglent/firmdata0/usr/log
cd /usr/bin/siglent/
./SDS1000_arm.app
Now the oscilloscope is back to life!
Please perform a hardware reset using the Math button method and you are good as new.

a big thanks to tv84 and tautech for their help!

[nvincis88]

Hello,

I have same issue, the oscilloscope still hangs on the boot logo.

I tried the instruction above, but nothing succed.

The "SDA1" folder doesn't exist into the "/dev" folder.

Below you can see the log of boot.

Thanks a lot

Code: [Select]

U-Boot 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)

I2C:   ready
DRAM:  128 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

set_default_env::7864
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
(Re)start USB...
USB0:   scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Download Linux from USB to Nandflash...
reading ro_uImage
2157832 bytes read in 1295 ms (1.6 MiB/s)

NAND erase: device 0 offset 0x3080000, size 0x500000
Erasing at 0x3560000 -- 100% complete.
OK

NAND write: device 0 offset 0x3080000, size 0x500000
 5242880 bytes written: OK
reading rootfs.img
** Unable to read file rootfs.img **
reading datafs.img
2097152 bytes read in 1273 ms (1.6 MiB/s)

NAND erase: device 0 offset 0x9a80000, size 0x6580000
Erasing at 0xffe0000 -- 100% complete.
OK

NAND write: device 0 offset 0x9a80000, size 0x1500000
 22020096 bytes written: OK
reading logo.bmp
** Unable to read file logo.bmp **
Booting from nand ...

NAND read: device 0 offset 0x3080000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.2.0+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2157768 Bytes = 2.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)
starting pid 519, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/ # check_and_upgrade:starting...
mount_fs: rw,sync,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,sync,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear


[conair7]

Hi,

I'm facing similar problem with the SDS1102CML+ device, but when it's boot (Siglent logo on screen) it hangs on:

Code: [Select]

Starting kernel ...
Uncompressing Linux... done, booting the kernel.
The USB is not powered up, internal green led blinking.
I'm aware of this thread: https://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/ but he firmware was not updated since the purchase (~2018).

[9a5n]

I have similar problem with SDS1050DL+.
Unit works well for many year (from 2016.) until a few days ago.

After boot finish, everything working well for 5-6 seconds and then screen and keys hang.
I contacted Siglent, and they sent me a zip file "System Recovery by U-disk".
I found some old 4GB USB drive and format it in FAT32.
3 files from zip has been copied to root.
After power on, the unit doesn't seem to see the USB drive during boot.
LED on USB drive start to blink when boot finish and unit came in operation.
Of coarse, after 5 seconds screen freeze and keys not working anymore.

From system status I read out:
Software Version 6.02.01.02      50M
Hardware Version 0-64-3.0
Serial No. SDS10BA1160348

What I am doing wrong?

[tv84]

1. Change USB disk and repeat.
2. If it fails again, go to 1.

[tautech]

USB drives must be FAT32 with 4K clusters and bootable.

If nothing works you might need the MicroSD card recovery package from Siglent……much more involved to implement…….main board soldering required but results are very reliable.

[9a5n]

In Siglent instructions those details are not written.
FAT32 is not a problem.
4K clusters is not a problem.
However, how to make Linux bootable drive on Windows without some ISO file?

[Antonio90]

Rufus has worked quite well for me. AFAIK, bootable has nothing to do with the operating system anyway, it's checked at boot, way before loading the OS.

EDIT: https://rufus.ie/

[tv84]

In Siglent instructions those details are not written.
FAT32 is not a problem.
4K clusters is not a problem.
However, how to make Linux bootable drive on Windows without some ISO file?

   It's not supposed for the drive to be bootable. The remaining bootloader (in the machine) must be able to recognize the USB disk files and go from there. If your bootloader is in a state of incapability, not common, then you won't be able to do anything.

[9a5n]

So I have to find a USB drive that the bootloader will recognize.

[tautech]

So I have to find a USB drive that the bootloader will recognize.

Having assisted with many recoveries, when it’s a straightforward recovery which previous FW supports, not all USB sticks even when configured correctly will recover the instrument.
Another error that is sometimes made is not having the recovery files in the root folder of the USB stick.

In my generic instructions I also warn that a new USB stick might be required for recovery to be successful.

[tautech]

@All
Member contacted me today informing the 10th USB stick they tried successfully recovered their scope.

Why, IDK, maybe PC OS used but goes to show that when everything lines up successful USB recovery is simple.

[9a5n]

During boot, the USB port seems dead.
There is no indication that the bootloader wants to access the USB port and the attached stick.
The LED on the stick does not blink even once.
Isn't it expected that the bootloader tries to access the USB port and connected stick?

When the boot finishes and the oscilloscope starts working, the USB port also starts working and reports that the USB stick is connected.
Of course, after a few seconds everything freezes.

[tautech]

During boot, the USB port seems dead.
There is no indication that the bootloader wants to access the USB port and the attached stick.
The LED on the stick does not blink even once.
Isn't it expected that the bootloader tries to access the USB port and connected stick?

When the boot finishes and the oscilloscope starts working, the USB port also starts working and reports that the USB stick is connected.
Of course, after a few seconds everything freezes.

The now very old 6.02.01.02 FW likely does not support recovery.

Instead we need use SD card recovery and the unit needs be opened to access the SD card slot.
Send me PM with your email.