Products > Test Equipment
Siglent SDS1102CML+ is not working
(1/1)
irato:
Hi.
My scope is stucked on booting screen, I tried the "hit the math button" but it didn't work.
Any ideas?
Thanks.
smittyinthesky:
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: 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 1300 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 1266 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
Bus error
mount: mounting none on /sys/kernel/debug failed: No such file or directory
mdev: /sys/block: No such file or directory
mdev: /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/null
can't open /dev/ttyO0: No such file or directory
/etc/init.d/rcS: line 24: can't open /dev/null
process '-/bin/sh' (pid 535) exited. Scheduling for restart.
can't open /dev/ttyO0: No such file or directory
process '-/bin/sh' (pid 536) exited. Scheduling for restart.
can't open /dev/ttyO0: No such file or directory
--- End code ---
I'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?
Navigation
[0] Message Index
Go to full version