Author Topic: Help restore SDS1102CML+ after unsuccessful flashing  (Read 18939 times)

0 Members and 1 Guest are viewing this topic.

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Help restore SDS1102CML+ after unsuccessful flashing
« on: November 03, 2019, 01:40:04 pm »
After an erroneous firmware, the device turned into almost a brick.
I opened the device, found UART and looked at what was going on inside the device. The bottom line is that the application /usr/bin/siglent/SDS1000_arm.app responsible for the operation of the device crashes with an error:

Code: [Select]
/ # check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
The Help file load OK!!
Could not create log file: File exists
COULD NOT CREATE LOGFILE '19700101-000005.534'!
I0101 00:00:05.250442   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.271838   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

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

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


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

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

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

Please help to resurrect the device.

Update 05.03.2020

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

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #1 on: November 04, 2019, 12:31:37 am »
What .ADS did you flash?
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #2 on: November 04, 2019, 09:15:56 am »
Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

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

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

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

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

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

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

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #3 on: November 04, 2019, 09:35:16 am »
This is how the full load of the device from the moment of power supply looks:
Code: [Select]
U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
Booting from nand ...

NAND read: device 0 offset 0x3080000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.2.0+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2157768 Bytes = 2.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)
starting pid 519, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
The Help file load OK!!
Could not create log file: File exists
COULD NOT CREATE LOGFILE '19700101-000005.534'!
I0101 00:00:05.193285   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.214703   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

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

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


If during boot, use any key, then we get into the bootloader. In which you can see all the download options provided in it:
Code: [Select]
U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)

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

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

Environment size: 7391/131068 bytes


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

Any ideas what can be done?
 

Offline StillTrying

  • Super Contributor
  • ***
  • Posts: 2850
  • Country: se
  • Country: Broken Britain
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #4 on: November 04, 2019, 12:05:54 pm »
Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

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

Quote
I am ready for almost any experiment.

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

There's only 6 or 7 CML+ posters here, and 3 of them are stuck in some way. :(
.  That took much longer than I thought it would.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #5 on: November 04, 2019, 12:16:34 pm »
Here's what happens after you press MATH:
Code: [Select]
U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
Booting from nand ...

NAND read: device 0 offset 0x3080000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.2.0+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2157768 Bytes = 2.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)
starting pid 519, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
format_fs++
Erasing 128 Kibyte @ 6560000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
format_fs--
The system is going down NOW!
Sending SIGTERM to all processes
Requesting system reboot

U-Boot SPL 2013.01.01-svn22880 (Dec 23 2015 - 15:35:13)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


U-Boot 2013.01.01-svn22880 (Dec 23 2015 - 15:53:58)

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

set_default_env::7090
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
Booting from nand ...

NAND read: device 0 offset 0x3080000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 80200000 ...
   Image Name:   Linux-3.2.0+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2157768 Bytes = 2.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
init started: BusyBox v1.13.2 (2012-04-08 17:28:57 CDT)
starting pid 519, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 15: setterm: not found
starting pid 536, tty '/dev/ttyO0': '-/bin/sh'

Processing /etc/profile... Done

/etc/init.d/rcS: line 24: portmap: Structure needs cleaning
/ # check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
The Help file load OK!!
I0101 00:00:05.855635   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:05.873046   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

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

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

/ #


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

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #6 on: November 04, 2019, 12:29:43 pm »
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.)
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #7 on: November 04, 2019, 01:50:43 pm »
those. do i have a hardware problem? And do I need to replace NAND with another? But where to get the BIN file for flashing the new NAND?

Or did I understand something wrong?

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

PS

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

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

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

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #8 on: November 04, 2019, 01:58:26 pm »
Tell me, do I think that NAND is precisely this chip on the board?
Or I'm wrong?
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #9 on: November 04, 2019, 07:48:14 pm »
Downloaded from here: https://www.siglent.eu/Downloads
Section: SDS1000CML + Series Digital Storage Oscilloscopes
The latest version: SDS1000CML + Firmware - 6.01.01.21R2 (Release Date 09.25.19) Download

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

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

Now I don’t know what to do ... I really do not want to buy a new one. I believe that there is a way to restore it to work.
I checked the FW link and it points to the Siglent America site where I get the same file size from so it should be OK.

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

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

Edit
Please confirm the label badge of this DSO as rebadged Siglents are supplied into Russia.
If it was being flashed with Siglent FW a .config file is also needed.
« Last Edit: November 04, 2019, 07:53:53 pm by tautech »
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #10 on: November 04, 2019, 07:52:27 pm »
Wow! I think you got a problem in that .app file.

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

The parsing of that .ADS is attached.

Edit: I include the file.
« Last Edit: November 04, 2019, 08:01:58 pm by tv84 »
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #11 on: November 05, 2019, 04:50:16 am »
@Zhenja
I have SDS1kCML+ USB recovery files now that I can email. (the factory was very quick to reply and send them)
It is 12.5MB zip file so contact me via PM and I can get them to you when I have your email.
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #12 on: November 05, 2019, 04:51:47 pm »
@tv84

Thanks so much for providing the SDS1000_arm.app application.
Running the application in USB flash drive did not bring success :(
The first launch was long and there was an error:
Code: [Select]
 I/O warning : failed to load external entity "/usr/bin/siglent/usr/log/111/config/NSP_config_upgrade_info.xml"
Here is the complete conclusion:
Code: [Select]
check_and_upgrade:starting...
mount_fs: rw,ubi1_0,/usr/bin/siglent/usr
ubi1_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN = ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
is_fs_mounted 1 --- ubi1_0 /usr/bin/siglent/usr ubifs rw,relatime 0 0 /dev/sda1 /usr/bin/siglent/usr/log/111 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
mount: mounting ubi1_0 on /usr/bin/siglent/usr failed: Device or resource busy
mount_fs: mounted
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0attached
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN = ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
is_fs_mounted 1 --- ubi2_0 /usr/bin/siglent/firmdata0 ubifs ro,relatime 0 0
mount: mounting ubi2_0 on /usr/bin/siglent/firmdata0 failed: Device or resource busy
mount_fs: mounted
--mount_check_copy_appdata: ending
Load Fpga Success!
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 0
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00010000...
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
I0101 00:01:18.966090   704 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:01:18.969528   704 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------

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

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

[1] + Done(1)                    ./SDS1000_arm.app
/usr/bin/siglent/usr/log/111 #

I copied the necessary files to the directory where the program is looking for them, but the application still does not start :(

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

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

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

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

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

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

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


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

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

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


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

Although the line confuses me:
Code: [Select]
Erasing 128 Kibyte @ 20000 -- 100 % complete
but this did not affect the original behavior of the device.

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

@tautech
I sent my contacts in a personal message.
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #13 on: November 05, 2019, 05:05:06 pm »
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.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #14 on: November 05, 2019, 06:17:21 pm »
Let's try to find out what I really flooded. It became interesting to myself...

SDS1000_arm.app -> CRC32: 723008D8

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

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #15 on: November 05, 2019, 07:13:09 pm »
@tautech
I sent my contacts in a personal message.
Replied with the conditions of use.

Let's try to find out what I really flooded. It became interesting to myself...
Understood, just let me know when/if you still want the recovery package.
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #16 on: November 06, 2019, 08:58:40 am »
@tautech

I gave you a complete answer in the mail.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #17 on: November 06, 2019, 09:03:46 am »
@tautech

I gave you a complete answer in the mail.
Files sent.  :)
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #18 on: November 09, 2019, 01:24:18 pm »
Hello. I apologize for the long reply. I was on a business trip.

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

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

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

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #19 on: November 09, 2019, 08:22:11 pm »
The .app file that you have in the scope is bad.

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

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

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


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

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

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #20 on: November 09, 2019, 08:39:17 pm »
@tv84
We are both working on this ATM and I have a unit unpacked trying a few things.
The recovery files from Siglent only work with V 19 or 20 FW according to them.   :-//
I will talk to them more in the next few days.


And BTW I'm looking at those CML+ key press sequences you posted a week or two back......no success with them yet.  :(
Others I know about  :-X work OK so I'm not sure if I'm in the right mode to get yours to work.  :-//
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline ZhenjaTopic starter

  • Contributor
  • Posts: 11
  • Country: ru
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #21 on: November 09, 2019, 09:30:58 pm »
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.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #22 on: November 09, 2019, 09:44:11 pm »
Due to the rush and my carelessness, I “erased” the bootloader. The device no longer turns on at all.
There are 3 ways left:
1) Soldering iron and programmer - filling in the dump (here I just do not have it)
2) find a way to flash a nand flash without a soldering iron (but there is no dump)
3) buy a new device and NEVER UPDATE IT MORE.
Please leave the HW until we get a fix from Siglent, see my findings below.....

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

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


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 !
« Last Edit: November 11, 2019, 02:18:33 am by tautech »
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3322
  • Country: pt
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #23 on: November 09, 2019, 10:40:09 pm »
Version 6.01.01.21R2 will NOT load over V20  >:(

 :wtf:

Explain me this as if I were 4 years old.
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 29491
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Help restore SDS1102CML+ after unsuccessful flashing
« Reply #24 on: November 09, 2019, 10:49:45 pm »
Version 6.01.01.21R2 will NOT load over V20  >:(

 :wtf:
Yes,  :wtf:  :rant:
Quote
Explain me this as if I were 4 years old.
The message to NOT cut power NEVER finishes !
The FW is NOT installed ....NO progress bar and the unit does NOT auto reboot as indicated in the update instructions.

3 different USB sticks tested ! Factory Default tried .......FW's broken JIM !
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf