Help restore SDS1102CML+ after unsuccessful flashing - Page 1
Forum section: electronics / testgear

author: Zhenja
author_rank: Contributor
timestamp: November 03, 2019, 01:40:04 pm
content: 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:/ # check_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Success!The Help file load OK!!Could not create log file: File existsCOULD 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 = 5583sh: portmap: Structure needs cleaningCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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 firmwarePlease help to resurrect the device.Update 05.03.2020I 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.

author: tv84
author_rank: Super Contributor
timestamp: November 04, 2019, 12:31:37 am
content: What .ADS did you flash?

author: Zhenja
author_rank: Contributor
timestamp: November 04, 2019, 09:15:56 am
content: Downloaded from here:https://www.siglent.eu/DownloadsSection: SDS1000CML + Series Digital Storage OscilloscopesThe latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) DownloadThe 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.ADSNow 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 ...PSIs 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.

author: Zhenja
author_rank: Contributor
timestamp: November 04, 2019, 09:35:16 am
content: This is how the full load of the device from the moment of power supply looks:Code: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7090Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autobootBooting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/etc/init.d/rcS: line 24: portmap: Structure needs cleaning/ # check_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Success!The Help file load OK!!Could not create log file: File existsCOULD 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 = 5542sh: portmap: Structure needs cleaningCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7090Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autobootU-Boot# printenva=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 darch=armb=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 0x300000baudrate=115200board=sds1000aboard_name=A335X_SKboard_rev=1.0Abootargs_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=1bootenv=uEnv.txtbootfile=uImageconsole=ttyO0,115200n8cpu=armv7d=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; fidfu_alt_info_emmc=rawemmc mmc 0 3751936dfu_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 1dfu_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 9ethact=cpswethaddr=60:64:05:37:5a:0cf=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; fifdt_high=0xfffffffffdtaddr=0x80F80000findfdt=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; figatewayip=10.11.13.1i=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; fiimportbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesizeip_method=noneipaddr=10.11.13.250k=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; fikloadaddr=0x80007fc0loadaddr=0x80200000loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gzloaduimage=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; fimmc-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=0mmcroot=/dev/mmcblk0p2 rommcrootfstype=ext3 rootwaitmtdids=nand0=omap2-nand.0mtdparts=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=0x300000nandroot=ubi0:rootfs rw ubi.mtd=7,2048nandrootfstype=ubifs rootwait=1nandsrcaddr=0x3080000netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcpnetboot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}netmask=255.255.255.0nfsopts=nolockr=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; firamargs=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},64Mramrootfstype=ext2rdaddr=0x81000000rootpath=/export/rootfsserverip=10.11.13.19soc=am33xxspiargs=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=0spiimgsize=0x362000spiroot=/dev/mtdblock4 rwspirootfstype=jffs2spisrcaddr=0xe0000static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::offstderr=serialstdin=serialstdout=serialu=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; fivendor=tiver=U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)Environment size: 7391/131068 bytesIt describes different download options from different sources ...Perhaps this information will be useful.Any ideas what can be done?

author: StillTrying
author_rank: Super Contributor
timestamp: November 04, 2019, 12:05:54 pm
content: Quote from: Zhenja on November 04, 2019, 09:15:56 amI'm glad I haven't tried .21R2 yet.QuoteThere'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.

author: Zhenja
author_rank: Contributor
timestamp: November 04, 2019, 12:16:34 pm
content: Here's what happens after you press MATH:Code: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7090Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autobootBooting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/etc/init.d/rcS: line 24: portmap: Structure needs cleaning/ # check_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Success!format_fs++Erasing 128 Kibyte @ 6560000 -- 100 % completeWriting data to block 0 at offset 0x0Writing data to block 1 at offset 0x20000Writing data to block 2 at offset 0x40000Writing data to block 3 at offset 0x60000Writing data to block 4 at offset 0x80000Writing data to block 5 at offset 0xa0000Writing data to block 6 at offset 0xc0000Writing data to block 7 at offset 0xe0000Writing data to block 8 at offset 0x100000Writing data to block 9 at offset 0x120000Writing data to block 10 at offset 0x140000Writing data to block 11 at offset 0x160000Writing data to block 12 at offset 0x180000Writing data to block 13 at offset 0x1a0000Writing data to block 14 at offset 0x1c0000Writing data to block 15 at offset 0x1e0000format_fs--The system is going down NOW!Sending SIGTERM to all processesRequesting system rebootU-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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7090Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autobootBooting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/etc/init.d/rcS: line 24: portmap: Structure needs cleaning/ # check_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Success!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 = 6188sh: portmap: Structure needs cleaningCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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.

author: tv84
author_rank: Super Contributor
timestamp: November 04, 2019, 12:29:43 pm
content: 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.)

author: Zhenja
author_rank: Contributor
timestamp: November 04, 2019, 01:50:43 pm
content: 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?PSI copied SDS1000_arm.app from the device to a USB flash. Counted md 5: 143d81349e8abf7ea799c92f09bfeadeCan 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.

author: Zhenja
author_rank: Contributor
timestamp: November 04, 2019, 01:58:26 pm
content: Tell me, do I think that NAND is precisely this chip on the board?Or I'm wrong?

author: tautech
author_rank: Super Contributor
timestamp: November 04, 2019, 07:48:14 pm
content: Quote from: Zhenja on November 04, 2019, 09:15:56 amI 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.EditPlease 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.

author: tv84
author_rank: Super Contributor
timestamp: November 04, 2019, 07:52:27 pm
content: Wow! I think you got a problem in that .app file.TheMD5of SDS1000_arm.app in SDS1000A_6.01.01.21R2.ADS is8D9E216E6EDCA25E8C8B3BD25EE9A938.The parsing of that .ADS is attached.Edit: I include the file.

author: tautech
author_rank: Super Contributor
timestamp: November 05, 2019, 04:50:16 am
content: @ZhenjaI 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.

