Siglent SDS1102CML+ is not working - Page 1
Forum section: electronics / testgear

author: irato
author_rank: Newbie
timestamp: December 06, 2022, 11:08:07 pm
content: Hi.My scope is stucked on booting screen, I tried the "hit the math button" but it didn't work.Any ideas?Thanks.

author: smittyinthesky
author_rank: Newbie
timestamp: July 16, 2023, 01:52:32 pm
content: I've got this same problem. I think it's related to a bad firmware flash.I've tried, unsuccessfully, the USB boot method described by tautech here:https://www.eevblog.com/forum/testgear/siglent-sds1052dl-stuck-in-startup/My error message is (w/ recovery USB attached to front of device):Code: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 1300 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 1266 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 inBus errormount: mounting none on /sys/kernel/debug failed: No such file or directorymdev: /sys/block: No such file or directorymdev: /sys/class: No such file or directory/etc/init.d/rcS: line 11: can't create /sys/class/gpio/export: nonexistent direc tory/etc/init.d/rcS: line 12: can't create /sys/class/gpio/gpio113/direction: nonexi stent directory/etc/init.d/rcS: line 13: can't create /sys/class/gpio/gpio113/value: nonexisten t directory/etc/init.d/rcS: line 15: setterm: not found/etc/init.d/rcS: line 18: can't open /dev/null/etc/init.d/rcS: line 21: can't open /dev/nullcan't open /dev/ttyO0: No such file or directory/etc/init.d/rcS: line 24: can't open /dev/nullprocess '-/bin/sh' (pid 535) exited. Scheduling for restart.can't open /dev/ttyO0: No such file or directoryprocess '-/bin/sh' (pid 536) exited. Scheduling for restart.can't open /dev/ttyO0: No such file or directoryI'm not sure what would cause this. Not seeing this exact error anywhere else. Looks like I've lost a serial port or GPIO interface?