Author Topic: Siglent .ads firmware file format  (Read 181547 times)

0 Members and 1 Guest are viewing this topic.

Offline gman76

  • Contributor
  • Posts: 32
  • Country: us
Re: Siglent .ads firmware file format
« Reply #400 on: August 05, 2020, 04:59:31 am »
I have the scopes at the office on a corporate network. There’s a sneaky way to copy a file from the PC to an external usb drive so that it doesn’t get encrypted. Involves the file extension.
 

Offline voronin_10

  • Newbie
  • Posts: 2
  • Country: ua
  • wise man
    • my instagram
Re: Siglent .ads firmware file format
« Reply #401 on: October 14, 2020, 07:55:40 pm »
Hi friend, i have bad osciloscome,
a need to decompres ads file to arhive

my osciloscp after flashing as brick,
but U-boot is alive annd need  3 files
this is console out:
Code: [Select]
Download Linux from USB to Nandflash...
reading ro_uImage
** Unable to read file ro_uImage **
reading rootfs.img
** Unable to read file rootfs.img **
reading datafs.img
** Unable to read file datafs.img **
reading logo.bmp
** Unable to read file logo.bmp **
Booting from nand ...



how to mount or extract this files of the update file?
https://siglentna.com/download/15283/
siglent sds1102cml+

good update log 


Code: [Select]
[00]
U-Boot SPL 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


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

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

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

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 @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 -- 50 % complete
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!

I0101 00:00:10.805797   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:10.828555   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------
 
I0101 00:00:10.858596   534 module.cpp:464] rm -f /usr/bin/siglent/usr/log/Info_19700101-000010.534
I0101 00:00:11.086069   534 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------
 
vxi11_main = 11206
init_lcd_driver()++
g_vinfo.xres = 800
g_vinfo.yres = 480
g_vinfo.bits_per_pixel = 16
E0101 00:00:13.605361   655 dev_interpreter.cpp:332] the device = /dev/sda mount fail
I0101 00:00:13.653393   655 dev_interpreter.cpp:338]
        №ТФШUЕМ /usr/bin/siglent/usr/media/U-disk0    device = /dev/sda1
 

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 -- 50 % complete
Erasing 128 Kibyte @ 20000 -- 100 % complete

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 -- 50 % complete
Erasing 128 Kibyte @ 20000 -- 100 % complete
FileHeader.product_type == 10000
version_flag == 1
xml_upgrade_id = 10000
Archive:  /usr/bin/siglent/usr/usr/upgrade/config.zip
  inflating: SDS1000_arm.app
  inflating: sds1000_fpga.rbf
  inflating: siglentlib.sh
  inflating: ti81xx.ko
  inflating: u-boot.img
  inflating: udc-core.ko
  inflating: update.sh
  inflating: upgrade.sh
  inflating: cfbcopyarea.ko
  inflating: cfbfillrect.ko
  inflating: cfbimgblt.ko
  inflating: da8xx-fb.ko
  inflating: datafs.img
  inflating: firmdata0.img
  inflating: g_usbtmc.ko
  inflating: gpib.ko
  inflating: help.bin
  inflating: libglog.so.0
  inflating: MLO
  inflating: musb_hdrc.ko
  inflating: NSP_config_upgrade_info.xml
  inflating: ro_uImage
  inflating: rw_uImage
update.sh starting ...
ubi0:rootfs / ubifs ro,relatime 0 0
rootfs ro
upgrade /usr/bin/siglent/usr/usr/upgrade/rw_uImage

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 --  2 % complete
Erasing 128 Kibyte @ 40000 --  4 % complete
Erasing 128 Kibyte @ 60000 --  6 % complete
Erasing 128 Kibyte @ 80000 --  8 % complete
Erasing 128 Kibyte @ a0000 -- 10 % complete
Erasing 128 Kibyte @ c0000 -- 12 % complete
Erasing 128 Kibyte @ e0000 -- 14 % complete
Erasing 128 Kibyte @ 100000 -- 16 % complete
Erasing 128 Kibyte @ 120000 -- 18 % complete
Erasing 128 Kibyte @ 140000 -- 20 % complete
Erasing 128 Kibyte @ 160000 -- 22 % complete
Erasing 128 Kibyte @ 180000 -- 25 % complete
Erasing 128 Kibyte @ 1a0000 -- 27 % complete
Erasing 128 Kibyte @ 1c0000 -- 29 % complete
Erasing 128 Kibyte @ 1e0000 -- 31 % complete
Erasing 128 Kibyte @ 200000 -- 33 % complete
Erasing 128 Kibyte @ 220000 -- 35 % complete
Erasing 128 Kibyte @ 240000 -- 37 % complete
Erasing 128 Kibyte @ 260000 -- 39 % complete
Erasing 128 Kibyte @ 280000 -- 41 % complete
Erasing 128 Kibyte @ 2a0000 -- 43 % complete
Erasing 128 Kibyte @ 2c0000 -- 45 % complete
Erasing 128 Kibyte @ 2e0000 -- 47 % complete
Erasing 128 Kibyte @ 300000 -- 50 % complete
Erasing 128 Kibyte @ 320000 -- 52 % complete
Erasing 128 Kibyte @ 340000 -- 54 % complete
Erasing 128 Kibyte @ 360000 -- 56 % complete
Erasing 128 Kibyte @ 380000 -- 58 % complete
Erasing 128 Kibyte @ 3a0000 -- 60 % complete
Erasing 128 Kibyte @ 3c0000 -- 62 % complete
Erasing 128 Kibyte @ 3e0000 -- 64 % complete
Erasing 128 Kibyte @ 400000 -- 66 % complete
Erasing 128 Kibyte @ 420000 -- 68 % complete
Erasing 128 Kibyte @ 440000 -- 70 % complete
Erasing 128 Kibyte @ 460000 -- 72 % complete
Erasing 128 Kibyte @ 480000 -- 75 % complete
Erasing 128 Kibyte @ 4a0000 -- 77 % complete
Erasing 128 Kibyte @ 4c0000 -- 79 % complete
Erasing 128 Kibyte @ 4e0000 -- 81 % complete
Erasing 128 Kibyte @ 500000 -- 83 % complete
Erasing 128 Kibyte @ 520000 -- 85 % complete
Erasing 128 Kibyte @ 540000 -- 87 % complete
Erasing 128 Kibyte @ 560000 -- 89 % complete
Erasing 128 Kibyte @ 580000 -- 91 % complete
Erasing 128 Kibyte @ 5a0000 -- 93 % complete
Erasing 128 Kibyte @ 5c0000 -- 95 % complete
Erasing 128 Kibyte @ 5e0000 -- 97 % complete
Erasing 128 Kibyte @ 5e0000 -- 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
Writing data to block 16 at offset 0x200000
++is 3.0 parition  version

U-Boot SPL 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


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

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

set_default_env::7864
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot
(Re)start USB...
USB0:   scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Download Linux from USB to Nandflash...
reading ro_uImage
** Unable to read file ro_uImage **
reading rootfs.img
** Unable to read file rootfs.img **
reading datafs.img
** Unable to read file datafs.img **
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:    2157776 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 520, tty '': '/etc/init.d/rcS'
rS in
/etc/init.d/rcS: line 15: setterm: not found

starting pid 537, 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:need upgrade
check_and_upgrade: upgrade start ...
upgrade /usr/bin/siglent/usr/usr/upgrade/MLO
upgrade /usr/bin/siglent/usr/usr/upgrade/u-boot.img

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 0 -- 100 % complete
Writing data to block 0 at offset 0x0

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 --  6 % complete
Erasing 128 Kibyte @ 40000 -- 13 % complete
Erasing 128 Kibyte @ 60000 -- 20 % complete
Erasing 128 Kibyte @ 80000 -- 26 % complete
Erasing 128 Kibyte @ a0000 -- 33 % complete
Erasing 128 Kibyte @ c0000 -- 40 % complete
Erasing 128 Kibyte @ e0000 -- 46 % complete
Erasing 128 Kibyte @ 100000 -- 53 % complete
Erasing 128 Kibyte @ 120000 -- 60 % complete
Erasing 128 Kibyte @ 140000 -- 66 % complete
Erasing 128 Kibyte @ 160000 -- 73 % complete
Erasing 128 Kibyte @ 180000 -- 80 % complete
Erasing 128 Kibyte @ 1a0000 -- 86 % complete
Erasing 128 Kibyte @ 1c0000 -- 93 % complete
Erasing 128 Kibyte @ 1c0000 -- 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
upgrade /usr/bin/siglent/usr/usr/upgrade/ro_uImage

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 --  2 % complete
Erasing 128 Kibyte @ 40000 --  4 % complete
Erasing 128 Kibyte @ 60000 --  6 % complete
Erasing 128 Kibyte @ 80000 --  8 % complete
Erasing 128 Kibyte @ a0000 -- 10 % complete
Erasing 128 Kibyte @ c0000 -- 12 % complete
Erasing 128 Kibyte @ e0000 -- 14 % complete
Erasing 128 Kibyte @ 100000 -- 16 % complete
Erasing 128 Kibyte @ 120000 -- 18 % complete
Erasing 128 Kibyte @ 140000 -- 20 % complete
Erasing 128 Kibyte @ 160000 -- 22 % complete
Erasing 128 Kibyte @ 180000 -- 25 % complete
Erasing 128 Kibyte @ 1a0000 -- 27 % complete
Erasing 128 Kibyte @ 1c0000 -- 29 % complete
Erasing 128 Kibyte @ 1e0000 -- 31 % complete
Erasing 128 Kibyte @ 200000 -- 33 % complete
Erasing 128 Kibyte @ 220000 -- 35 % complete
Erasing 128 Kibyte @ 240000 -- 37 % complete
Erasing 128 Kibyte @ 260000 -- 39 % complete
Erasing 128 Kibyte @ 280000 -- 41 % complete
Erasing 128 Kibyte @ 2a0000 -- 43 % complete
Erasing 128 Kibyte @ 2c0000 -- 45 % complete
Erasing 128 Kibyte @ 2e0000 -- 47 % complete
Erasing 128 Kibyte @ 300000 -- 50 % complete
Erasing 128 Kibyte @ 320000 -- 52 % complete
Erasing 128 Kibyte @ 340000 -- 54 % complete
Erasing 128 Kibyte @ 360000 -- 56 % complete
Erasing 128 Kibyte @ 380000 -- 58 % complete
Erasing 128 Kibyte @ 3a0000 -- 60 % complete
Erasing 128 Kibyte @ 3c0000 -- 62 % complete
Erasing 128 Kibyte @ 3e0000 -- 64 % complete
Erasing 128 Kibyte @ 400000 -- 66 % complete
Erasing 128 Kibyte @ 420000 -- 68 % complete
Erasing 128 Kibyte @ 440000 -- 70 % complete
Erasing 128 Kibyte @ 460000 -- 72 % complete
Erasing 128 Kibyte @ 480000 -- 75 % complete
Erasing 128 Kibyte @ 4a0000 -- 77 % complete
Erasing 128 Kibyte @ 4c0000 -- 79 % complete
Erasing 128 Kibyte @ 4e0000 -- 81 % complete
Erasing 128 Kibyte @ 500000 -- 83 % complete
Erasing 128 Kibyte @ 520000 -- 85 % complete
Erasing 128 Kibyte @ 540000 -- 87 % complete
Erasing 128 Kibyte @ 560000 -- 89 % complete
Erasing 128 Kibyte @ 580000 -- 91 % complete
Erasing 128 Kibyte @ 5a0000 -- 93 % complete
Erasing 128 Kibyte @ 5c0000 -- 95 % complete
Erasing 128 Kibyte @ 5e0000 -- 97 % complete
Erasing 128 Kibyte @ 5e0000 -- 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
Writing data to block 16 at offset 0x200000
upgrade_app:starting
upgrade_app:ending
is_no_firmdata0_partition:partion 3.0
check_and_upgrade: upgrade end... rebooting