author: Zhenja
author_rank: Contributor
timestamp: November 05, 2019, 04:51:47 pm
content: @tv84Thanks so much for providing the SDS1000_arm.app application.Running the application in USB flash drive did not bring successThe first launch was long and there was an error:Code: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:check_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_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 0is_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 0mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busymount_fs: mountedis_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busymount_fs: mounted--mount_check_copy_appdata: endingLoad Fpga Success!ECC failed: 0ECC corrected: 0Number of bad blocks: 0Number of bbt blocks: 0Block size 131072, page size 2048, OOB size 64Dumping data starting at 0x00000000 and ending at 0x00010000...Erasing 128 Kibyte @ 20000 -- 100 % completeThe 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 = 79187sh: portmap: Structure needs cleaninginsmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File existsCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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 existsinsmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File exists + 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 startWhat'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:/usr/bin/siglent/usr/log/111 # ./SDS1000_arm.appkillall: telnetd: no process killedcheck_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_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 0is_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 0mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busymount_fs: mountedis_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busymount_fs: mounted--mount_check_copy_appdata: endingLoad Fpga Success!ECC failed: 0ECC corrected: 0Number of bad blocks: 0Number of bbt blocks: 0Block size 131072, page size 2048, OOB size 64Dumping data starting at 0x00000000 and ending at 0x00010000...Erasing 128 Kibyte @ 20000 -- 100 % completeThe 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.706I0101 00:01:35.282466 706 module.cpp:489]-----------------------------------------------------------------------------------------------------------------------------------vxi11_main = 95290sh: portmap: Structure needs cleaninginsmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File existsCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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.appkillall: telnetd: no process killedcheck_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_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 0is_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 0mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busymount_fs: mountedis_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busymount_fs: mounted--mount_check_copy_appdata: endingLoad Fpga Success!ECC failed: 0ECC corrected: 0Number of bad blocks: 0Number of bbt blocks: 0Block size 131072, page size 2048, OOB size 64Dumping data starting at 0x00000000 and ending at 0x00010000...Erasing 128 Kibyte @ 20000 -- 100 % completeThe 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.752I0101 00:02:10.304207 752 module.cpp:489]-----------------------------------------------------------------------------------------------------------------------------------vxi11_main = 130310sh: portmap: Structure needs cleaninginsmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File existsCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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 existsinsmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File existsCode:/usr/bin/siglent/usr/log/111 # ./SDS1000_arm.appcheck_and_upgrade:starting...mount_fs: rw,ubi1_0,/usr/bin/siglent/usrubi1_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_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 0is_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 0mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busymount_fs: mountedis_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0attachedMOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busymount_fs: mounted--mount_check_copy_appdata: endingLoad Fpga Success!Erasing 128 Kibyte @ 20000 -- 100 % completeThe 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.658I0101 00:00:56.347872 658 module.cpp:489]-----------------------------------------------------------------------------------------------------------------------------------vxi11_main = 56360sh: portmap: Structure needs cleaninginsmod: cannot insert '/usr/bin/siglent/drivers/udc-core.ko': File existsCannot register service: RPC: Unable to receive; errno = Connection refusedunable 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 existsinsmod: cannot insert '/usr/bin/siglent/drivers/ti81xx.ko': File existsIt 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 deviceMaybe 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:Erasing 128 Kibyte @ 20000 -- 100 % completebut 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.@tautechI sent my contacts in a personal message.

author: tv84
author_rank: Super Contributor
timestamp: November 05, 2019, 05:05:06 pm
content: 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.

author: Zhenja
author_rank: Contributor
timestamp: November 05, 2019, 06:17:21 pm
content: Let's try to find out what I really flooded. It became interesting to myself...SDS1000_arm.app -> CRC32: 723008D8Just in case, I attach the original application copied from my device.

author: tautech
author_rank: Super Contributor
timestamp: November 05, 2019, 07:13:09 pm
content: Quote from: Zhenja on November 05, 2019, 04:51:47 pmReplied with the conditions of use.Quote from: Zhenja on November 05, 2019, 06:17:21 pmUnderstood, just let me know when/if you still want the recovery package.

author: Zhenja
author_rank: Contributor
timestamp: November 06, 2019, 08:58:40 am
content: @tautechI gave you a complete answer in the mail.

author: tautech
author_rank: Super Contributor
timestamp: November 06, 2019, 09:03:46 am
content: Quote from: Zhenja on November 06, 2019, 08:58:40 amFiles sent.

author: Zhenja
author_rank: Contributor
timestamp: November 09, 2019, 01:24:18 pm
content: 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.@tautechWrote a more detailed letter. Maybe I'm doing something wrong.The problem is not solved. Who else has any thoughts?

author: tv84
author_rank: Super Contributor
timestamp: November 09, 2019, 08:22:11 pm
content: 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 OK00000004 Format: 32-bits00000005 Data: Little endian00000006 Version: 100000007 OS/ABI: System V (often set to this)00000008 ABI Version: 000000010 Object Type: Executable00000012 Instruction Set: ARM00000014 Version: 100000018 Entry Point: 0000D2600000001C Program Header Table: 0000003400000020 Section Header Table:0081466C<- for example, this is totally wrong as the file is less than 0x00420000 in size!00000024 Flags: 0500000200000028 Header Size: 000000340000002A Program Headers Size: 000000200000002C # Program Headers: 80000002E Section Headers Size: 0000002800000030 # Section Headers: 4200000032 SH String Table Index: 39I 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.

author: tautech
author_rank: Super Contributor
timestamp: November 09, 2019, 08:39:17 pm
content: @tv84We 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 aboutwork OK so I'm not sure if I'm in the right mode to get yours to work.

author: Zhenja
author_rank: Contributor
timestamp: November 09, 2019, 09:30:58 pm
content: 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.

author: tautech
author_rank: Super Contributor
timestamp: November 09, 2019, 09:44:11 pm
content: Quote from: Zhenja on November 09, 2019, 09:30:58 pmPlease 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/#msg2779266Oh FFS Siglent !Version 6.01.01.21R2 will NOT load over V20Further, 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 !

author: tv84
author_rank: Super Contributor
timestamp: November 09, 2019, 10:40:09 pm
content: Quote from: tautech on November 09, 2019, 09:44:11 pmExplain me this as if I were 4 years old.

author: tautech
author_rank: Super Contributor
timestamp: November 09, 2019, 10:49:45 pm
content: Quote from: tv84 on November 09, 2019, 10:40:09 pmYes,QuoteThe 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 !

author: StillTrying
author_rank: Super Contributor
timestamp: November 10, 2019, 10:47:59 am
content: Quote from: tautech on November 09, 2019, 09:44:11 pmI 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

author: tv84
author_rank: Super Contributor
timestamp: November 10, 2019, 01:13:44 pm
content: As a filename, just use simplySIGLENT.ADS.

author: tautech
author_rank: Super Contributor
timestamp: November 11, 2019, 02:16:53 am
content: Quote from: tv84 on November 10, 2019, 01:13:44 pmYep, 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 !

author: ratmole
author_rank: Contributor
timestamp: February 10, 2021, 07:14:42 pm
content: If anyone has problems with stuck logo on boot, try this:1. Remove the back cover of the SDS1102CML+ oscilloscope,2, Remove the metal back of the cage3. Connect RX,TX serial cables on the unpopulated J11 connector. Solder TX to the second pad and RX to the third pad.4. Connect to serial: Baudrate 1152005. Boot the oscilloscope, now you will see the boot log. If not, swap the RX,TX cables to your serial adaptor.6. Unzip the contents of the P21R2.zip in a fat32 formated usb stick. Also unzip the SDS1000_arm.zip and copy the SDS1000_arm.app to the root of the usb flash drive.7. Connect the usb flash drive to the oscilloscope and power off and the on the oscilloscope.8. Let the oscilloscope to perform the FW Recovery.9. Remove the usb flash drive and Reboot10. done!If the oscilloscope still hangs on the boot logoStart the oscilloscopewithout the usb flash drive.When the boot is complete, but still on logoInsert the usb flash drive and type in the serial console:Code:mount /dev/sda1 /mntmount / -o remount,rwcp /mnt/SDS1000_arm.app /usr/bin/siglent/SDS1000_arm.appchmod +x /usr/bin/siglent/SDS1000_arm.appmkdir -p /usr/bin/siglent/firmdata0/usr/logcd /usr/bin/siglent/./SDS1000_arm.appNow the oscilloscope is back to life!Please perform a hardware reset using the Math button method and you are good as new.a big thanks to tv84 and tautech for their help!

author: huxfluxdeluxe
author_rank: Newbie
timestamp: March 16, 2021, 04:26:53 pm
content: 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 byratmole, but nothing happened.Here's the log:Code: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7090Net: <ethaddr> not set. Validating first E-fuse MACcpswHit any key to stop autobootBooting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ #I've tried to mount the USB drive and got a respond:Code:mount /dev/sda1 /mntmount: mounting /dev/sda1 on /mnt failed: No such file or directory/ #Okay, I've tried thedfcommand just likeucognitivesaid (to see all the drives attached):Code:dfFilesystem 1K-blocks Used Available Use% Mounted onubi0:rootfs 36696 12744 23952 35% /mdev 62884 0 62884 0% /dev/ #Looks like I don't have/dev/sda1device. 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!

author: tautech
author_rank: Super Contributor
timestamp: March 16, 2021, 07:23:15 pm
content: Quote from: huxfluxdeluxe on March 16, 2021, 04:26:53 pmContact me by PM with your email.I have some tools that will help...........

author: ratmole
author_rank: Contributor
timestamp: March 17, 2021, 01:04:31 pm
content: Quote from: huxfluxdeluxe on March 16, 2021, 04:26:53 pmdf will list only the mounted drives.typeCode:dmesgafter you plug the usb and see witch device/partition will be listed as usband then try to mount the usb device again.

author: huxfluxdeluxe
author_rank: Newbie
timestamp: March 17, 2021, 05:18:43 pm
content: Thank youratmole! We're working on a problem withtautechnow. 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!

author: huxfluxdeluxe
author_rank: Newbie
timestamp: March 18, 2021, 06:28:22 pm
content: And the biggest THANKS goes totautechas 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 contacttautechby 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 youratmolefor explaining how to use UART. It helped me a lot while finding the root of evil.

author: tautech
author_rank: Super Contributor
timestamp: March 18, 2021, 06:34:42 pm
content: 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/

author: AlexZ
author_rank: Newbie
timestamp: March 30, 2021, 02:48:51 pm
content: Hello everybody! There is an oscilloscopeSIGLENT SDS1152CMLWhen turned on, it hangs on the LOGO, connected the J11 connector , in the terminal it gives everything exactly the same ashuxfluxdeluxecan 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 oftautech,ratmoleand others - you are competent guys and I ask for your help.

author: tautech
author_rank: Super Contributor
timestamp: March 30, 2021, 02:55:36 pm
content: Quote from: AlexZ on March 30, 2021, 02:48:51 pmWelcome to the forum.Hopefully without a SD card holder we can recover this with USB tools.PM sent.

author: tv84
author_rank: Super Contributor
timestamp: March 30, 2021, 02:58:20 pm
content: Quote from: AlexZ on March 30, 2021, 02:48:51 pmPay attention. Your is a SIGLENT SDS1152CML+! Don't confuse it with non + versions.

author: AlexZ
author_rank: Newbie
timestamp: March 30, 2021, 03:03:04 pm
content: Today I soldered the SD card holder, microSD is read by the mmc part command in uboot.

author: tautech
author_rank: Super Contributor
timestamp: March 30, 2021, 03:06:14 pm
content: Quote from: tv84 on March 30, 2021, 02:58:20 pmI suspect it is however how did you spot this ?LAN = + model.Some CML+ do have a SD card holder.

author: tautech
author_rank: Super Contributor
timestamp: March 30, 2021, 03:07:44 pm
content: Quote from: AlexZ on March 30, 2021, 03:03:04 pmCheck your messages.

author: AlexZ
author_rank: Newbie
timestamp: March 30, 2021, 03:13:28 pm
content: Quote from: tautech on March 30, 2021, 03:06:14 pmmicroSD was able to check with themmc partcommand inU-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

author: tv84
author_rank: Super Contributor
timestamp: March 30, 2021, 03:40:28 pm
content: Quote from: tautech on March 30, 2021, 03:06:14 pmYou'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.

author: AlexZ
author_rank: Newbie
timestamp: March 30, 2021, 06:46:58 pm
content: Quote from: tv84 on March 30, 2021, 03:40:28 pmCan the SIGLENT SDY8.007.107E CML_1700 motherboard number match SDS1152CML+ ?

author: tautech
author_rank: Super Contributor
timestamp: March 30, 2021, 07:27:27 pm
content: Quote from: tv84 on March 30, 2021, 03:40:28 pmYes of course and because it has a LAN socket itmustbe a + model.Anyways work to do getting Alex fixed up.

author: AlexZ
author_rank: Newbie
timestamp: March 31, 2021, 04:47:22 am
content: Hey! Thanks for the help, everything worked, special thanks totautech, andtv84for responding to my problem,tautechhelped with tools.

author: StillTrying
author_rank: Super Contributor
timestamp: March 31, 2021, 04:41:40 pm
content: 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 theon graticuleauto measurements, just voltage, time, or both, which covers more than half area of the screen.

author: Cicciousb
author_rank: Newbie
timestamp: June 01, 2021, 02:55:34 pm
content: 1. Remove the back cover of the SDS1102CML+ oscilloscope,2, Remove the metal back of the cage3. Connect RX,TX serial cables on the unpopulated J11 connector. Solder TX to the second pad and RX to the third pad.4. Connect to serial: Baudrate 1152005. Boot the oscilloscope, now you will see the boot log. If not, swap the RX,TX cables to your serial adaptorhi to all, i have try it but not detected, i dont see any log and siglent stuck on logo. any solution?

author: tautech
author_rank: Super Contributor
timestamp: June 01, 2021, 08:51:53 pm
content: Quote from: Cicciousb on June 01, 2021, 02:55:34 pmWelcome to the forum.PM sent.

author: Cicciousb
author_rank: Newbie
timestamp: June 02, 2021, 08:20:41 am
content: Thanks, is a pleasure

author: godfather
author_rank: Contributor
timestamp: November 06, 2021, 05:06:30 pm
content: @tautechHello , 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: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: lowlevel init failedUSB error: all controllers failed lowlevel initDownload 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 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ # ./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 referenceWith Pendrive 4GBCode: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--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... 0 Storage Device(s) foundDownload 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 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ # ./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

author: tautech
author_rank: Super Contributor
timestamp: November 06, 2021, 07:20:23 pm
content: Quote from: godfather on November 06, 2021, 05:06:30 pmDon't need logs.Send me PM.

author: Roman555
author_rank: Newbie
timestamp: September 22, 2022, 07:11:19 pm
content: @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.tautechis 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 firmwareI thanktautechfor his help and resources, and also this forum that connects people living all over the world.

author: tautech
author_rank: Super Contributor
timestamp: September 22, 2022, 08:14:22 pm
content: Quote from: Roman555 on September 22, 2022, 07:11:19 pmWelcome to the forum.PM returned.

author: Rybak27
author_rank: Newbie
timestamp: October 04, 2022, 08:14:00 am
content: 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

author: OMAR EDEL
author_rank: Newbie
timestamp: January 22, 2023, 04:04:41 am
content: 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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--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: lowlevel init failedUSB error: all controllers failed lowlevel initDownload 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 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ # check_and_upgrade:starting...mount_fs: rw,sync,ubi1_0,/usr/bin/siglent/usrubi1_0unattachedattach_ubi:datafsattach_ubi:11UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/usrTEST_RESTURN =is_fs_mounted 0 ---is_need_upgradeis_need_upgrade:not need upgradecheck_and_upgrade:end...++mount_check_copy_appdata: startingmount_fs: ro,sync,ubi2_0,/usr/bin/siglent/firmdata0ubi2_0unattachedattach_ubi:firmdata0attach_ubi:9UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0TEST_RESTURN =is_fs_mounted 0 -----mount_check_copy_appdata: endingLoad Fpga Failed!ECC failed: 0ECC corrected: 0Number of bad blocks: 0Number of bbt blocks: 0Block size 131072, page size 2048, OOB size 64Dumping data starting at 0x00000000 and ending at 0x00010000...

author: tautech
author_rank: Super Contributor
timestamp: January 22, 2023, 04:14:30 am
content: Quote from: OMAR EDEL on January 22, 2023, 04:04:41 amWelcome 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.

author: Cyrus755
author_rank: Newbie
timestamp: January 23, 2023, 07:46:01 pm
content: 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 logCode: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn119138 (Jul 22 2021 - 10:57:19)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7922musb-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: lowlevel init failedUSB error: all controllers failed lowlevel initDownload 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 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.

author: tautech
author_rank: Super Contributor
timestamp: January 23, 2023, 07:54:23 pm
content: Quote from: Cyrus755 on January 23, 2023, 07:46:01 pmWelcome to the forum.Button it up, we don't need logs.Contact me via PM with your email address.

author: vagalum147
author_rank: Newbie
timestamp: January 27, 2023, 04:41:39 pm
content: 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 youUPDATE: All is ok now! Thank you so much,tautech.

author: ocb2b
author_rank: Newbie
timestamp: February 25, 2023, 07:48:30 am
content: 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 ?

author: tautech
author_rank: Super Contributor
timestamp: February 25, 2023, 08:49:59 am
content: Quote from: ocb2b on February 25, 2023, 07:48:30 amSure.Send me a personal message with your email address.

author: ocb2b
author_rank: Newbie
timestamp: February 25, 2023, 07:58:37 pm
content: Massive thank you for your help.

author: tautech
author_rank: Super Contributor
timestamp: February 25, 2023, 08:03:06 pm
content: Quote from: ocb2b on February 25, 2023, 07:58:37 pmNo worries, you did all the work.Stick around and enjoy the forum.

author: jhnlmn
author_rank: Newbie
timestamp: June 18, 2023, 06:56:44 pm
content: Hi,My SDS1102CML+ prints "Uncompressing Linux... done, booting the kernel." and nothing more.I tried to flash files from P21R2.zip, which was posted inhttps://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg3280472/#msg3280472but 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

author: tautech
author_rank: Super Contributor
timestamp: June 18, 2023, 08:19:30 pm
content: Quote from: jhnlmn on June 18, 2023, 06:56:44 pmWelcome 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

author: jhnlmn
author_rank: Newbie
timestamp: June 19, 2023, 01:47:59 am
content: 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.

author: tautech
author_rank: Super Contributor
timestamp: June 19, 2023, 03:46:50 am
content: Quote from: jhnlmn on June 19, 2023, 01:47:59 amOh a boot freeze, that is different !Send a PM with your contact email and we'll have you fixed up in no time.

author: rdekens@internode.on.net
author_rank: Newbie
timestamp: June 27, 2023, 08:34:56 am
content: 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 furtherhave 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 streamas belowso 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‹¿¿¿# A7/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¿!¿! ¿=!;!!‹¿¿¿ïïï¿Ÿ¿åë# ¥;!!ƒ¿ ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||...RegardsRayman

author: Francesco
author_rank: Newbie
timestamp: July 13, 2023, 12:36:02 pm
content: Quote from: tautech on March 16, 2021, 07:23:15 pmGoogmorning 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 boardsSo...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 linkhttps://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 lotFrancesco

author: smittyinthesky
author_rank: Newbie
timestamp: July 16, 2023, 02:01:39 pm
content: 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: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: lowlevel init failedUSB error: all controllers failed lowlevel initDownload 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 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 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/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'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.

author: tv84
author_rank: Super Contributor
timestamp: July 16, 2023, 05:55:49 pm
content: Is the scope working or not?

author: smittyinthesky
author_rank: Newbie
timestamp: July 17, 2023, 01:07:28 pm
content: tautech got me up and running with proper recovery files. just working out the last few items, but it's back up and running.

author: tautech
author_rank: Super Contributor
timestamp: July 17, 2023, 06:01:24 pm
content: Quote from: smittyinthesky on July 17, 2023, 01:07:28 pmYup.Note to all, please don't go opening your scopes to sniff any data bus .....it's just not required !

author: dwhp
author_rank: Newbie
timestamp: October 14, 2023, 10:33:50 pm
content: 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

author: tautech
author_rank: Super Contributor
timestamp: October 15, 2023, 12:18:17 am
content: Quote from: dwhp on October 14, 2023, 10:33:50 pmWelcome 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/QC1934Send me a PM with your email address.

author: dwhp
author_rank: Newbie
timestamp: October 15, 2023, 08:46:37 am
content: 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.

author: tautech
author_rank: Super Contributor
timestamp: October 15, 2023, 08:55:31 am
content: Quote from: dwhp on October 15, 2023, 08:46:37 amYou'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.

author: aniko71
author_rank: Newbie
timestamp: February 19, 2024, 01:47:55 pm
content: 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.

author: cmmodem
author_rank: Newbie
timestamp: March 11, 2024, 05:24:31 pm
content: 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: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--U-Boot 2013.01.01-svn72327 (Jun 02 2021 - 18:19:21)I2C: readyDRAM: 128 MiBNAND: 256 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1Using default environmentset_default_env::7914musb-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: lowlevel init failedUSB error: all controllers failed lowlevel initDownload 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 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 inSegmentation faultSegmentation faultSegmentation faultSegmentation faultSegmentation faultSegmentation fault/etc/init.d/sysfs.sh: line 17: can't create /proc/sys/kernel/hotplug: nonexistent directorySegmentation faultSegmentation 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/nullcan'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/nullprocess '-/bin/sh' (pid 533) exited. Scheduling for restart.can't open /dev/ttyO0: No such file or directoryprocess '-/bin/sh' (pid 534) exited. Scheduling for restart.can't open /dev/ttyO0: No such file or directoryprocess '-/bin/sh' (pid 535) exited. Scheduling for restart.can't open /dev/ttyO0: No such file or directoryThanks for the help!Tautech , Thank you so much for the help! The oscilloscope has come back to life!! Awesome!

author: eeKnud
author_rank: Newbie
timestamp: April 20, 2024, 10:04:18 pm
content: 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/andchmod +'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 stick7. 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 scopeTodo : give scope to my son for his shop.Quote from: ratmole on February 10, 2021, 07:14:42 pm

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

author: Strateg58
author_rank: Contributor
timestamp: September 20, 2024, 11:49:40 am
content: Hi guys. I want to update the firmware of my Siglent SDS1102CML oscilloscope. But I'm afraid to get a brick. Does anyone have any sensible instructions on how to flash it? From a USB stick or from a Windows 10 laptop?

author: tautech
author_rank: Super Contributor
timestamp: September 20, 2024, 06:57:07 pm
content: Quote from: Strateg58 on September 20, 2024, 11:49:40 amPlus model ?Latest/last firmware version:https://int.siglent.com/upload_file/zip/firmware/Oscilloscope/SDS1000CML+_V6.01.01.25_EN.zipUnzip and study the PDF.

author: Strateg58
author_rank: Contributor
timestamp: September 20, 2024, 11:44:47 pm
content: No, not +. Where can I get the latest firmware?

author: tautech
author_rank: Super Contributor
timestamp: September 21, 2024, 12:04:21 am
content: Quote from: Strateg58 on September 20, 2024, 11:44:47 pmNo longer available from Siglent websites.Which version are you on as we may have a later version we can upload here buried in the archives.

author: Strateg58
author_rank: Contributor
timestamp: September 22, 2024, 08:08:19 pm
content: Quote from: tautech on September 21, 2024, 12:04:21 am

author: tautech
author_rank: Super Contributor
timestamp: September 22, 2024, 08:49:15 pm
content: Quote from: Strateg58 on September 22, 2024, 08:08:19 pm.32 attached for old CML models

author: Strateg58
author_rank: Contributor
timestamp: September 23, 2024, 09:30:05 am
content: Thanks.

author: tautech
author_rank: Super Contributor
timestamp: September 23, 2024, 09:31:52 am
content: Quote from: Strateg58 on September 23, 2024, 09:30:05 amSorry forgot to mention it's a zipped RAR folder so you'll need to unpack it twice.

author: Rapanui
author_rank: Newbie
timestamp: November 27, 2024, 05:01:31 pm
content: Dear TautecI saw on the forum that you helped a lot of people in the same situation as me. I hope you can help me too.I have an oscilloscope SDS1102CML+ that remains stuck on SIGLENTIt has already happened to me twice!- The first time: with Maths, it worked- The second time: Maths did not work, but by booting on a USB key, with the files "datafs.img", "ro_uImage"and "rootfs.img" at the root, it restarted.This time, neither MATHS nor the boot workCan you help me?Thank you in advance

