Help restore SDS1102CML+ after unsuccessful flashing

[tautech]

Hi. 

I’m also new to the forum, however long time viewer of Dave’s YouTube channels. I’m only a bit of a hobbyist & recently when I tried to use my Jaycar QC1934 oscilloscope I have also fallen victim to the “Stuck on Splash Screen” issue that has been discussed in this forum. I have never updated the firmware and seemed to work fine for the last 3 or 4 years.

I believe it is actually the siglent sds1102 cml plus, correct me if I’m wrong Ref attached photos. No relays click just splash screen, Repeatedly pressing math button doesn’t do anything. Just all buttons lit up and a led inside pulsing. It has a sd card slot, lan port, usb, bnc connector & an unpopulated J11 pads.

I have tried to contacting siglent for support, the American address info@siglent.com keeps bouncing back, no reply from the other 2 email addresses.

Any help would be greatly appreciated. TIA

Welcome to the forum.

Indeed it does seem like a SDS1102CML+ and info from here confirms it has 2Mpts mem depth as CML models do.
https://www.jaycar.co.nz/7-screen-100mhz-dual-channel-dso/p/QC1934

Send me a PM with your email address.

[dwhp]

Tautech thankyou thankyou thankyou   . I have followed your instructions and now all back up and running again. Including updated to most recent firmware. Couldn’t be happier.

[tautech]

Tautech thankyou thankyou thankyou   . I have followed your instructions and now all back up and running again. Including updated to most recent firmware. Couldn’t be happier.

You're welcome D, enjoy.
This wasn't as straightforward as many as I suspect QC1934 firmware was some early version that didn't support USB recovery however the somewhat more involved MicroSD card recovery did the trick. 

[aniko71]

I have a Siglent 1102CML+ which is stuck on logo. I need some info from @tautech to help me restore it like so many other happy users here. Thank you.

[cmmodem]

Hello and good morning.. Where I teach we have a sds 1102cml+ oscilloscope that does not start and remains with the black screen of the logo. I would appreciate help to repair it, since the warranty date has passed. I have connected through the terminal and this is what appears:

Code: [Select]

U-Boot SPL 2013.01.01-svn72327 (Jun 02 2021 - 18:19:21)
config ddr_pll_config()++
config ddr_pll_config()--
********am33xx_spl_board_init=720**************
*********mpu_pll=720**************
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn72327 (Jun 02 2021 - 18:19:21)

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

set_default_env::7914
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:   lowlevel init failed
USB error: all controllers failed lowlevel init
Download Linux from USB to Nandflash...
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
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
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
/etc/init.d/sysfs.sh: line 17: can't create /proc/sys/kernel/hotplug: nonexistent directory
Segmentation fault
Segmentation fault
/etc/init.d/rcS: line 11: can't create /sys/class/gpio/export: nonexistent directory
/etc/init.d/rcS: line 12: can't create /sys/class/gpio/gpio113/direction: nonexistent directory
/etc/init.d/rcS: line 13: can't create /sys/class/gpio/gpio113/value: nonexistent directory
/etc/init.d/rcS: line 15: setterm: not found
/etc/init.d/rcS: line 18: can't open /dev/null
can't open /dev/ttyO0: No such file or directory
/etc/init.d/rcS: line 24: can't open /dev/null
/etc/init.d/rcS: line 21: can't open /dev/null
process '-/bin/sh' (pid 533) exited. Scheduling for restart.
can't open /dev/ttyO0: No such file or directory
process '-/bin/sh' (pid 534) exited. Scheduling for restart.
can't open /dev/ttyO0: No such file or directory
process '-/bin/sh' (pid 535) exited. Scheduling for restart.
can't open /dev/ttyO0: No such file or directory
Thanks for the help!

Tautech , Thank you so much for the help! The oscilloscope has come back to life!! Awesome!

[eeKnud]

Big thanks to ratmole for putting me on the right track to get past the splash screen on an SDS1052DL+.

For those interested, I did these steps:

1. Opened the case to get at the main board.
2. Connected a serial console to J11 and confirmed that the unit was trying to boot. (I had right-angle 0.1" headers, so just soldered one on and used jumper wires to connect to an Arduino running serial passthrough)
3. Compared ratmole's SDS1000_arm.app to the one in /usr/bin/siglent/ and seeing they were different, thought what the heck, try it. Put it on a USB stick, mounted, copied to /usr/bin/siglent/ and chmod +'d it.
4. Reboot (from the command line via serial or via the power switch, both work) and removed the USB stick during.
5. Scope now got past the splash screen, but the display was funky; the signal traces were in an odd state/configuration.
6. Put the latest ADS from SDS1000DL+_V6.02.01.13_EN on the USB stick
7. Put the scope into firmware update mode, inserted USB stick, and selected the ADS file.
8. Watched update on the scope and via the serial console. Lots of output, but completed successfully.
9. Enjoyed a happy scope

Todo : give scope to my son for his shop.

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!

[va_user_2024]

Hello - New to this forum. I have a Siglent 1102CML+ that is stuck on the splash screen. I tried inserting USB stick with downloaded firmware from Siglent in the front of the unit per Siglent's instruction. But, this unit is still only showing the splash screen and hanging.  Any help is greatly appreciated as this unit has only been using about an hour over it's lifetime and I would like to get it running again. There was no reason for it to stop working (not dropped or damaged in any way). So any help is very much appreciated to help get it up and running again. Thank you. By the way, I did not see a prompt on this forum to add a new topic so I am posting here because it seems the closest to my issue (same Siglent model with a stuck boot process).

[Strateg58]

Hi guys. I want to update the firmware of my Siglent SDS1102CML oscilloscope. But I'm afraid to get a brick. Does anyone have any sensible instructions on how to flash it? From a USB stick or from a Windows 10 laptop?

[tautech]

Hi guys. I want to update the firmware of my Siglent SDS1102CML oscilloscope. But I'm afraid to get a brick. Does anyone have any sensible instructions on how to flash it? From a USB stick or from a Windows 10 laptop?

Plus model ?
Latest/last firmware version:
https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS1000CML+_V6.01.01.25_EN.zip

Unzip and study the PDF.

[Strateg58]

No, not +. Where can I get the latest firmware?

[tautech]

No, not +. Where can I get the latest firmware?

No longer available from Siglent websites.

Which version are you on as we may have a later version we can upload here buried in the archives.

[Strateg58]

No, not +. Where can I get the latest firmware?

No longer available from Siglent websites.

Which version are you on as we may have a later version we can upload here buried in the archives.

[tautech]

No, not +. Where can I get the latest firmware?

No longer available from Siglent websites.

Which version are you on as we may have a later version we can upload here buried in the archives.

.32 attached for old CML models

[Strateg58]

Thanks.

[tautech]

Thanks.

Sorry forgot to mention it's a zipped RAR folder so you'll need to unpack it twice.