U-Boot SPL 2013.01.01-svn29730 (Mar 27 2017 - 19:02:34)
config ddr_pll_config()++
config ddr_pll_config()--
nand_init+++++
nand_init-----
Lcd_Init()++
SetUpLCD()++
SetUpLCD()--
len=768052, height=480, width=800
Logo from nandflash: base=0x81000000; end=0x810bb81f; end-base=0xbb81f; rwsize=0xbb820; r=0x0
Lcd_Init()--


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

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

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

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 @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 -- 50 % complete
Erasing 128 Kibyte @ 20000 -- 100 % complete
The Help file load OK!!

I0101 00:00:10.685917   534 module.cpp:568] ---------------------------------------------------------------------------------------
I0101 00:00:10.711039   534 module.cpp:569]                     Creat Log
-----------------------------------------------------------------------------------------------------------------------------------
 
I0101 00:00:10.742288   534 module.cpp:464] rm -f /usr/bin/siglent/usr/log/Info_19700101-000010.534
I0101 00:00:10.832217   534 module.cpp:464] rm -f /usr/bin/siglent/usr/log/Warning_19700101-000013.534
I0101 00:00:11.008834   534 module.cpp:489]
-----------------------------------------------------------------------------------------------------------------------------------
 
vxi11_main = 11130
init_lcd_driver()++
g_vinfo.xres = 800
g_vinfo.yres = 480
g_vinfo.bits_per_pixel = 16
I0101 00:00:12.443692   655 dev_interpreter.cpp:220] Udisk = U-disk0  not found notes
Could not create log file: File exists
COULD NOT CREATE LOGFILE '19700101-000012.534'!
E0101 00:00:12.445013   655 dev_interpreter.cpp:395] the u-disk sum = -1 is error
E0101 00:00:12.467742   655 dev_interpreter.cpp:406] the device = /usr/bin/siglent/usr/media/U-disk0 umount fail
E0101 00:00:12.472785   655 dev_interpreter.cpp:421] not erase the udisk = U-disk0
I0101 00:00:13.544532   655 dev_interpreter.cpp:338]
        №ТФШUЕМ /usr/bin/siglent/usr/media/U-disk0    device = /dev/sda1
 
E0101 00:00:13.599209   655 dev_interpreter.cpp:332] the device = /dev/sda mount fail

Erasing 128 Kibyte @ 0 --  0 % complete
Erasing 128 Kibyte @ 20000 -- 50 % complete
Erasing 128 Kibyte @ 20000 -- 100 % complete
Writing data to block 0 at offset 0x0

i am don't know how hide long code,sorry

it is after  i try update, iwant to copy log but i off it in momrnt :( and my osciloscope is u-boot mode permanently

please help me to fix my mistake
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 28885
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: Siglent .ads firmware file format
« Reply #402 on: October 14, 2020, 08:10:59 pm »
Hi friend, i have bad osciloscome,
and my osciloscope is u-boot mode permanently

please help me to fix my mistake
Welcome to the forum.

I have SDS1000CML+ recovery files.
By PM please send me your email and we'll see what we can do to fix it.  :)
Avid Rabid Hobbyist.
Siglent Youtube channel: https://www.youtube.com/@SiglentVideo/videos
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #403 on: October 16, 2020, 12:13:49 pm »
Here (without app).
 
The following users thanked this post: voronin_10

Offline voronin_10

  • Newbie
  • Posts: 2
  • Country: ua
  • wise man
    • my instagram
Re: Siglent .ads firmware file format
« Reply #404 on: October 16, 2020, 04:26:56 pm »
tv84 Thank you, ( P21R2.zip ) this file is very important,
tautech Thank you, your file is best, but send this file to this forum, many people seach it

i recover my siglent sds1102cml+ with  cuted MLO file and original u-boot.img

 :-BROKE :-/O   :-DMM :box:
if you device send CC CC CC and uBoot (U-BOOT) dead, this istruction for you

step 1) donload teratermpro23 (version 2.3)
step 2) connect com to device and run and setup 115200, your device send CC CC  word to terminal,
step 3) cut in winhex  original MLO file  start buto  to  this code  140000EA14F09FE5, and save, your cuted file will start at  140000EA14F09FE5
step 4) terra term File -> Transfer -> XMODEM -> Send  open  cuted MLO  file? program send this file to device
step 5) File -> Transfer -> XMODEM -> Send  open u-boot.img, program send this file to device,