author: tautech
author_rank: Super Contributor
timestamp: November 27, 2024, 07:29:40 pm
content: Quote from: Rapanui on November 27, 2024, 05:01:31 pmWelcome to the forum.Your USB stick is the problem.Reformat it to FAT32 and 4k clusters.Also it should be 8 GB max.Further notes.....some USB sticks do not work for recovery.There are a few tricks, Full/slow format and someone sent me this:None of my USB <- 8GB worked first time.Double checked FAT32 / 4k - but still no go.Thinking this has to be some MBR / UEFI issue.. I'm using W11 machines only...However - used Rufus to format one of my sticks as MBR - BIOS - MS-DOS.Deleted the DOS files from stick afterwards - and copied back the 3 files from your Mega link ... and VOILA :-)

author: Sergey78
author_rank: Newbie
timestamp: January 22, 2025, 11:43:30 am
content: Dear TautechI saw on the forum that you helped a lot of people in the same situation as me. I hope you can help me too.Initial data. The SIGLENT SDS1000DL+ series oscilloscope is stuck on the logo. The relays do not click. The keyboard backlight is on. The motherboard is SDY8.007.107E CML 170700.Connected to the J11 connector. The log is read when the oscilloscope is turned on. The log ends with the messageNAND 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.If you connect a USB flash drive with files from message #28, the log ends with the messageNAND 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 ..microsd card slot is not installed on the motherboard.Thanks in advance.Thank you very much! The recovery was successful.

author: iampeteandrews
author_rank: Newbie
timestamp: February 13, 2025, 05:47:03 pm
content: Hey All -first post / new member! I wanted to get a PM to @tautech in regards to me having the same issue with an 1102CML+ ( boots into the Util page and then is hung there ). But seems i need 10 posts before I can PM!so I'll follow along from the sidelines for the time being and make snarky comments.'thanks!-pete

author: tv84
author_rank: Super Contributor
timestamp: February 13, 2025, 05:49:05 pm
content: Quote from: iampeteandrews on February 13, 2025, 05:47:03 pmTry to pm him now.

author: iampeteandrews
author_rank: Newbie
timestamp: February 13, 2025, 06:59:48 pm
content: Well what do you know! I can PM now.However that was made possible... THANK YOU!!-pete

author: tautech
author_rank: Super Contributor
timestamp: February 13, 2025, 07:09:21 pm
content: Quote from: iampeteandrews on February 13, 2025, 05:47:03 pmFlick the chaps in Ohio a message for the recovery tools:support@siglentna.com

author: iampeteandrews
author_rank: Newbie
timestamp: February 13, 2025, 07:10:51 pm
content: @tautech - will do.thanks...-pete

author: iampeteandrews
author_rank: Newbie
timestamp: February 18, 2025, 02:43:53 pm
content: do these guys take a while to reply?I'll try them again... but haven't heard anything.-pete

author: iampeteandrews
author_rank: Newbie
timestamp: February 18, 2025, 04:29:11 pm
content: nevermind!they did get back - found the reply in the junk folder.trying their recovery procedure now... will report back!-pete

author: iampeteandrews
author_rank: Newbie
timestamp: February 18, 2025, 05:18:53 pm
content: success!after downloading the recovery files / putting them on a FAT32 usb drive / booting the unit up with the drive already inserted ( then waiting !! ) / one more reboot , we have a working scope.thanks tautech!-pete

author: spyderbdm
author_rank: Newbie
timestamp: May 25, 2025, 04:41:34 pm
content: I have a Siglent SDS 1102CML+ that I’ve had for a few years but only use it on occasion. Last time I used it about two months ago, everything worked fine. This morning I go to use it, and get stuck in the boot sequence at the logo splash screen. I’ve never updated the firmware, but will if I can ever use the OS again. It appears that this is a very common issue that only one man on the planet is willing and able to fix…but I’m new to the eevblog and cant PM yet; @tautech. Can anyone help get me in touch? Serial#: SDS1MEBQ2R5378

author: spyderbdm
author_rank: Newbie
timestamp: May 25, 2025, 04:50:50 pm
content: Any chance of getting a copy of the recovery files from you? I wish Siglent made these more accessible seeing how widespread this issue is. I can’t PM yet b/c not enough posts.

author: KungFuJosh
author_rank: Super Contributor
timestamp: May 25, 2025, 05:31:04 pm
content: You don't need to share your serial number here.You can contact SiglentNA directly, and they'll share the needed recovery with you.Thanks,Josh

author: tautech
author_rank: Super Contributor
timestamp: May 25, 2025, 07:55:59 pm
content: Quote from: spyderbdm on May 25, 2025, 04:41:34 pmThe current USB recovery package will restore the OS and install the latest FW version.Give Ohio a message:https://siglentna.com/contact-us/

author: mic315
author_rank: Newbie
timestamp: September 01, 2025, 10:12:44 pm
content: Hello, I have the same problem with the logo frozen at startup (SDS1000CML+), I have tried all methods, I have access to the USB key, the programs launch well, but always the same screen, please help me. Here is the startup process:Quote

author: tautech
author_rank: Super Contributor
timestamp: September 01, 2025, 10:40:50 pm
content: Quote from: mic315 on September 01, 2025, 10:12:44 pmIf showing a French flag, Siglent EU HQ is your first point of contact for their USB recovery package.https://www.siglenteu.com/contact-us/

author: dec123ua
author_rank: Newbie
timestamp: September 08, 2025, 12:16:55 pm
content: Hi all, my SDS1102CML+ killed after uncorrect update.Could you please send me repair update pack or NAND image for upload directly via programmatorNow unit started U-Boot only

author: tautech
author_rank: Super Contributor
timestamp: September 08, 2025, 09:06:59 pm
content: Quote from: dec123ua on September 08, 2025, 12:16:55 pmRecovery is only done via a USB recovery package.Looking at your flag, EU HQ is your nearest point of contact:https://www.siglenteu.com/contact-us/

author: dec123ua
author_rank: Newbie
timestamp: September 09, 2025, 04:19:19 pm
content: I successfully restored my oscilloscope SDS1102CML+ using the files sent by technical support and TFTP

author: electronic2000
author_rank: Newbie
timestamp: September 13, 2025, 06:46:48 am
content: Hello everyone! I have the same problem with Siglent SDS 1102CML+ . During startup, a logo appears on the screen and a single relay click .I contacted Siglent and they sent me a USB recovery file. However, recovery from USB and SD cards doesn't work.QuoteCan someone help? I'm out of ideas.Thank You

author: tautech
author_rank: Super Contributor
timestamp: September 13, 2025, 06:57:27 am
content: Quote from: electronic2000 on September 13, 2025, 06:46:48 amWelcome to the forum.USB recovery files are ONLY for use with USB !You may have done more damage to the OS !USB sticks must be properly formatted as per instructions and all recovery files placed in the root folder.Some I have assisted have tried 10 sticks, yes 10 before one would work.

author: electronic2000
author_rank: Newbie
timestamp: September 13, 2025, 07:23:56 am
content: Hello tautech.I've already tried 8 pendrives. They were formatted as FAT32 and 4k cluster, and all the files were in the root folder.I don't have any more pendrives with a capacity below 8GB.I need to buy more . Do you have a model that works?Are you sure that my version of oscilloscope is able to boot from a pendrive?In the console I see that the oscilloscope boots directly from the NAND memory and does not check the USB device. Is it correct behavior.Thank You

author: tautech
author_rank: Super Contributor
timestamp: September 13, 2025, 09:17:33 am
content: Quote from: electronic2000 on September 13, 2025, 07:23:56 amTry larger as they have been known to work.Quote100%QuoteIf the USB stick is incompatible, yes.

author: werliock
author_rank: Newbie
timestamp: October 02, 2025, 07:16:46 am
content: Hello, I'm new here, and I've found this forum because I had the same issue. Thanks to @tautech recommendations, I've asked to Siglent for the recovery files and my oscillocope is alive!But I have a doubt... On the instruccions pdf it says: "When the device recover successfully, please delete all the recovery files". Does it refer to the files into the USB, or some recovery files placed on the oscilloscope after restoration?Thank you so much!!

author: tautech
author_rank: Super Contributor
timestamp: October 02, 2025, 08:05:03 am
content: Quote from: werliock on October 02, 2025, 07:16:46 amOnly those on your USB stick so that if it's inserted in the scope at boot the recovery files don't automatically run again.By all means keep them on your PC if you feel the need or just bookmark the download link.

author: wroverbob
author_rank: Newbie
timestamp: October 18, 2025 07:24:05 am
content: Hello,Here is a SDS1102CNL+ with the logo frozen at startup. I have tried the firmware recovery guide inhttps://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/msg3457924/#msg3457924, the UART log shows that `ro_uImage` (offset 0x3080000, which is `kernel`) and `datafs.img` (offset 0x9a80000) were flashed according to the files provided at that post. But the `rootfs.img` file is missing, thus `rootfs` seems untouched.After that operation, the osilloscope still looks frozen at startup. The BusyBox shell is accessable through the UART port, but scripts placed in the USB flash device is probably not executed, and I can't mount the USB disk (which is at least recognized by U-Boot) according to the guide mentioned above: there's no `/dev/sda1`.The "updated" application (and kernel?) is probably incompatible with the original `rootfs.img`. Someone has shown that the full USB firmware recovery package is much larger than the files provide in the@ratmole's post, if I recall correctly.@tautechI have emailed to Siglent asking for the recovery file, however they haven't replied yet. Would you please send the full USB recovery package to me?The UART log during operation:Code: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=800Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0Lcd_Init()--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 1354 ms (1.5 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 1314 ms (1.5 MiB/s)NAND erase: device 0 offset 0x9a80000, size 0x6580000Erasing at 0xffe0000 -- 100% complete.OKNAND write: device 0 offset 0x9a80000, size 0x150000022020096 bytes written: OKreading logo.bmp** Unable to read file logo.bmp **Booting from nand ...NAND read: device 0 offset 0x3080000, size 0x3000003145728 bytes read: OK## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.2.0+Image Type: ARM Linux Kernel Image (uncompressed)Data Size: 2157768 Bytes = 2.1 MiBLoad Address: 80008000Entry Point: 80008000Verifying Checksum ... OKLoading Kernel Image ... OKOKStarting kernel ...Uncompressing Linux... done, booting the kernel.init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)starting pid 519, tty '': '/etc/init.d/rcS'rS in/etc/init.d/rcS: line 15: setterm: not foundstarting pid 536, tty '/dev/ttyO0': '-/bin/sh'Processing /etc/profile... Done/ # ./SDS1000_arm.app: relocation error: /lib/libpthread.so.0: symbol _zdefault_sa_restorer_v2, version GLIBC_PRIVATE not defined in file libc.so.6 with link time referenceTrying to execute the application manually:Code:/ # /usr/bin/siglent/SDS1000_arm.app/usr/bin/siglent/SDS1000_arm.app: relocation error: /lib/libpthread.so.0: symbol _zdefault_sa_restorer_v2, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference/ # ls -l /usr/bin/siglent-rwxr-xr-x 1 root root 9231014 Jan 1 00:00 SDS1000_arm.appdrwxrwxrwx 2 1000 ding 320 Jul 30 2015 configdrwxrwxrwx 2 1000 ding 800 Jan 1 00:00 driversdrwxr-xr-x 2 1000 ding 160 Dec 21 2015 firmdata0drwxrwxrwx 2 1000 ding 240 Jan 1 00:00 fpgadrwxrwxrwx 2 1000 ding 304 Dec 21 2015 upgradedrwxrwxrwx 2 1000 ding 160 Jul 30 2015 usr/ # ls -l /lib...-rwxrwxrwx 1 1000 ding 1185216 Jan 13 2015 libc.so.6...-rwxrwxrwx 1 1000 ding 88472 Jan 13 2015 libpthread.so.0.../ # cat /proc/versionLinux version 3.2.0+ (ding[member=188039]ding-desktop) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #716 Fri Dec 18 16:33:18 ULAT 2015(String `GCC: (GNU) 4.5.3 20110311 (prerelease)` is also found in the flashed `SDS1000_arm.app` file)Code:/ # ls /sys/bus/usb/devices/ # dmesgdmesg: klogctl: Function not implemented/ # lsusb-/bin/sh: lsusb: not found/ # mountrootfs on / type rootfs (rw)ubi0:rootfs on / type ubifs (ro,relatime)proc on /proc type proc (rw,relatime)sysfs on /sys type sysfs (rw,relatime)mdev on /dev type tmpfs (rw,relatime)devpts on /dev/pts type devpts (rw,relatime,mode=600)none on /sys/kernel/debug type debugfs (rw,relatime)/ # ls /devGpmc mtdblock8 tty33console mtdblock9 tty34cpu_dma_latency network_latency tty35device network_throughput tty36fpga_key null tty37full psaux tty38i2c-1 ptmx tty39i2c-2 pts tty4kmem ram0 tty40kmsg ram1 tty41loop-control ram10 tty42loop0 ram11 tty43loop1 ram12 tty44loop2 ram13 tty45loop3 ram14 tty46loop4 ram15 tty47loop5 ram2 tty48loop6 ram3 tty49loop7 ram4 tty5mem ram5 tty50mice ram6 tty51mtd0 ram7 tty52mtd0ro ram8 tty53mtd1 ram9 tty54mtd10 random tty55mtd10ro spidev1.0 tty56mtd11 spidev1.1 tty57mtd11ro tty tty58mtd1ro tty0 tty59mtd2 tty1 tty6mtd2ro tty10 tty60mtd3 tty11 tty61mtd3ro tty12 tty62mtd4 tty13 tty63mtd4ro tty14 tty7mtd5 tty15 tty8mtd5ro tty16 tty9mtd6 tty17 ttyO0mtd6ro tty18 ttyO1mtd7 tty19 ttyO2mtd7ro tty2 ttyO3mtd8 tty20 ttyO4mtd8ro tty21 ttyO5mtd9 tty22 ubi0mtd9ro tty23 ubi0_0mtdblock0 tty24 ubi_ctrlmtdblock1 tty25 urandommtdblock10 tty26 vcsmtdblock11 tty27 vcs1mtdblock2 tty28 vcsamtdblock3 tty29 vcsa1mtdblock4 tty3 watchdogmtdblock5 tty30 zeromtdblock6 tty31mtdblock7 tty32

author: wroverbob
author_rank: Newbie
timestamp: October 18, 2025 10:34:01 am
content: I just found an imperfect method for dumping raw NAND flash data fastly (currently without OOB). During the freeze of the splash screen, connect the scope to the PC via a network cable, then execute these commands via UART BusyBox shell to start a TFTP server on the device:Code:mount --remount --rw rootfsifdown eth0ifup eth0ifconfig eth0 add 192.168.138.140 netmask 255.255.255.0mount --remount --ro rootfsudpsvd -vE 0.0.0.0 69 tftpd /In which `192.168.138.140` can be changed according to your PC's ethernet IP address.On Windows PC: tftp -i 192.168.138.140 get /dev/mtd4Dumping speed is about 500KB/s. The sum of sizes of mtd0~mtd11 dumps is exactly 256MB.NOTE: Dumping mtdX devices is just reading raw partitions without spare data!I also tried dumping `/dev/ubi0_0` and took a quick glance of the raw data, it's probably just a high-level mapping of `/dev/mtd7`. As for now, I just know how to read OOB data for every page with `nand` under U-Boot. Under Linux, it probably requires writing some code and compiling it into an executable targeting Linux 3.2 (ARMv7) or even a kernel module, which is too complicated to me.I've also found that U-Boot pings the host PC successfully after setting `ipaddr` and `netmask` variables in U-Boot. I should be able to "boot image via network using BOOTP/TFTP protocol" after configuring on the host PC in some ways, but this version of U-Boot might not be able to upload files to the PC via TFTP. Serial port transfer is slow...

author: rf-loop
author_rank: Super Contributor
timestamp: October 18, 2025 11:26:18 am
content: You've probably noticed that you're talking about the SDS1102CNL+ model and elsewhere in this thread we're mainly talking about the SDD1102CML+ model.Both model series (CNL+ and CML+) have their own USB boot recovery package.This is for your CNL+ model:SDS1000CNL+_USB Recovery.ziprootfs.img CRC32 = BB4223EBdatafs.img CRC32 = D95340C8ro_uImage CRC32 = A1F4A7ACOthers are for CML+ models.SDS1000CML+ series SD-card recovery.zipSDS1000CML+_P25 USB recovery.zipThey should not be confused with each others under any circumstances. It is assumed that the users of these recovery packages read carefully least model numeber and instructions and also it is one reason, together with other reasons, why these are not in public share. Do not use anything but genuine original recovery packs which is intended for exactly the device it is used for. They do not have "blonde" protection.Sometimes some USB do not work, and some other works.Also then there's the formatting of the USB stick. For example, performing a normal full or quick format in Windows is not always enough.Among other things, Windows' diskpart.exe is an good tool for completely reformatting a disk for FAT32, starting with the clean command.I've sometimes encountered problems with USB recoveries and sometimes that complete "deep" formatting of the disk has helped.

author: wroverbob
author_rank: Newbie
timestamp: October 18, 2025 02:47:37 pm
content: @rf-loopExcuse me, I was confused by SDS1000DL+_V6.02.01.13_EN ADS package available at Siglent EU site (Release Date 02.08.23,https://siglentna.com/download/36724/?tmstv=1760705884) and the SDS1000DL+_V6.02.01.13_CN ADS package available at Siglent CN site (the same release date,https://siglent.oss-cn-shenzhen.aliyuncs.com/firmware/Oscilloscope/SDS1000DL%2B_V6.02.01.13_CN.zip):The EN instructions claims that the firmware is made for SDS1000DL+/CML+, while the CN instructions claims that it's for SDS1000A/SDS1000CNL+/SDS1000DL+/SDS1122E+/SDS1202F+. But the two packages actually contain the same ADS file. This is why I used to think that firmwares for SDS1000CNL+ and SDS1000CML+ can be the same. According to your notes, it's probably not the case when doing real "full" firmware upgrade.I wouldn't have tried the partial firmware recovery package for SDS1000CML+ (which is made public by@ratmole) if the recovery package for SDS1000CNL+ had been made public. My email iswuwbobo2@outlook.com, would you please send the `SDS1000CNL+_USB Recovery.zip` to me? Otherwise I will have to stick with@ratmole's package after managing to back up NAND spare data, maybe uploading these unpacked files through TFTP and executing the update script.Appended: CRC32 values of `datafs.img` and `ro_uImage` found in `P21R2.7z` (provided by @ratmole for SDS1000CML+) are the same as the values shown in your last post (for SDS1000CNL+_USB Recovery.zip). I just need to solve the `rootfs` problem.

author: rf-loop
author_rank: Super Contributor
timestamp: October 18, 2025 05:33:15 pm
content: You have email.