Siglent SDS1102CML+ non-responsive: Any ideas? - Page 1
Forum section: electronics / testgear

author: dclaar
author_rank: Newbie
timestamp: March 08, 2020, 01:25:08 am
content: 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 foronly$200 + S&H.I've included a picture of what's on the screen after it boots.Thanks! [ Attachment Invalid Or Does Not Exist ]

author: tautech
author_rank: Super Contributor
timestamp: March 08, 2020, 07:08:26 am
content: Quote from: dclaar on March 08, 2020, 01:25:08 amWelcome to the forum.QuoteA few.First the USB drive should be formatted as FAT32. Please confirm.QuoteDo 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 ?

author: dclaar
author_rank: Newbie
timestamp: March 08, 2020, 11:18:52 pm
content: 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 withthisunit.As the unit was purchased in Dec 2016, it is a few months out of warranty.

author: tautech
author_rank: Super Contributor
timestamp: March 08, 2020, 11:45:36 pm
content: Quote from: dclaar on March 08, 2020, 11:18:52 pmOK 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.

author: dclaar
author_rank: Newbie
timestamp: March 09, 2020, 02:40:11 am
content: Sent PM. Thanks for your help!

author: StillTrying
author_rank: Super Contributor
timestamp: March 14, 2020, 02:36:29 pm
content: Did you ever get it working, or have you now got a fancy door stop.

author: dclaar
author_rank: Newbie
timestamp: March 17, 2020, 02:35:13 am
content: 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.

author: StillTrying
author_rank: Super Contributor
timestamp: March 17, 2020, 08:44:26 am
content: "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.

author: tv84
author_rank: Super Contributor
timestamp: March 17, 2020, 10:57:59 am
content: 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.

author: NoisyBoy
author_rank: Frequent Contributor
timestamp: March 17, 2020, 05:31:33 pm
content: 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.

author: BobRyan
author_rank: Contributor
timestamp: March 17, 2020, 05:51:24 pm
content: Quote from: tv84 on March 17, 2020, 10:57:59 amI couldn't find any serial output from mine

author: ratmole
author_rank: Contributor
timestamp: February 10, 2021, 07:17:00 pm
content: 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 cage3. 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 1152005. 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 Reboot10. done!If the oscilloscope still hangs on the boot logoStart the oscilloscopewithout the usb flash drive.When the boot is complete, but still on logoInsert the usb flash drive and type in the serial console:Code:mount /dev/sda1 /mntmount / -o remount,rwcp /mnt/SDS1000_arm.app /usr/bin/siglent/SDS1000_arm.appchmod +x /usr/bin/siglent/SDS1000_arm.appmkdir -p /usr/bin/siglent/firmdata0/usr/logcd /usr/bin/siglent/./SDS1000_arm.appNow 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!

author: nvincis88
author_rank: Newbie
timestamp: April 21, 2021, 04:24:53 pm
content: 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 lotCode:U-Boot 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7864musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)musb-hdrc: MHDRC RTL version 2.0musb-hdrc: setup fifo_mode 4musb-hdrc: 28/31 max ep, 16384/16384 memoryUSB Peripheral mode controller at 47401000 using PIO, IRQ 0musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)musb-hdrc: MHDRC RTL version 2.0musb-hdrc: setup fifo_mode 4musb-hdrc: 28/31 max ep, 16384/16384 memoryUSB Host mode controller at 47401800 using PIO, IRQ 0Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autoboot(Re)start USB...USB0: scanning bus 0 for devices... 1 USB Device(s) foundscanning usb for storage devices... 1 Storage Device(s) foundDownload Linux from USB to Nandflash...reading ro_uImage2157832 bytes read in 1295 ms (1.6 MiB/s)NAND erase: device 0 offset 0x3080000, size 0x500000Erasing at 0x3560000 -- 100% complete.OKNAND write: device 0 offset 0x3080000, size 0x5000005242880 bytes written: OKreading rootfs.img** Unable to read file rootfs.img **reading datafs.img2097152 bytes read in 1273 ms (1.6 MiB/s)NAND erase: device 0 offset 0x9a80000, size 0x6580000Erasing at 0xffe0000 -- 100% complete.OKNAND write: device 0 offset 0x9a80000, size 0x150000022020096 bytes written: OKreading logo.bmp** Unable to read file logo.bmp **Booting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 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 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting 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 foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ # check_and_upgrade:starting...mount_fs: rw,sync,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI 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/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,sync,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI 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/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Success!Erasing 128 Kibyte @ 20000 -- 100 % completeThe Help file load OK!!terminate called after throwing an instance of 'std::ios_base::failure'what(): basic_ios::clear

author: conair7
author_rank: Newbie
timestamp: October 12, 2022, 06:48:09 pm
content: Hi,I'm facing similar problem with the SDS1102CML+ device, but when it's boot (Siglent logo on screen) it hangs on:Code: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).

author: 9a5n
author_rank: Newbie
timestamp: January 03, 2024, 06:59:40 pm
content: 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 50MHardware Version 0-64-3.0Serial No. SDS10BA1160348What I am doing wrong?

author: tv84
author_rank: Super Contributor
timestamp: January 03, 2024, 07:02:10 pm
content: 1. Change USB disk and repeat.2. If it fails again, go to 1.

author: tautech
author_rank: Super Contributor
timestamp: January 03, 2024, 10:40:38 pm
content: 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.

author: 9a5n
author_rank: Newbie
timestamp: January 04, 2024, 10:10:16 am
content: 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?

author: Antonio90
author_rank: Frequent Contributor
timestamp: January 04, 2024, 10:45:20 am
content: 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/

author: tv84
author_rank: Super Contributor
timestamp: January 04, 2024, 11:28:25 am
content: Quote from: 9a5n on January 04, 2024, 10:10:16 amIt'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.

author: 9a5n
author_rank: Newbie
timestamp: January 04, 2024, 07:20:17 pm
content: So I have to find a USB drive that the bootloader will recognize.

author: tautech
author_rank: Super Contributor
timestamp: January 05, 2024, 01:14:05 am
content: Quote from: 9a5n on January 04, 2024, 07:20:17 pmHaving 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.

author: tautech
author_rank: Super Contributor
timestamp: January 11, 2024, 09:23:51 am
content: @AllMember 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.

author: 9a5n
author_rank: Newbie
timestamp: January 21, 2024, 11:19:26 am
content: 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.

author: tautech
author_rank: Super Contributor
timestamp: January 21, 2024, 07:33:44 pm
content: Quote from: 9a5n on January 21, 2024, 11:19:26 amThe 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.

author: 9a5n
author_rank: Newbie
timestamp: February 05, 2024, 04:09:04 pm
content: tatech,thank you very much for your help!SC card recovery was successful.

author: Rodrigo
author_rank: Newbie
timestamp: March 12, 2025, 12:24:22 am
content: Hi, i have the same problem with my scope.tried the math button method with no succes.can you pls help me?thanks.

author: tautech
author_rank: Super Contributor
timestamp: March 12, 2025, 12:34:49 am
content: Quote from: Rodrigo on March 12, 2025, 12:24:22 amWelcome to the forum.NA branch in Ohio can send you the recovery package:support@siglentna.comCome back and tell us how things went.

author: spyderbdm
author_rank: Newbie
timestamp: May 25, 2025, 07:40:35 pm
content: Thank you for your post. I feel like I’m really close to getting my scope back, but when I run the “mkdir” command, it says the file system is read-only. When I execute the SDS1000_arm.app file, It says “Bus error”. I had to wire GND of jumper J11 to my serial-to-usb converter to get serial to work, but left off the 5V; only TX, RX, and GND. Any ideas?

author: tautech
author_rank: Super Contributor
timestamp: May 25, 2025, 07:58:26 pm
content: Quote from: spyderbdm on May 25, 2025, 07:40:35 pmAnswered you call for help in another thread.Don't go mucking with the HW but instead get the USB recovery package from Ohio branch.

author: spyderbdm
author_rank: Newbie
timestamp: May 26, 2025, 12:07:22 pm
content: Roger, will-co. Dropped them another email, but via the Website this time. Will post updates should they reply to this one. Thanks for letting me know this is do-able via usb.

author: spyderbdm
author_rank: Newbie
timestamp: May 27, 2025, 05:27:28 pm
content: Got a reply from Siglent North America today with the USB recovery files. They did the trick. Instructions say it takes about three minutes, but it really only took about one. I asked if I can share the files, because I was unable to find them anywhere, but email footer says I can’t. We’ll see what they say. Thank you @tautech. Wish I would’ve waited to break the seal, but it’s honestly worthless this long after manufacture anyway. Would definitely wait to see if USB recovery works before doing anything else; assuming spamming the Test button didn’t work. It may at least keep the re-sell value higher.USB flash drive used = 2GB PNY Optima Pro Attaché, formatted as FAT32.

author: tautech
author_rank: Super Contributor
timestamp: May 27, 2025, 08:08:49 pm
content: Quote from: spyderbdm on May 27, 2025, 05:27:28 pmPlease don't shareanyrecovery packages.You should now be on Version： V6.01.01.25 FW/SW, the last for CML+ models.Check Sys Info that you are and if necessary update further from here:https://int.siglent.com/download/firmwares/?ProId=40

author: Alex2309
author_rank: Newbie
timestamp: August 11, 2025, 12:04:49 pm
content: Hello, is any help still available? SDS 1102CNL+ stuck on boot (

author: tautech
author_rank: Super Contributor
timestamp: August 11, 2025, 09:04:12 pm
content: Quote from: Alex2309 on August 11, 2025, 12:04:49 pmWelcome to the forum.As you're showing a US flag please contact the NA branch:support@siglentna.com

author: Alex2309
author_rank: Newbie
timestamp: August 12, 2025, 07:10:27 am
content: I have changed the flag - VPN issue

author: tautech
author_rank: Super Contributor
timestamp: August 12, 2025, 07:13:48 am
content: Quote from: Alex2309 on August 12, 2025, 07:10:27 amWe have never supplied a Alex with a CML+ model.See your PM.