after on console you see word UBOOT#
after,  recover your device of standarts method

this message of about CC CC and recover
http://www.mantrid.ru/forum/showthread.php?t=1657

good luck friends

by Peter Skip
 
The following users thanked this post: skander36

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #405 on: October 07, 2021, 04:28:53 pm »
How to open a telnet session in a Siglent when the root password is unknown?

Use the following scripts, according to each equipment.

They provide a root session via port 10101.


Guys, does anyone have a telnet script for SDS5000x series DSO ?

Many Thanks !!!

luudee

 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #406 on: October 08, 2021, 04:25:35 pm »
Guys, does anyone have a telnet script for SDS5000x series DSO ?

The best way is to use the SDS2000X+ method here.
 
The following users thanked this post: luudee

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #407 on: October 09, 2021, 09:40:16 am »
Guys, does anyone have a telnet script for SDS5000x series DSO ?

The best way is to use the SDS2000X+ method here.

Thank you so much, that worked (even with static IP, no need for DHCP).

BUT, I can't find the password. I've been trying for an hour and nothing so far.
Tried all kind os combinations of siglent_sds5000x ...

Any suggestions?

Many Thanks!
luudee
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #408 on: October 09, 2021, 10:34:29 am »
BUT, I can't find the password. I've been trying for an hour and nothing so far.

User name:   'root'
Password: 'siglent_sds1000x_e'


is for shadow contents (used, at least, in SDS1000X-E and SDS2000X+):

root:$6$DZO.HiUy$JKaJGKC8ynyAn.7IF64GzC6cGnmJCQgGlqoPQ9QTc7EW8iF/8lMD00EtiiS3/GpgzN7rvfTbmfnAKzAg66dnu/

From what you're saying SDS5000X uses another password.

You need to copy the shadow file from SDS5000X so that we can verify that. Use the attached file and then attach the file here.
 
The following users thanked this post: luudee

Offline blurpy

  • Regular Contributor
  • *
  • Posts: 233
  • Country: no
Re: Siglent .ads firmware file format
« Reply #409 on: October 09, 2021, 11:01:21 am »
It's interesting to find out the password, but as a start you could possibly just skip it as well.

Code: [Select]
/usr/sbin/telnetd -l /bin/sh
 
The following users thanked this post: tv84, luudee

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #410 on: October 09, 2021, 11:15:50 am »
It's interesting to find out the password, but as a start you could possibly just skip it as well.

Code: [Select]
/usr/sbin/telnetd -l /bin/sh

I'm getting old...  :palm:  Nonetheless, the shadow file would be interesting.
 
The following users thanked this post: luudee

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #411 on: October 09, 2021, 12:34:30 pm »

Thanks so much, guys, very much appreciated !!!

I can now telnet in to my sds5000, with the latest firmware installed.

This is the shadow password file:
root:$6$qWDH15y1$JmmNaT8CddB4GCKIRtcel4fv5TavNr1CFZcYC2iLD6OaoVsDXIbV76S2JEmSBJ54kYrAreEBjWTJL8XIKUuu70:0:0:99999:7:::

Cheers,
rudi
 
The following users thanked this post: blurpy

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #412 on: October 09, 2021, 01:50:28 pm »

