Products > Test Equipment
Siglent SDS1102CML+ non-responsive: Any ideas?
<< < (3/6) > >>
BobRyan:

--- Quote from: tv84 on March 17, 2020, 10:57:59 am ---If you have nothing to loose, I suggest opening it and try find a UART output to see any boot log.

Don't remember if these BF machines have boot log... must be from the virus.  |O

--- End quote ---

I couldn't find any serial output from mine
ratmole:
If anyone has problems with stuck logo on boot, try this:

1. Remove the back cover of the SDS1102CML+ oscilloscope,
2, Remove the metal back of the cage
3. Connect RX,TX serial cables on the unpopulated J11 connector. Solder TX to the second pad and RX to the third pad.
4. Connect to serial: Baudrate 115200
5. Boot the oscilloscope, now you will see the boot log. If not, swap the RX,TX cables to your serial adaptor.
6. Unzip the contents of the P21R2.zip in a fat32 formated usb stick. Also unzip the SDS1000_arm.zip and copy the SDS1000_arm.app to the root of the usb flash drive.
7. Connect the usb flash drive to the oscilloscope and power off and the on the oscilloscope.
8. Let the oscilloscope to perform the FW Recovery.
9. Remove the usb flash drive and Reboot
10. done!

If  the oscilloscope still hangs on the boot logo
Start the oscilloscope without the usb flash drive.
When the boot is complete, but still on logo
Insert the usb flash drive and type in the serial console:


--- Code: ---mount /dev/sda1 /mnt
mount / -o remount,rw
cp /mnt/SDS1000_arm.app /usr/bin/siglent/SDS1000_arm.app
chmod +x  /usr/bin/siglent/SDS1000_arm.app
mkdir -p /usr/bin/siglent/firmdata0/usr/log
cd /usr/bin/siglent/
./SDS1000_arm.app
--- End code ---

Now the oscilloscope is back to life!
Please perform a hardware reset using the Math button method and you are good as new.

a big thanks to tv84 and tautech for their help!
nvincis88:
Hello,

I have same issue, the oscilloscope still hangs on the boot logo.

I tried the instruction above, but nothing succed.

The "SDA1" folder doesn't exist into the "/dev" folder.

Below you can see the log of boot.

Thanks a lot


--- Code: ---U-Boot 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)

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

set_default_env::7864
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
(Re)start USB...
USB0:   scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Download Linux from USB to Nandflash...
reading ro_uImage
2157832 bytes read in 1295 ms (1.6 MiB/s)

NAND erase: device 0 offset 0x3080000, size 0x500000
Erasing at 0x3560000 -- 100% complete.
OK

NAND write: device 0 offset 0x3080000, size 0x500000
 5242880 bytes written: OK
reading rootfs.img
** Unable to read file rootfs.img **
reading datafs.img
2097152 bytes read in 1273 ms (1.6 MiB/s)

NAND erase: device 0 offset 0x9a80000, size 0x6580000
Erasing at 0xffe0000 -- 100% complete.
OK

NAND write: device 0 offset 0x9a80000, size 0x1500000
 22020096 bytes written: OK
reading logo.bmp
** Unable to read file logo.bmp **
Booting from nand ...

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

Starting kernel ...

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

Processing /etc/profile... Done

/ # check_and_upgrade:starting...
mount_fs: rw,sync,ubi1_0,/usr/bin/siglent/usr
ubi1_0unattached
attach_ubi:datafs
attach_ubi:11
UBI device number 1, total 812 LEBs (103104512 bytes, 98.3 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/usr
TEST_RESTURN =
is_fs_mounted 0 ---
is_need_upgrade
is_need_upgrade:not need upgrade
check_and_upgrade:end...
++mount_check_copy_appdata: starting
mount_fs: ro,sync,ubi2_0,/usr/bin/siglent/firmdata0
ubi2_0unattached
attach_ubi:firmdata0
attach_ubi:9
UBI device number 2, total 400 LEBs (50790400 bytes, 48.4 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
MOUNT_DIR_NAME = /usr/bin/siglent/firmdata0
TEST_RESTURN =
is_fs_mounted 0 ---
--mount_check_copy_appdata: ending
Load Fpga Success!
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!
terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_ios::clear

--- End code ---
conair7:
Hi,

I'm facing similar problem with the SDS1102CML+ device, but when it's boot (Siglent logo on screen) it hangs on:


--- Code: ---Starting kernel ...
Uncompressing Linux... done, booting the kernel.
--- End code ---

The USB is not powered up, internal green led blinking.
I'm aware of this thread: https://www.eevblog.com/forum/testgear/help-restore-sds1000cml-after-unsuccessful-flashing/ but he firmware was not updated since the purchase (~2018).
9a5n:
I have similar problem with SDS1050DL+.
Unit works well for many year (from 2016.) until a few days ago.

After boot finish, everything working well for 5-6 seconds and then screen and keys hang.
I contacted Siglent, and they sent me a zip file "System Recovery by U-disk".
I found some old 4GB USB drive and format it in FAT32.
3 files from zip has been copied to root.
After power on, the unit doesn't seem to see the USB drive during boot.
LED on USB drive start to blink when boot finish and unit came in operation.
Of coarse, after 5 seconds screen freeze and keys not working anymore.

From system status I read out:
Software Version 6.02.01.02      50M
Hardware Version 0-64-3.0
Serial No. SDS10BA1160348

What I am doing wrong?
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod