Help restore SDS1102CML+ after unsuccessful flashing

[Zhenja]

After an erroneous firmware, the device turned into almost a brick.
I opened the device, found UART and looked at what was going on inside the device. The bottom line is that the application /usr/bin/siglent/SDS1000_arm.app responsible for the operation of the device crashes with an error:

Code: [Select]

/ # check_and_upgrade:starting...
mount_fs: rw,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,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!
The Help file load OK!!
Could not create log file: File exists
COULD NOT CREATE LOGFILE '19700101-000005.534'!
I0101 00:00:05.250442   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.271838   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:00:05.476723   534 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 5583
sh: portmap: Structure needs cleaning
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!

To flash the device again, there are 2 ways:
1) Run the "native" application for this device, for example with a USB flash drive - but where can I get it?
2) Find somewhere a memory dump with working firmware and upload it to my chip using the programmer. But where to get the dump?

Perhaps someone has experience in this task. Or other thoughts - how to solve this problem.

I downloaded the program: SDS_ads_014 (it seems to be the latest version - I wanted to use it to distribute the application from the ads firmware), but this software does not read the latest firmware

Please help to resurrect the device.

Update 05.03.2020

I would like to report that my problem has been resolved! This happened thanks to the efforts of the user tautech!
Thanks a lot to him! It was he who helped contact the manufacturer and get a new board. This procedure took several months and there were all sorts of attempts to restore my board and other problems BUT it was worth it!
As a result, I received a new motherboard!
This event took place in mid-January 2020, but I was able to report this only now.
I was able to assemble and restore the operation of my device!
Advice to others: if you encounter a problem, do not hesitate to contact the manufacturer to solve your problem! Most likely a solution will be found! As it was in my case.

[tv84]

What .ADS did you flash?

[Zhenja]

Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

The device has accepted the firmware. The device has been flashed. And after rebooting, there is nothing but a splash screen ... the probability of error is minimal, but the device turned into a brick. Or did I still upload the wrong firmware?

The file was named like this: SDS1000CML + _6.01.01.21R2.ADS

Now I don’t know what to do ... I really do not want to buy a new one. I believe that there is a way to restore it to work.

At least there are several service recovery methods in the bootloader, but I do not have the necessary files. Maybe someone has them ...

PS
Is there any way to see which firmware is actually uploaded? Maybe this information is in some kind of file? Maybe I'm really mistaken that the exact firmware I am writing about is uploaded.

I am ready for almost any experiment. The only thing I would like to first sort through all the software solutions to the problem and only then move on to hardware methods.

[Zhenja]

This is how the full load of the device from the moment of power supply looks:

Code: [Select]

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
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

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,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,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!
The Help file load OK!!
Could not create log file: File exists
COULD NOT CREATE LOGFILE '19700101-000005.534'!
I0101 00:00:05.193285   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.214703   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:00:05.419588   534 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 5542
sh: portmap: Structure needs cleaning
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!
/ #


If during boot, use any key, then we get into the bootloader. In which you can see all the download options provided in it:

Code: [Select]

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
U-Boot# printenv
a=echo tftp download MLO,u-boot.img,uImage,ubi.img image fpga nand ...; run m; run u; run k; run f; run b; run r; run d
arch=arm
b=echo tftp download logo.bmp to nand ...; tftp 0x83000000 logo.bmp; bmpload 0x82000000 0x83000000; nand erase 0x280000 0x300000; nand write.i 0x82000000 0x280000 0x300000; mw.b 0x82000000 0x0 0x300000
baudrate=115200
board=sds1000a
board_name=A335X_SK
board_rev=1.0A
bootargs_defaults=setenv bootargs console=${console} ${optargs}
bootcmd=if run nandboot; then;elif mmc rescan; then echo SD/MMC found on device ${mmc_dev};if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run mmc_load_uimage; then run mmc_args;bootm ${kloadaddr};fi;fi;
bootdelay=1
bootenv=uEnv.txt
bootfile=uImage
console=ttyO0,115200n8
cpu=armv7
d=echo Upgrade the datafs.img by tftp ...; mw.b 0x82000000 0x0 0x2800000; if tftp 0x82000000 datafs.img; then nand erase 0x9a80000 0x6580000; nand write.i 0x82000000 0x9a80000 0x1500000; mw.b 0x82000000 0x0 0x1500000; fi
dfu_alt_info_emmc=rawemmc mmc 0 3751936
dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100 100;u-boot.img.raw mmc 300 3C0;u-boot.img fat 0 1;uEnv.txt fat 0 1
dfu_alt_info_nand=SPL part 0 1;SPL.backup1 part 0 2;SPL.backup2 part 0 3;SPL.backup3 part 0 4;u-boot part 0 5;rootfs part 0 8;kernel part 0 9
ethact=cpsw
ethaddr=60:64:05:37:5a:0c
f=echo Upgrade the rootfs.img by tftp ...; mw.b 0x82000000 0x0 0x2b00000; if tftp 0x82000000 rootfs.img; then nand erase 0x580000 0x2b00000; nand write.i 0x82000000 rootfs; mw.b 0x82000000 0x0 0x2b00000; fi
fdt_high=0xffffffff
fdtaddr=0x80F80000
findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name = A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi
gatewayip=10.11.13.1
i=echo Upgrade the image by tftp ...; if tftp 0x82000000 image; then nand erase 0x280000 0x300000; nand write.i 0x82000000 Manufacturedata; mw.b 0x82000000 0x0 0x300000; fi
importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize
ip_method=none
ipaddr=10.11.13.250
k=echo Upgrade the uImage by tftp ...; if tftp 0x82000000 uImage; then nand erase 0x3080000 0x600000; nand write.i 0x82000000 kernel; mw.b 0x82000000 0x0 0x600000; fi
kloadaddr=0x80007fc0
loadaddr=0x80200000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=ext2load mmc ${mmcdev}:2 ${kloadaddr} /boot/${bootfile}
loaduimagefat=fatload mmc ${mmcdev} ${kloadaddr} ${bootfile}
m=echo Upgrade the MLO by tftp ...; if tftp 0x82000000 MLO; then nand erase 0x0 0x20000; nand write.i 0x82000000 SPL; mw.b 0x82000000 0x0 0x20000; fi
mmc-all=nand erase.chip; run mmc-m; run mmc-u; run mmc-k; run mmc-rootfs; run mmc-datafs; run mmc-firm; run mmc-l; echo ================mmc-all Done===================;
mmc-datafs=echo =============datafs(datafs.img)=====================; echo [fatload mmc, download datafs to nand ...]; if fatload mmc 0 0x82000000 datafs.img; then nand erase 0x9a80000 0x6580000; nand write.i 0x82000000 0x9a80000 0x1500000; mw.b 0x82000000 0x0 0x1500000; fi;
mmc-firm=echo =============firmdata0(firmdata0.img)=====================; echo [fatload mmc, download firmdata0 to nand ...]; if fatload mmc 0 0x82000000 firmdata0.img; then nand erase 0x3680000 0x3200000; nand write.i 0x82000000 0x3680000 0x3200000; mw.b 0x82000000 0x0 0x3200000; fi;
mmc-k=echo =============kernel(uImage)======================; echo [fatload mmc, download kernel to nand ...]; if fatload mmc 0 0x82000000 uImage; then nand erase 0x3080000 0x500000; nand write.i 0x82000000 0x3080000 0x500000; mw.b 0x82000000 0x0 0x500000;fi;
mmc-l=echo =============logo(logo.bmp)=======================; mmc rescan; echo [fatload mmc, download logo to nand ...]; if fatload mmc 0 0x83000000 logo.bmp; then bmpload 0x82000000 0x83000000; nand erase 0x280000 ${filesize}; nand write.i 0x82000000 0x280000 ${filesize}; mw.b 0x82000000 0x0 ${filesize};mw.b 0x83000000 0x0 ${filesize};fi;
mmc-m=echo ===================MLO(MLO)======================; echo [fatload mmc, download MLO to nand ...]; if fatload mmc 0 0x82000000 MLO; then nand erase 0x0 0x20000; nand write.i 0x82000000 0x0 0x20000; mw.b 0x82000000 0x0 0x20000; fi;
mmc-rootfs=echo =============rootfs(rootfs.img)=====================; echo [fatload mmc, download rootfs to nand ...]; if fatload mmc 0 0x82000000 rootfs.img; then nand erase 0x0580000 0x2B00000; nand write.i 0x82000000 0x0580000 0x1500000; mw.b 0x82000000 0x0 0x1500000; fi;
mmc-u=echo =============u-boot(u-boot.img.program)==========; echo [fatload mmc, download u-boot to nand ...]; if fatload mmc 0 0x82000000 u-boot.img.program; then nand erase 0x80000  0x100000; nand write.i 0x82000000 0x80000 0x100000; mw.b 0x82000000 0x0 0x100000;fi;
mmcargs=run bootargs_defaults;setenv bootargs ${bootargs} root=${mmcroot} rootfstype=${mmcrootfstype} ip=${ip_method}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${kloadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext3 rootwait
mtdids=nand0=omap2-nand.0
mtdparts=mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),3m(Manufacturedata),43m(rootfs),6m(kernel),-(datafs)
nandargs=setenv bootargs console=${console} ${optargs} root=${nandroot} rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} ${nandsrcaddr} ${nandimgsize}; bootm ${loadaddr}
nandimgsize=0x300000
nandroot=ubi0:rootfs rw ubi.mtd=7,2048
nandrootfstype=ubifs rootwait=1
nandsrcaddr=0x3080000
netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
netboot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}
netmask=255.255.255.0
nfsopts=nolock
r=echo Upgrade the firmdata0.img by tftp ...; if tftp 0x82000000 firmdata0.img; then nand erase 0x3680000 0x3200000; nand write.i 0x82000000 0x3680000 0x3200000; mw.b 0x82000000 0x0 0x3200000; fi
ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=${rdaddr},64M
ramrootfstype=ext2
rdaddr=0x81000000
rootpath=/export/rootfs
serverip=10.11.13.19
soc=am33xx
spiargs=setenv bootargs console=${console} ${optargs} root=${spiroot} rootfstype=${spirootfstype}
spiboot=echo Booting from spi ...; run spiargs; sf probe ${spibusno}:0; sf read ${loadaddr} ${spisrcaddr} ${spiimgsize}; bootm ${loadaddr}
spibusno=0
spiimgsize=0x362000
spiroot=/dev/mtdblock4 rw
spirootfstype=jffs2
spisrcaddr=0xe0000
static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
stderr=serial
stdin=serial
stdout=serial
u=echo Upgrade the u-boot.img by tftp ...; if tftp 0x82000000 u-boot.img; then nand erase 0x80000 0x1e0000; nand write.i 0x82000000 u-boot; mw.b 0x82000000 0x0 0x1e0000; fi
vendor=ti
ver=U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)

Environment size: 7391/131068 bytes


It describes different download options from different sources ...
Perhaps this information will be useful.

Any ideas what can be done?

[StillTrying]

Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

I'm glad I haven't tried .21R2 yet.

I am ready for almost any experiment.

There's something about pressing MATH 5 times during power up.

There's only 6 or 7 CML+ posters here, and 3 of them are stuck in some way.

[Zhenja]

Here's what happens after you press MATH:

Code: [Select]

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
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

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,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,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!
format_fs++
Erasing 128 Kibyte @ 6560000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
format_fs--
The system is going down NOW!
Sending SIGTERM to all processes
Requesting system reboot

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
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

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,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,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!
The Help file load OK!!
I0101 00:00:05.855635   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.873046   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:00:06.077378   534 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 6188
sh: portmap: Structure needs cleaning
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!

/ #


that is, it loads, erases some part of the data, then as I understand it, it formats the same area again and reboots. And nothing new is happening. I already tried it repeatedly.

[tv84]

I would say that you have a NAND physical problem. Not a FW issue.

A few days ago another user in the forum solved his problems and he used the latest FW. (He had flashed a wrong FW.)

[Zhenja]

those. do i have a hardware problem? And do I need to replace NAND with another? But where to get the BIN file for flashing the new NAND?

Or did I understand something wrong?

Is there any way to make sure that a replacement for NAND is needed?

PS

I copied SDS1000_arm.app from the device to a USB flash. Counted md 5: 143d81349e8abf7ea799c92f09bfeade

Can someone on the same firmware version calculate their md5 or send me the SDS1000_arm.app file from the same device. I would be very grateful. With it, I could start the device and flash it again with native firmware. Perhaps this would help solve the problem.

Maybe the fact is that the firmware, for some reason, went wrong last time and the second operation will be successful.

[Zhenja]

Tell me, do I think that NAND is precisely this chip on the board?
Or I'm wrong?

[tautech]

Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

The device has accepted the firmware. The device has been flashed. And after rebooting, there is nothing but a splash screen ... the probability of error is minimal, but the device turned into a brick. Or did I still upload the wrong firmware?

The file was named like this: SDS1000CML + _6.01.01.21R2.ADS

Now I don’t know what to do ... I really do not want to buy a new one. I believe that there is a way to restore it to work.

I checked the FW link and it points to the Siglent America site where I get the same file size from so it should be OK.

The normal method to get past a boot freeze is pressing Math, Math, Math at the instant of power ON and for many press times.
Try several times and fast button presses are required.

I can ask the factory for USB recovery files if they have them.
Please do not change any HW until I can get a reply from the factory.

Edit
Please confirm the label badge of this DSO as rebadged Siglents are supplied into Russia.
If it was being flashed with Siglent FW a .config file is also needed.

[tv84]

Wow! I think you got a problem in that .app file.

The MD5 of SDS1000_arm.app in SDS1000A_6.01.01.21R2.ADS is 8D9E216E6EDCA25E8C8B3BD25EE9A938.

The parsing of that .ADS is attached.

Edit: I include the file.

[tautech]

@Zhenja
I have SDS1kCML+ USB recovery files now that I can email. (the factory was very quick to reply and send them)
It is 12.5MB zip file so contact me via PM and I can get them to you when I have your email.

[Zhenja]

@tv84

Thanks so much for providing the SDS1000_arm.app application.
Running the application in USB flash drive did not bring success
The first launch was long and there was an error:

Code: [Select]

 I/O warning : failed to load external entity "/usr/bin/siglent/usr/log/111/config/NSP_config_upgrade_info.xml"
Here is the complete conclusion:

Code: [Select]

check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN = ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
is_fs_mounted 1 --- ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busy
mount_fs: mounted
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busy
mount_fs: mounted
--mount_check_copy_appdata: ending
Load Fpga Success!
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00010000...
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
I0101 00:01:18.966090   704 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:01:18.969528   704 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:01:19.170990   704 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

I/O warning : failed to load external entity "/usr/bin/siglent/usr/log/111/config/NSP_config_upgrade_info.xml"
vxi11_main = 79187
sh: portmap: Structure needs cleaning
insmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File exists
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!
insmod: cannot insert '/usr/bin/siglent/drivers/musb_hdrc.ko': File exists
insmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File exists

[1] + Done(1)                    ./SDS1000_arm.app
/usr/bin/siglent/usr/log/111 #
I copied the necessary files to the directory where the program is looking for them, but the application still does not start

What's interesting: the built-in application always produces the same error, and the application in USB flash drives is different each time. Here are a couple of conclusions:

Code: [Select]

/usr/bin/siglent/usr/log/111 # ./SDS1000_arm.app
killall: telnetd: no process killed
check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN = ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
is_fs_mounted 1 --- ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busy
mount_fs: mounted
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busy
mount_fs: mounted
--mount_check_copy_appdata: ending
Load Fpga Success!
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00010000...
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
I0101 00:01:33.245787   706 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:01:33.247694   706 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:01:33.257544   706 module.cpp:464] rm -f /usr/bin/siglent/usr/log/111/usr/log/Info_19700101-000133.706
I0101 00:01:35.282466   706 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 95290
sh: portmap: Structure needs cleaning
insmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File exists
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!
insmod: cannot insert '/usr/bin/siglent/drivers/musb_hdrc.ko': File exists
/usr/bin/siglent/usr/log/111 # insmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File exists

/usr/bin/siglent/usr/log/111 #
/usr/bin/siglent/usr/log/111 #
/usr/bin/siglent/usr/log/111 # ./SDS1000_arm.app
killall: telnetd: no process killed
check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN = ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
is_fs_mounted 1 --- ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busy
mount_fs: mounted
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busy
mount_fs: mounted
--mount_check_copy_appdata: ending
Load Fpga Success!
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00010000...
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
I0101 00:02:08.258028   752 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:02:08.259955   752 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:02:08.269704   752 module.cpp:464] rm -f /usr/bin/siglent/usr/log/111/usr/log/Info_19700101-000208.752
I0101 00:02:10.304207   752 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 130310
sh: portmap: Structure needs cleaning
insmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File exists
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!
insmod: cannot insert '/usr/bin/siglent/drivers/musb_hdrc.ko': File exists
insmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File exists


Code: [Select]

/usr/bin/siglent/usr/log/111 # ./SDS1000_arm.app
check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN = ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
is_fs_mounted 1 --- ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busy
mount_fs: mounted
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busy
mount_fs: mounted
--mount_check_copy_appdata: ending
Load Fpga Success!
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
I0101 00:00:55.197074   658 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:55.201481   658 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

I0101 00:00:55.213566   658 module.cpp:464] rm -f /usr/bin/siglent/usr/log/111/usr/log/Info_19700101-000055.658
I0101 00:00:56.347872   658 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------

vxi11_main = 56360
sh: portmap: Structure needs cleaning
insmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File exists
Cannot register service: RPC: Unable to receive; errno = Connection refused
unable to register (DEVICE_ASYNC, DEVICE_ASYNC_VERSION, udp).Clean Up Ready!
Clean Up Over!
/usr/bin/siglent/usr/log/111 # insmod: cannot insert '/usr/bin/siglent/drivers/musb_hdrc.ko': File exists
insmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File exists


It seems that the matter is not only in the application.
In general, I began to doubt that I really poured exactly SDS1000CML + _6.01.01.21R2.ADS into the device
Maybe I was mistaken and uploaded some other firmware and therefore the option with the correct application did not help.

Although the line confuses me:

Code: [Select]

Erasing 128 Kibyte @ 20000 -- 100 % complete
but this did not affect the original behavior of the device.

So far I have no idea what can be done. I will wait for the option that tautech offers.
If someone has ideas - write.

@tautech
I sent my contacts in a personal message.

[tv84]

tautech will solve the problem.

But you can do a CRC32 of your app and place it here so that I can search which version you flashed. Use the usual zip CRC32.

[Zhenja]

Let's try to find out what I really flooded. It became interesting to myself...

SDS1000_arm.app -> CRC32: 723008D8

Just in case, I attach the original application copied from my device.

[tautech]

@tautech
I sent my contacts in a personal message.

Replied with the conditions of use.

Let's try to find out what I really flooded. It became interesting to myself...

Understood, just let me know when/if you still want the recovery package.

[Zhenja]

@tautech

I gave you a complete answer in the mail.

[tautech]

@tautech

I gave you a complete answer in the mail.

Files sent. 

[Zhenja]

Hello. I apologize for the long reply. I was on a business trip.

I tried the recovery disk. It seems to be all according to the instructions, but the download process does not change in any way. As a result, nothing happens.

@tautech
Wrote a more detailed letter. Maybe I'm doing something wrong.

The problem is not solved. Who else has any thoughts?

[tv84]

The .app file that you have in the scope is bad.

As you can see in the attached files, I made and ELF parsing to analyse possible errors.

My parser can't even parse your app file because it has errors inside.

00000000                 Magic: 7F454C46    ELF File OK
00000004                Format: 32-bits
00000005                  Data: Little endian
00000006               Version: 1
00000007                OS/ABI: System V (often set to this)
00000008           ABI Version: 0
00000010           Object Type: Executable
00000012       Instruction Set: ARM
00000014               Version: 1
00000018           Entry Point: 0000D260
0000001C  Program Header Table: 00000034
00000020  Section Header Table: 0081466C  <- for example, this is totally wrong as the file is less than 0x00420000 in size!
00000024                 Flags: 05000002
00000028           Header Size: 00000034
0000002A  Program Headers Size: 00000020
0000002C     # Program Headers: 8
0000002E  Section Headers Size: 00000028
00000030     # Section Headers: 42
00000032 SH String Table Index: 39

I think the file is wrongly loaded into memory because of the errors.

Since tautech's recovery was worthless, according to you, my suspicion is that you have a bad NAND.

[tautech]

@tv84
We are both working on this ATM and I have a unit unpacked trying a few things.
The recovery files from Siglent only work with V 19 or 20 FW according to them.   
I will talk to them more in the next few days.


And BTW I'm looking at those CML+ key press sequences you posted a week or two back......no success with them yet. 
Others I know about  work OK so I'm not sure if I'm in the right mode to get yours to work. 

[Zhenja]

Due to the rush and my carelessness, I “erased” the bootloader. The device no longer turns on at all.
There are 3 ways left:
1) Soldering iron and programmer - filling in the dump (here I just do not have it)
2) find a way to flash a nand flash without a soldering iron (but there is no dump)
3) buy a new device and NEVER UPDATE IT MORE.

[tautech]

Due to the rush and my carelessness, I “erased” the bootloader. The device no longer turns on at all.
There are 3 ways left:
1) Soldering iron and programmer - filling in the dump (here I just do not have it)
2) find a way to flash a nand flash without a soldering iron (but there is no dump)
3) buy a new device and NEVER UPDATE IT MORE.

Please leave the HW until we get a fix from Siglent, see my findings below.....

Update:
See post:
https://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/msg2779266/#msg2779266

Oh FFS Siglent ! 
Version 6.01.01.21R2 will NOT load over V20 
Further, warnings that FW update is progressing so do not cut power NEVER finish, even after 10 minutes !
AND from the update instructions:
10. A window will open showing the system updating and progress bar . When it finished, The SPO will restart itself.
RUBBISH ! 

Stern mail will be found in their inbox tomorrow, this is simply not good enough !

If these failings are the cause of Zhenja's problems then his unit should be fixed at zero cost !

[tv84]

Version 6.01.01.21R2 will NOT load over V20 

 

Explain me this as if I were 4 years old.

[tautech]

Version 6.01.01.21R2 will NOT load over V20 

 

Yes,   

Explain me this as if I were 4 years old.

The message to NOT cut power NEVER finishes !
The FW is NOT installed ....NO progress bar and the unit does NOT auto reboot as indicated in the update instructions.

3 different USB sticks tested ! Factory Default tried .......FW's broken JIM !

[StillTrying]

Oh FFS Siglent ! 
Version 6.01.01.21R2 will NOT load over V20 
Further, warnings that FW update is progressing so do not cut power NEVER finish, even after 10 minutes !
AND from the update instructions:

I found .18 -> .19 impossible until I renamed the .19 filename to the .18 filename with just the final P18 bit changed to P19.
Which was quite different to the instruction to rename it to 8 chrs or less, I'd already tried 'FW19.ADS'.

https://www.eevblog.com/forum/testgear/siglent-cml-firmware/msg1197684/#msg1197684

[tv84]

As a filename, just use simply SIGLENT.ADS.

[tautech]

As a filename, just use simply SIGLENT.ADS.

Yep, solved but the instructions are abysmal to insist this be done and I've pleaded with Siglent to update their CML+ firmware install guides to ensure no one misses this required important filename edit.......I did ! 

[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!

[huxfluxdeluxe]

Hello everyone! I have Siglent SDS 1102CML+ at work that doesn't start. It wasn't due to update, somebody had just turned it off and all we got the next day was a logo screen. Not a single click from the relays!  I've tried the solution proposed by ratmole, but nothing happened.

Here's the log:

Code: [Select]

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
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

/ #
I've tried to mount the USB drive and got a respond:

Code: [Select]

mount /dev/sda1 /mnt
mount: mounting /dev/sda1 on /mnt failed: No such file or directory
/ #
Okay, I've tried the df command just like ucognitive said (to see all the drives attached):

Code: [Select]

df
Filesystem           1K-blocks      Used Available Use% Mounted on
ubi0:rootfs              36696     12744     23952  35% /
mdev                     62884         0     62884   0% /dev
/ #
Looks like I don't have /dev/sda1 device. Moreover, there was no power on the USB interface. We have another SDS 1102CML+ that is OK, so I've figured out that USB power turns on long after the startup, after the third relay click. Looks like I'm unable to use USB to recover my scope.

Is there another way to bring it back to life? I've noticed microSD slot next to UART interface, what's it for?

P. S. Pic attached: UART interface. White = TX, Green = RX, Purple = GND. Don't forget to cross RX and TX lines on your adapter. I've used cheap CH340 and it worked well!

[tautech]

Hello everyone! I have Siglent SDS 1102CML+ at work that doesn't start.

Is there another way to bring it back to life? I've noticed microSD slot next to UART interface, what's it for?

Contact me by PM with your email.
I have some tools that will help...........

[ratmole]

Okay, I've tried the df command just like ucognitive said (to see all the drives attached):

Code: [Select]

df
Filesystem           1K-blocks      Used Available Use% Mounted on
ubi0:rootfs              36696     12744     23952  35% /
mdev                     62884         0     62884   0% /dev
/ #

df will list only the mounted drives.
type

Code: [Select]

dmesg after you plug the usb and see witch device/partition will be listed as usb

and then try to mount the usb device again.

[huxfluxdeluxe]

Thank you ratmole! We're working on a problem with tautech now. I've found that there's no power on the USB port - I believe it becomes active after the HW check, but my scope can't get there. I've checked USB power on a good 1102CML+ and it really appears simultaneously with the main user interface. So my flash drive's LED isn't lit when plugged into the scope. I think it won't be listed in a device list too, since there's no power.

We're relying on microSD card recovery now, but I've got some troubles formatting it. Gotta look for old low capacity cards at home. Anyway, thank you for priceless information and for your readiness to help a complete stranger!

[huxfluxdeluxe]

And the biggest THANKS goes to tautech as he helped me to resurrect the oscilloscope! Moreover, it became 1152CML+, which is a nice bonus!

Everybody struggling with Siglents stuck on a startup screen - don't hesitate and contact tautech by persanal messages. It's truly a miracle that we couldn't find help from local equipment reseller but found it in New Zealand!

Also thank you ratmole for explaining how to use UART. It helped me a lot while finding the root of evil.

[tautech]

 
You did all the work....I only supplied the recovery tools from Siglent.

To all out there: keep your firmware updated !
https://int.siglent.com/download/firmwares/

[AlexZ]

Hello everybody! There is an oscilloscope SIGLENT SDS1152CML When turned on, it hangs on the LOGO, connected the J11 connector , in the terminal it gives everything exactly the same as huxfluxdeluxe can not mount a USB flash drive. When loading the device, the USB flash drive is read, but then I can't find it when the KERNEL is loaded   . I reread the posts of tautech, ratmole and others - you are competent guys and I ask for your help.

[tautech]

Hello everybody! There is an AKIP 4115/5A oscilloscope (SIGLENT SDS1152CML) When turned on, it hangs on the LOGO, connected the J11 connector , in the terminal it gives everything exactly the same as huxfluxdeluxe can not mount a USB flash drive. When loading the device, the USB flash drive is read, but then I can't find it when the KERNEL is loaded   . I reread the posts of tautech, ratmole and others - you are competent guys and I ask for your help.

Welcome to the forum.

Hopefully without a SD card holder we can recover this with USB tools.
PM sent.

[tv84]

Hello everybody! There is an oscilloscope SIGLENT SDS1152CML

Pay attention. Your is a SIGLENT SDS1152CML+ ! Don't confuse it with non + versions.

[AlexZ]

Today I soldered the SD card holder, microSD is read by the mmc part command in uboot.

[tautech]

Hello everybody! There is an oscilloscope SIGLENT SDS1152CML

Pay attention. Your is a SIGLENT SDS1152CML+ ! Don't confuse it with non + versions.

I suspect it is however how did you spot this ? LAN = + model.
Some CML+ do have a SD card holder. 

[tautech]

I soldered the microsd card holder today, I thought that I could see it through it did not work. AKIP 4115/5A the same SIGLENT SDS1152CML+

Check your messages.

[AlexZ]

I suspect it is however how did you spot this ?
Some CML+ do have a SD card holder. 

microSD was able to check with the mmc part command in U-BOOT, an answer was received about the number of blocks on the microSD, i.e. the port itself and the katra working is obtained now. only I can't see it outside of U-BOOT

[tv84]

I suspect it is however how did you spot this ?
Some CML+ do have a SD card holder. 

  You're the expert in these recoveries.

The CML+ is an ARM machine as his logs shows. The CML would be a BF with no uboot...

I was just warning so that, in despair, he wouldn't try to flash a CML FW.

[AlexZ]

The CML+ is an ARM machine as his logs shows.

Can the SIGLENT SDY8.007.107E CML_1700 motherboard number match SDS1152CML+ ?

[tautech]

I suspect it is however how did you spot this ?
Some CML+ do have a SD card holder. 

  You're the expert in these recoveries.

The CML+ is an ARM machine as his logs shows. The CML would be a BF with no uboot...

I was just warning so that, in despair, he wouldn't try to flash a CML FW.

Yes of course and because it has a LAN socket it must be a + model.

Anyways work to do getting Alex fixed up.

[AlexZ]

Hey! Thanks for the help, everything worked, special thanks to tautech, and tv84 for responding to my problem, tautech helped with tools.

[StillTrying]

I would have expected all CML+ version screens to look nearly identical, my CML+ looks quite a bit different from AlexZ. There's not much choice in what comes up for the on graticule auto measurements, just voltage, time, or both, which covers more than half area of the screen.

[Cicciousb]

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

hi to all, i have try it but not detected, i dont see any log and siglent stuck on logo. any solution?

[tautech]

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

hi to all, i have try it but not detected, i dont see any log and siglent stuck on logo. any solution?

Welcome to the forum.

PM sent.

[Cicciousb]

Thanks, is a pleasure

[godfather]

@tautech
 Hello , I hope everyone is doing great.
I am having problems with my SDS1102CML+ DSO, Its Stuck at BOOT logo, I tried doing factory recovey but it isnt working, Below is my Serial Log. I request @tautech and other to provide the solution for the same.

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:   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
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/ # ./SDS1000_arm.app: relocation error: /usr/lib/libglog.so.0: symbol _ZNSt15basic_streambufIcSt11char_traitsIcEE6setbufEPci, version GLIBCXX_3.4 not defined in file libstdc++.so.6 with link time reference


With Pendrive 4GB

Code: [Select]

U-Boot SPL 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)
config ddr_pll_config()++
config ddr_pll_config()--
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-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... 0 Storage Device(s) found
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
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/ # ./SDS1000_arm.app: relocation error: /usr/lib/libglog.so.0: symbol _ZNSt15basic_streambufIcSt11char_traitsIcEE6setbufEPci, version GLIBCXX_3.4 not defined in file libstdc++.so.6 with link time reference



[tautech]

@tautech
 Hello , I hope everyone is doing great.
I am having problems with my SDS1102CML+ DSO, Its Stuck at BOOT logo, I tried doing factory recovey but it isnt working, Below is my Serial Log.

Don't need logs.
Send me PM.

[Roman555]

@tautech ,
do you still help owners of digital oscilloscopes Siglent ? Please, help me too.
I also have Siglent SDS1102cml+ (for my hobby) and it doesn't boot anymore.
The story is similar : it was turned off the day before and it didn't boot the next day.
It just stuck on boot logo. I tried to press MATH rapidly and although the device did reset but there were no changes.
Is there a way to restore my digital oscilloscope not opening the case?
Though the warranty is off a long ago...
Thanks!

Upd.
tautech is helping me. Many thanks him.
The oscilloscope appears to be picky about a recovery method (the USB recovery doesn't work because of too old firmware).

Upd2.
My oscilloscope is recovered successfully. Now it also has a fresh firmware 
I thank tautech for his help and resources, and also this forum that connects people living all over the world.

[tautech]

@tautech ,
do you still help owners of digital oscilloscopes Siglent ? Please, help me too.
I also have Siglent SDS1102cml+ (for my hobby) and it doesn't boot anymore.
The story is similar : it was turned off the day before and it didn't boot the next day.
It just stuck on boot logo. I tried to press MATH rapidly and although the device did reset but there were no changes.
Is there a way to restore my digital oscilloscope not opening the case?
Though the warranty is off a long ago...
Thanks!

Welcome to the forum.

PM returned.

[Rybak27]

Hello!
I have an oscilloscope:

Yesterday it stopped working.  This always displays the boot logo.  I tried resetting with the Math button, but that didn't help.  I want to try flashing it.  Help identify the original model.  I know for sure that this is a plus model, it has an ethernet port.
Sorry for my English

[OMAR EDEL]

Hello good night. I have a problem with an oscilloscope siglent SDS 1052DL+. This is in logo stuck, it can start.
Thank you for your help. Best Regards.

U-Boot SPL 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34) config ddr_pll_config()++ config ddr_pll_config()-- 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-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:   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 /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 Failed! ECC failed: 0 ECC corrected: 0 Number of bad blocks: 0 Number of bbt blocks: 0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00010000...

[tautech]

Hello good night. I have a problem with an oscilloscope siglent SDS 1052DL+. This is in logo stuck, ........

Welcome to the forum.

Close it up and we don't need a dump to fix it.
Send your email address by PM and we will work with you to recover it with our USB tools from Siglent.

[Cyrus755]

Hi everybody. My SDS1102CML+ turned into a brick after trying to update the firmware "SDS1000CML+ Firmware_V6.01.01.22 (Release Date 08.06.21)". At the moment, after switching on, only the Siglent logo is displayed on the screen. The oscilloscope startup stops at the Linux kernel starting stage. @tautech can you help resurrect my oscilloscope?

Startup console log

Code: [Select]

U-Boot SPL 2013.01.01-svn119138 (Jul 22 2021 - 10:57:19)
config ddr_pll_config()++
config ddr_pll_config()--
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-svn119138 (Jul 22 2021 - 10:57:19)
 
I2C:   ready
DRAM:  128 MiB
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
 
set_default_env::7922
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.

[tautech]

Hi everybody. My SDS1102CML+ turned into a brick after trying to update the firmware "SDS1000CML+ Firmware_V6.01.01.22 (Release Date 08.06.21)". At the moment, after switching on, only the Siglent logo is displayed on the screen. The oscilloscope startup stops at the Linux kernel starting stage. @tautech can you help resurrect my oscilloscope?

Startup console log..............

Welcome to the forum.

Button it up, we don't need logs.
Contact me via PM with your email address.

[vagalum147]

Hi,

I have the same problem.  The SDS1102CML+, it has the initial screen stuck. I bought it a few months ago to do my hobbies but now I turn it on and it gets stuck on the home screen. Need help and tools like you said. Thank you

UPDATE: All is ok now! Thank you so much, tautech.

[ocb2b]

Hello,
I use this post to ask for help, I have exact same problem with my SDS1102CML+. It is stucked on the "Uncompressing Linux... done, booting the kernel." message.
Can I ask you for help in private messages too tautech ?

[tautech]

Hello,
I use this post to ask for help, I have exact same problem with my SDS1102CML+. It is stucked on the "Uncompressing Linux... done, booting the kernel." message.
Can I ask you for help in private messages too tautech ?

Sure.
Send me a personal message with your email address.

[ocb2b]

Massive thank you for your help. 

[tautech]

Massive thank you for your help. 

No worries, you did all the work. 

Stick around and enjoy the forum.

[jhnlmn]

Hi,
My SDS1102CML+ prints "Uncompressing Linux... done, booting the kernel." and nothing more.
I tried to flash files from P21R2.zip, which was posted in https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg3280472/#msg3280472 but that made no difference.
I noticed that files P21R2.zip are from 2015/2016 but my SDS1102CML+ is new.
I wonder whether I can download some other, may be newer files from somewhere?
Thank you

[tautech]

Hi,
My SDS1102CML+ prints "Uncompressing Linux... done, booting the kernel." and nothing more.
I tried to flash files from P21R2.zip, which was posted in https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg3280472/#msg3280472 but that made no difference.
I noticed that files P21R2.zip are from 2015/2016 but my SDS1102CML+ is new.
I wonder whether I can download some other, may be newer files from somewhere?
Thank you

Welcome to the forum.

All recent firmware files are here at the US Siglent website:
https://siglentna.com/service-and-support/firmware-software/digital-oscilloscopes/#sds1000cml-series

[jhnlmn]

But official firmware from Siglent only contains P21R2.ADS, which cannot be installed if Linux does not start. Can it?
I tried placing P21R2.ADS to USB stick and rebooting, but nothing happens.
I see that it is trying to read ro_uImage, rootfs.img, datafs.img and logo.bmp, but not P21R2.ADS.

[tautech]

But official firmware from Siglent only contains P21R2.ADS, which cannot be installed if Linux does not start. Can it?
I tried placing P21R2.ADS to USB stick and rebooting, but nothing happens.
I see that it is trying to read ro_uImage, rootfs.img, datafs.img and logo.bmp, but not P21R2.ADS.

Oh a boot freeze, that is different !

Send a PM with your contact email and we'll have you fixed up in no time.

[rdekens@internode.on.net]

Greetings - have a SDS 1104x-E that has decided to suddenly become a teapot -

Siglent inital splash screen comes up -  - all the lights ( and I mean all buttons) stay lit - you can see it try to reset ? buttons dim for a sec but nothing further

have tryed with the USB - nothing -
have connected on j11 and get a poor serial trace - couple of random strings and then just a never ending character stream
as below

so i need some help !

ñññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññññ
VQÚ¿%5#¿7%=¿£££åë ^H¤¦)úë=µýSwe}£££¿åëY=¿%5#¿7%=¿7!#5£¿åë y½Þ¯UÛ…!¿›Ÿ—£Ÿ‘¥#™›‘“Ÿ¿¯e=¿›™¿›Ÿ¿¥¿Ÿ‹™•‹›­åëåë{!=7‹íO-'-#¿K
#åëm›y‹¿¿¿5=7
åëw[}e‹¿¿uyy¿7-=;'57¿›—™¿e-{åë ¬Ý-¿¿›•“¿e-{åëeey‹¿¿¿
#A7/9-‹¿Ÿåë µµµ‹õ#-#1¿¥¿;=7¿y[y§¿-#1¿753='¿5#-!#%5#åëåëm#‹¿¿¿¿5-='åëa‹¿¿¿5-='åëu‹¿¿¿5-='åë-#¿;!=7A'=5A-#-¯!-7­©©©©©åëImcsaE-#¿3;A7-'=
A'!1!¯!-7­©©©©©©©©©©©©åë R[¬®}Y!=15e5%…Ÿ3=ŸŸŸŸŸ§¿'!1!A7==…Ÿ›ŸŸŸ™“§¿-7/…ŸŸ§¿/5-1/…—Ÿåë¿ R[¬®µ#¿3;A7-'=
A'!1!¯!-7­¥¥¥¥¥¥¥¥¥¥åë-#¿;!=7A'=5A-#-¯!-7­¥¥¥¥¥åëc5‹¿¿¿q5%£5ŸŸŸ;ŸŸŸåëo-¿=#
¿)5
¿!¿!¿=!;!!‹¿¿¿ïïï¿Ÿ¿åë
#¥;!!ƒ¿ ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

...

Regards
Rayman

[Francesco]

Hello everyone! I have Siglent SDS 1102CML+ at work that doesn't start.

Is there another way to bring it back to life? I've noticed microSD slot next to UART interface, what's it for?

Contact me by PM with your email.
I have some tools that will help...........

Googmorning tautech,
my name is Francesco and i m a newbie. Last week my friend gifted to me a sds 1102cml+ with a lock logo screen ...and ..if possible, i would fix it.
I have many problems....because my english is so bad and my skill in this topic are too low for understand all...but i know somthing welding  electronics boards
So...I soldering wire and connect to rs232 usb adpator. I download from siglent Easy scopex and i conneced to him with rs232 ( same photo on link  [url]https://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/25/]https://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/25/).
Now i don't say how walkaway....
Thank a lot
Francesco

[smittyinthesky]

I would like to add a "me too" posting in this thread. I think I have a similar but different issue?

I recall I attempted to flash the firmware on my SDS1102CML+ and it never came back up.

Here is my serial out put.

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:   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
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 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
/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

I've done the USB recovery with P21R2.7z but I still get an error about /dev/ttyO0 not being found.

Does this look like a bad board or a bad kernel/firmware?

Thanks.

[tv84]

Is the scope working or not?

[smittyinthesky]

tautech got me up and running with proper recovery files. just working out the last few items, but it's back up and running.

[tautech]

tautech got me up and running with proper recovery files. just working out the last few items, but it's back up and running.

Yup.

Note to all, please don't go opening your scopes to sniff any data bus .....it's just not required !

[dwhp]

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

[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!