ohh crap, they changed the way licensing works :(

Last time I did, I had just modify one file (NSP_system_info.xml)  and add the license key to it.
Now, they use two files for each option:
---x------    1 root     0               20 Jun  5  2020 options_pa_cfg.bin
---x------    1 root     0               20 Jun  5  2020 options_pa_license.txt

The text file seems to have a license key, which does not match what I am generating with the python script anymore.
And the binary file has 20 bytes, of which the first 16 are identical between all option*.bin file, only the last 6 bytes differ ...

Any clues how to generate these ?

Many Thanks,
luudee



 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #413 on: October 09, 2021, 02:05:02 pm »
It's the same scheme. You must be making mistake. Switch to SDS5000X thread.
 
The following users thanked this post: luudee

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #414 on: October 09, 2021, 03:13:44 pm »

Thanks guys, I figured it out ... was using a old python script, after looking thought the changes, I figured it out.

Please let me know if I can be of any help to you guy !


Cheers,
rudi
 

Offline luudee

  • Frequent Contributor
  • **
  • Posts: 281
  • Country: th
Re: Siglent .ads firmware file format
« Reply #415 on: October 09, 2021, 03:20:59 pm »

I found a permanent way to enable telnet, not sure if it will be removed by a
firmware update, but this works without a flash drive once installed:

1. mount -o remount,rw,sync /usr/bin/siglent
2. cd /usr/bin/siglent/etc/init.d
3. vi rcLocal
4. Add at the end of rcLocal: /usr/sbin/telnetd -l /bin/sh


btw, the main application on my SDS500X, is /usr/bin/siglent/sds2000hsr


Cheers,
rudi
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #416 on: September 26, 2022, 09:17:50 pm »
SUCCESS!!!!!!!!     I know, I know, it was just a meaningless personal quest but you can't imagine the time I've spent on this...  :palm:  :-DD

Ever since the HostID and ScopeIP came into existence (in Siglent's HW) that I've been trying to discover where that info is stored and, most importantly, how it is determined and how the initial byte that always looked like a CRC/checksum was calculated. Even some forum members have participated in my endless quest...

Today is the day when that mystery came to an end!!!!!!!!  :popcorn:

After several years looking at lots of IDs, today I was once again lead on a "random mistake" and googled the attached document. Once I read "The DS2401 consists of a 64-bit ROM that includes a unique 48-bit serial number, an 8-bit CRC, and an 8-bit Family Code (01h). Data is transferred serially via the 1-Wire protocol that requires only a single data lead and a ground return. ", I knew I had found what Siglent is using.

Now I just had to discover what was the CRC-8 implementation and confirm the results... It took a few minutes: CRC-8/MAXIM   :popcorn:

This IC scheme is an unbelievable simple thing that I had never heard of... Had eluded me for years because I was always focused on the other HW parts of the devices!   :palm:

So, if we take a Siglent "fictitious" ScopeID like "2F000089ABCDEF01", its CRC-8 is calculated like this:

CRC-8[01EFCDAB890000] => 2F

That confirms that Siglent seems to use the 64-bits chip ID byte-reversed. The CRC-8 is calculated with the bytes order reversed.

Time to celebrate!!  :popcorn: :popcorn:
« Last Edit: September 28, 2022, 09:03:04 am by tv84 »
 
The following users thanked this post: KeBeNe, egonotto, Orange, Emo, james38, tubularnut, kerouanton, Martin72, zrq, blurpy, umgfoin

Offline Orange

  • Frequent Contributor
  • **
  • Posts: 348
  • Country: nl
Re: Siglent .ads firmware file format
« Reply #417 on: September 27, 2022, 05:43:33 pm »
SUCCESS!!!!!!!!     I know, I know, it was just a meaningless personal quest but you can't imagine the time I've spent on this...  :palm:  :-DD

Ever since the HostID and ScopeIP came into existence (in Siglent's HW) that I've been trying to discover where that info is stored and, most importantly, how it is determined and how the initial byte that always looked like a CRC/checksum was calculated. Even some forum members have participated in my endless quest...

Today is the day when that mystery came to an end!!!!!!!!  :popcorn:

After several years looking at lots of IDs, today I was once again lead on a "random mistake" and googled the attached document. Once I read "The DS2401 consists of a 64-bit ROM that includes a unique 48-bit serial number, an 8-bit CRC, and an 8-bit Family Code (01h). Data is transferred serially via the 1-Wire protocol that requires only a single data lead and a ground return. ", I knew I had found what Siglent is using.

Now I just had to discover what was the CRC-8 implementation and confirm the results... It took a few minutes: CRC-8/MAXIM   :popcorn:

This IC scheme is an unbelievable simple thing that I had never heard of... Had eluded me for years because I was always focused on the other HW parts of the devices!   :palm:

So, if we take a Siglent "fictitious" ScopeID like "2F000089ABCDEF01", its CRC-8 is calculated like this:

CRC-8[01EFCDAB890000] => 2F

That confirms that Siglent seems to use the 64-bits chip ID byte-reversed.

Time to celebrate!!  :popcorn: :popcorn:
Do you think that Siglent internally keeps an mapping table where the SopeID is linked to the Serial number of the instrument so that license generation can be done ?

Do they use Blackfin IDs for their older devices ?
 
The following users thanked this post: czorgormez

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #418 on: September 27, 2022, 08:51:41 pm »
Do you think that Siglent internally keeps an mapping table where the SopeID is linked to the Serial number of the instrument so that license generation can be done ?

Do they use Blackfin IDs for their older devices ?

1. Yes.

2. No. In the old SDS2000X/SDS1000X they use the same (or very similar) ID chips but only consider the inner 6 bytes. The family ID and CRC8 are discarded for the ScopeID construction.
 
The following users thanked this post: Orange

Offline Mick B

  • Regular Contributor
  • *
  • Posts: 109
  • Country: us
Re: Siglent .ads firmware file format
« Reply #419 on: March 16, 2023, 07:26:36 pm »
Is the  telnet_SSA3032X_Plus.zip (224.02 kB) OK to use on the SSA3032X
Thanks just making sure
 

Offline tv84

  • Super Contributor
  • ***
  • Posts: 3260
  • Country: pt
Re: Siglent .ads firmware file format
« Reply #420 on: November 03, 2023, 07:47:32 pm »
Here is the file to get telnet access to the SDG6000X-E (China model).

Product_ID = 10900
 
The following users thanked this post: boolhead

Offline boolhead

  • Newbie
  • Posts: 2
  • Country: cn
Re: Siglent .ads firmware file format
« Reply #421 on: November 06, 2023, 03:05:55 am »
 :-+ :-+ :-+, Hi tv84, it works for the modle SDG6012X-E :clap:, by following the steps from this tip:

I'm clearly no expert.
would it be possible to get a step by step procedure to unlock this device ?

Attached are my notes I made of the process.
 

Offline rloc

  • Newbie
  • Posts: 4
  • Country: ru
Re: Siglent .ads firmware file format
« Reply #422 on: April 06, 2024, 10:05:15 am »
Hi all!

Who knows how to unpack the *.ads firmware of Siglent SDS800X-HD based on the Zynq US+ platform?

https://siglentna.com/service-and-support/firmware-software/digital-oscilloscopes/#sds800x-hd-series
 

Offline coromonadalix

  • Super Contributor
  • ***
  • Posts: 6204
  • Country: ca
Re: Siglent .ads firmware file format
« Reply #423 on: May 23, 2024, 12:31:45 pm »
HI @ll

As anyone worked on the SSG 3000x series,  i bought a new one,  but  sadly i cant recall how i BW upgraded it,   and the 1st one  did go smootlhy,  maybe too much, cant recall how i did it  |O

is there a way to find  the bw infos thru telnet ?   i can see its webpage ...

or poke in the ADS FW upgrade file ?    i/m not strong on these  TELNET thing

thks


EDIT    worked and tested with a scope script,  see the relevant ssg3000x  thread,   i posted it there, enter manually with the touchscreen
« Last Edit: May 24, 2024, 05:09:26 pm by coromonadalix »
 

Offline james38

  • Regular Contributor
  • *
  • Posts: 100
  • Country: de
Re: Siglent .ads firmware file format
« Reply #424 on: May 23, 2024, 02:48:43 pm »
The optionkey for bw upgrade is : 21BW31
I think the upgrade is only possible via scpi
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf