Author Topic: Unlocking Siglent SDS1104X-E, step by step  (Read 86478 times)

0 Members and 2 Guests are viewing this topic.

Offline sdt

  • Contributor
  • Posts: 7
  • Country: au
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #175 on: September 04, 2019, 10:14:46 pm »
wanted to know if it would be possible to reverse-downgrade (for whatever reason) the process to 100M key?

It is. Run the MCBD command again with your 100M key and it's back to 100Mhz.

Also after updating does indeed the model name change?

It does. There's screenshots in this thread showing the status page with the updated model code.
 
The following users thanked this post: ssaenek

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #176 on: September 24, 2019, 11:52:51 am »
hi guys,
I've read all posts from this topic and I'm impressed.
It seems that all is done regarding this oscilloscope but I have other problem fitting well to this topic. I hope will be interesting for you.

Some time ago I've been in China (8 months in totall of living and working in Shenzhen city). Just before returning to Europe I bought oscilloscope from taobao (chinese ebay). I haven't known about hacking possibility in this time, by the way. I've choosen it because of parameters vs price ratio. Price was 3,1k CNY (~430 USD - current rate). So, cheaper then in Europe but not much. On Chinese market this oscilloscope has little bit different name: SDS1104X-C. I noticed it  but didn't expect that only different between ...X-C nad ...X-E are Chinese language in menu that can't be change to any other:)
I wrote a message to Siglent China with question how to change the language to English but they rid me off and suggested to return device back (it was too late for me because of next day flight). Also Siglent Europe(Netherlands) didn't help me (they even didn't know about ...X-C model exist:)). Only thing I've known from Siglent was that only this model (4ch) SDS1104X has unchangable Chinese language on domestic market. On any other Siglent product you can change language to English:)

Hardware seems to be the same like ...X-E. On the motherboard is a label with SDS1000X-E text. Reading of .ads files works and I can changes firmware. But Operation System updating is disable. I think there is no bootloader in flash. It would be too easy to change from ...X-C to ...X-E I guess.

Information in this topic helped me to (almost) fix this problem. My idea was to locate language files and simply exchange chinese and englishc file names. I did it by following steps:

1. change firmware version to 6.1.25R2 (by loading .ads file)
2. change ip on oscilloscope to 192.168.1.57
3. switche to root by:

telnet 192.168.1.57 5024
SHELLCMD telnetd -l/bin/sh -p9999
---------------------------------------------------------
telnet 192.168.1.57 9999

4. remounte partition to rw by:

mount -o remount,rw ubi2_0 /usr/bin/siglent

5. all languages files are in .xml format and are located in:

/usr/bin/siglent/config/ui_data/

chinese simplified version:

simp_help_info.xml
simp_menu_info.xml
simp_text_info.xml

chinese traditional version:

trad_help_info.xml
trad_menu_info.xml
trad_text_info.xml

english version:

english_help_info.xml
english_menu_info.xml
english_text_info.xml

I copied all above files to USB drive:

/usr/bin/siglent/usr/mass_storage/U-disk0/

then changed names of english... files (under windows) to simp... and trad... and coppied back rom USB to:

/usr/bin/siglent/config/ui_data/

After reboot I seen all menu names in english:)
I was happy but it was working on old firmware 6.1.25R2 so I changed firmware to newest 6.1.33 but with this change language changed back to chinese (logical, because new functions requaier new menu files). Unfortunetly, rooting method, mentioned above isn't work on this firmware version, so I couldn't change language files.

I returned to 6.1.25R2 and repeated procedure but I did HORRIBLE mistake this time: during exchanging files I removed them first from ui_data and then copy form USB but I didn't check the files was in ui_data folder after operation. Probably I did some typo and files didn't copy. After reboot the device has hange up on Siglent logo and can't go next.
I can ping it but SHELLCMD (telnet 192.168.1.57 5024) doesn't work:(
so I lost root access. Only I can do is:

 telnet 192.168.1.57 23

but I don't know root password off course.
This is my story:)


but it isn't end of the world and I have new idea how to resurrect my device by restore dumped memory. I see 2 possibilities:

1. I localized flash memory on the motherboard. It is one chip: 29F2G08ABAEA WP. This is 2Gb nand flash with 8 bit organization. Unfortunetly, this is parallel programming memory so need to be take off from board to programm it directly. Of corse there is special programmer and adapter needed(I can get it).

2. On the motherboard we can find JTAG connector. Main processor is Xilinx Zynq so using Xilinx SDK(https://www.xilinx.com/html_docs/xilinx2019_1/SDK_Doc/SDK_tasks/sdk_t_memory_dump_restore.html) and Digilent JTAG-HS3(https://store.digilentinc.com/jtag-hs3-programming-cable/) or JTAG-HS2 USB flashing memory throught Jtag should be possible. Another problem could be to confirme that this is for sure JTAG connector and what is the pinout.

I'm wondering could I flash dumped memory from another oscilloscope (...X-E version with different serial number).
I did dump mem from my scope but if I flash it back there will be the same problem with language and bootloader.

I would be grateful if somebody could share with me dumped memory from SDS1104X-E scope (best for me would be OSV1_EN_eevblog with known root password).

What do you think about my idea to fix it and flashing method I'm mentioning? I would be happy for any suggestions or corrections.
 
The following users thanked this post: ssaenek

Offline Gege34

  • Contributor
  • Posts: 22
  • Country: fr
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #177 on: September 24, 2019, 12:24:13 pm »
On this thread tv84 (and plurn) give a way to activate telnet on firmware 6.1.33
 
The following users thanked this post: ssaenek

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #178 on: September 24, 2019, 12:49:15 pm »
Thanks for this info. I'll try it on hanging scope first.
 

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #179 on: September 24, 2019, 02:28:32 pm »
Thanks for this info. I'll try it on hanging scope first.

First, get control of your machine once again. After that, worry about changing language.

To solve the language problem you should change the scope model from X-C to X-E. Don't go around patching the filesystem.

Maybe you can do it with a simple SCPI command.

PS: If you have any memdump of your machine I would be interested in having a look.
« Last Edit: September 24, 2019, 02:31:48 pm by tv84 »
 

Offline rf-loop

  • Super Contributor
  • ***
  • Posts: 3607
  • Country: cn
  • Born in Finland with DLL21 in hand
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #180 on: September 24, 2019, 04:17:20 pm »
Thanks for this info. I'll try it on hanging scope first.

First, get control of your machine once again. After that, worry about changing language.

To solve the language problem you should change the scope model from X-C to X-E. Don't go around patching the filesystem.

Maybe you can do it with a simple SCPI command.

PS: If you have any memdump of your machine I would be interested in having a look.

Jus very tiny sidenote for yours this: "Also Siglent Europe(Netherlands) didn't help me (they even didn't know about ...X-C model exist:))."

Siglent Europe(Netherlands) is not Siglent at all. It is one Siglent distributor. (also sell many other equipments but using different domain)

If you need Siglent (manufacturer) help in Europe: Right place is Siglent Technologies Germany GmbH
Web side: https://www.siglenteu.com/

Problem is also factory warranty in EU area. You have model localized for China domestic markets what have warranty only there and its serial number is not in EU area database.

But...    no one can deny when the owner makes "some" changes and modifications at his own risk. ;)
If practice and theory is not equal it tells that used application of theory is wrong or the theory itself is wrong.
-
Huawei HarmonyOS 2.0  |  ArcFox Alpha S
 
The following users thanked this post: ssaenek

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #181 on: September 25, 2019, 08:46:09 am »
tv84,
regarding getting control once again, do you think that two ways I mentioned above are only possible or maybe you have another idea how to do this easier?
I sent you memdump to PW.

rf-loop,
you've right. I don't remember how I reached to this contact. I could swear that from siglent.com link but as I'm checking now there is link to Siglent Hamburg.
Regarding warranty, yes I was full aware of it. I expected something like "to solve your problem we need to reflash device. Cost of this operation is ...." I didn't expect any free warranty actions.
But it doesn't metter now because I've gone to hardware mafia already:)
 

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #182 on: September 25, 2019, 09:36:03 am »
I don't remember if you can force an FW upgrade while the scope is booting (supported by the bootloader).

Maybe tautech can help in that regard.

Do you have access to serial port? What does that log show?
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #183 on: September 25, 2019, 10:16:36 am »
I'll try to read log in the evening. Will let you know.
« Last Edit: September 25, 2019, 01:06:06 pm by ucognitive »
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #184 on: September 25, 2019, 06:40:46 pm »
serial transmition work with baudrate 115200kbps. It seems that I can write commands also.

here are
Code: [Select]
df command response:

Code: [Select]
df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                29868     29868         0 100% /
devtmpfs                110060         0    110060   0% /dev
none                    118348         0    118348   0% /tmp
ubi1_0                   29816     14388     15428  48% /usr/bin/siglent
ubi2_0                    5848        72      5776   1% /usr/bin/siglent/firmdata0
ubi0_0                   84752       280     84472   0% /usr/bin/siglent/usr
/dev/sda1             15711208     31136  15680072   0% /usr/bin/siglent/usr/mass_storage/U-disk0
/ #




here are the logs:

1.Booting of scope

Code: [Select]
Start menu vdma ...
Config AXI VDMA...
Start menu vdma done.


U-Boot 2014.07-svn32760 (Mar 23 2018 - 01:35:12)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 243 MiB
NAND:  256 MiB
MMC:   zynq_sdhci: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
int board_late_init(void)+++++
[INFO]int fb_display_logo(void)++++++++++++
[INFO]pStorageMem=0xfa00000, logo_data=0x200036, width=800, height=480
 [INFO]int fb_display_logo(void)----------
int board_late_init(void)-----
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1:   ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
       scanning usb for storage devices... 0 Storage Device(s) found
Copying Linux from USB to RAM...
** Bad device usb 0 **
** Bad device usb 0 **
Copying Linux from NAND flash to RAM...

NAND read: device 0 offset 0x780000, size 0x400000
 4194304 bytes read: OK

NAND read: device 0 offset 0xb80000, size 0x80000
 524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-3.19.0-xilinx-svn8988
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3614680 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
   Loading Kernel Image ... OK
   Loading Device Tree to 0e00d000, end 0e013e8b ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.19.0-xilinx-svn8988 (david@david-virtual-machine) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #187 SMP PREEMPT Wed Feb 28 18:55:09 CST 2018
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Zynq Zed Development Board
[    0.000000] cma: Reserved 16 MiB at 0x0d000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 9 pages/cpu @4edf2000 s8128 r8192 d20544 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
[    0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=08
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 220120K/245760K available (4514K kernel code, 229K rwdata, 1748K rodata, 192K init, 223K bss, 9256K reserved, 16384K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0x4f800000 - 0xff000000   (2808 MB)
[    0.000000]     lowmem  : 0x40000000 - 0x4f000000   ( 240 MB)
[    0.000000]     pkmap   : 0x3fe00000 - 0x40000000   (   2 MB)
[    0.000000]     modules : 0x3f000000 - 0x3fe00000   (  14 MB)
[    0.000000]       .text : 0x40008000 - 0x40625c7c   (6264 kB)
[    0.000000]       .init : 0x40626000 - 0x40656000   ( 192 kB)
[    0.000000]       .data : 0x40656000 - 0x4068f620   ( 230 kB)
[    0.000000]        .bss : 0x4068f620 - 0x406c74c4   ( 224 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[    0.000000] slcr mapped to 4f804000
[    0.000000] zynq_clock_init: clkc starts at 4f804100
[    0.000000] Zynq clock init
[    0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000137] timer #0 at 4f806000, irq=17
[    0.000507] Console: colour dummy device 80x30
[    0.000528] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090280] pid_max: default: 32768 minimum: 301
[    0.090439] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090454] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091117] CPU: Testing write buffer coherency: ok
[    0.091334] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.091420] Setting up static identity map for 0x441b50 - 0x441ba8
[    0.240268] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.240353] Brought up 2 CPUs
[    0.240373] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[    0.240382] CPU: All CPU(s) started in SVC mode.
[    0.240922] devtmpfs: initialized
[    0.241765] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.247861] NET: Registered protocol family 16
[    0.250053] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.281232] cpuidle: using governor ladder
[    0.311198] cpuidle: using governor menu
[    0.319920] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.319937] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.320085] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4f880000
[    0.338397] vgaarb: loaded
[    0.338845] SCSI subsystem initialized
[    0.339258] usbcore: registered new interface driver usbfs
[    0.339354] usbcore: registered new interface driver hub
[    0.339533] usbcore: registered new device driver usb
[    0.339696] phy0 supply vcc not found, using dummy regulator
[    0.339788] phy1 supply vcc not found, using dummy regulator
[    0.339918] --------------usb_udc_init ------
[    0.340147] pps_core: LinuxPPS API ver. 1 registered
[    0.340160] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.340211] PTP clock support registered
[    0.340340] EDAC MC: Ver: 3.0.0
[    0.342110] cfg80211: Calling CRDA to update world regulatory domain
[    0.342491] Switched to clocksource arm_global_timer
[    0.355818] NET: Registered protocol family 2
[    0.356660] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.356711] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.356769] TCP: Hash tables configured (established 2048 bind 2048)
[    0.356821] TCP: reno registered
[    0.356837] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.356871] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.357079] NET: Registered protocol family 1
[    0.357408] RPC: Registered named UNIX socket transport module.
[    0.357421] RPC: Registered udp transport module.
[    0.357430] RPC: Registered tcp transport module.
[    0.357439] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.357873] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.359295] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.360980] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.362084] io scheduler noop registered
[    0.362106] io scheduler deadline registered
[    0.362157] io scheduler cfq registered (default)
[    0.364345] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.364368] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.364875] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[    0.943761] console [ttyPS0] enabled
[    0.947945] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4f878000
[    0.954721] [drm] Initialized drm 1.1.0 20060810
[    0.967430] brd: module loaded
[    0.974577] loop: module loaded
[    0.985927] libphy: MACB_mii_bus: probed
[    1.062680] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 150 (00:0a:35:00:01:22)
[    1.072565] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.083970] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.090420] ehci-pci: EHCI PCI platform driver
[    1.095032] usbcore: registered new interface driver usbtmc
[    1.100611] usbcore: registered new interface driver usb-storage
[    1.106791] e0002000.usb supply vbus not found, using dummy regulator
[    1.113516] ci_hdrc ci_hdrc.0: EHCI Host Controller
[    1.118334] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[    1.142513] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[    1.148689] hub 1-0:1.0: USB hub found
[    1.152388] hub 1-0:1.0: 1 port detected
[    1.156845] e0003000.usb supply vbus not found, using dummy regulator
[    1.165041] i2c /dev entries driver
[    1.169306] cdns-i2c e0005000.i2c: 20 kHz mmio e0005000 irq 144
[    1.176565] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.182821] Xilinx Zynq CpuIdle Driver started
[    1.187860] ledtrig-cpu: registered to indicate activity on CPUs
[    1.193949] usbcore: registered new interface driver r8188eu
[    1.200381] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.206679] nand: Micron MT29F2G08ABAEAWP
[    1.210650] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.218244] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.229708] Bad block table found at page 131008, version 0x01
[    1.235969] Bad block table found at page 130944, version 0x01
[    1.242072] 11 ofpart partitions found on MTD device pl353-nand
[    1.247919] Creating 11 MTD partitions on "pl353-nand":
[    1.253229] 0x000000000000-0x000000780000 : "fsbl"
[    1.259101] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.265424] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.271702] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.278368] 0x000001100000-0x000001600000 : "reserved1"
[    1.284559] 0x000001600000-0x000003e00000 : "rootfs"
[    1.290488] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.296687] 0x000004800000-0x000007000000 : "siglent"
[    1.302875] 0x000007000000-0x00000d400000 : "datafs"
[    1.308928] 0x00000d400000-0x00000fc00000 : "upgrade_cramdisk"
[    1.315809] 0x00000fc00000-0x000010000000 : "reserved2"
[    1.324085] TCP: cubic registered
[    1.327329] NET: Registered protocol family 17
[    1.331766] lib80211: common routines for IEEE802.11 drivers
[    1.337774] Registering SWP/SWPB emulation handler
[    1.349485] cramfs_fill_nand blocks is 320-----------------------
[    1.349485]
[    1.349485]
[    1.349485]
[    1.362746] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.369593] devtmpfs: mounted
[    1.372790] Freeing unused kernel memory: 192K (40626000 - 40656000)
[    1.482595] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.633815] hub 1-1:1.0: USB hub found
[    1.637694] hub 1-1:1.0: 3 ports detected
Starting rcS...
 Mounting filesystem
[    1.798962] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.201038] UBI-0: scan_all:scanning is finished
 40
[    2.760356] UBIFS: mounted UBI device 1, volume 0, name "siglent", R/O mode
[    2.767266] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.776374] UBIFS: FS size: 33775616 bytes (32 MiB, 266 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.786001] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.791032] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 52ED3690-D3C2-49A9-9055-7EBFF2762FCB, small LPT model
[    2.867658] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.874396] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.883497] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.892864] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.897890] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C429C489-76D4-469B-8BFE-043289ABBD0F, small LPT model
[    2.911607] UBIFS: background thread "ubifs_bgt0_0" started, PID 675
[    2.943197] UBIFS: recovery needed
 2.760356] UBIFS: mounted UBI device 1, volume 0, name "siglent", R/O mode
[    2.767266] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.776374] UBIFS: FS size: 33775616 bytes (32 MiB, 266 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.786001] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.791032] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 52ED3690-D3C2-49A9-9055-7EBFF2762FCB, small LPT model
[    2.867658] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.874396] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.883497] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.892864] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.897890] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C429C489-76D4-469B-8BFE-043289ABBD0F, small LPT model
[    2.911607] UBIFS: background thread "ubifs_bgt0_0" started, PID 675
[    2.943197] UBIFS: recovery needed
h_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.674601] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 670
, name "siglent", R/O mode
[    2.767266] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.776374] UBIFS: FS size: 33775616 bytes (32 MiB, 266 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.786001] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.791032] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 52ED3690-D3C2-49A9-9055-7EBFF2762FCB, small LPT model
[    2.867658] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.874396] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.883497] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.892864] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.897890] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C429C489-76D4-469B-8BFE-043289ABBD0F, small LPT model
[    3.025920] UBIFS: recovery completed
[    3.029594] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.035545] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.044644] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.054276] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.059305] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C886A817-B838-46DF-AE16-F9920045A7D7, small LPT model
Upgrade start
 Configure eth0
Starting mdev
[    2.911607] UBIFS: background thread "ubifs_bgt0_0" started, PID 675
[    2.943197] UBIFS: recovery needed
h_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.674601] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 670
8 KiB), LEB size: 126976 bytes
[    2.478605] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.487104] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.495793] UBI-1: ubi_attach_mtd_dev:good PEBs: 320, bad PEBs: 0, corrupted PEBs: 0
[    2.503509] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.512435] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 13/9, WL threshold: 4096, image sequence number: 1819264682
[    2.523399] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 320, PEBs reserved for bad PEB handling:[    4.045576] xilinx-dma 40400000.dma: Probing xilinx axi dma engine...Successful
[    4.087569] sigdma_init++++++
[    4.111420] siglentkb probe
[    4.114484] ##### siglentkb registers 4fc1e580 4fc365a4 4fc385b8
[    4.139471] usbcore: registered new interface driver mt7601u
[    4.152355] irq = 170
config read
###### Config vdma for wave transform #######
config write
config read
dump s2mm registers
dump mm2s registers
####### done! ########
Config vnc  data to memory
Config done!
#### siglentkb registers 4fc1e580 4fc365a4 4fc385b8
[    4.139471] usbcore: regis[    4.371815] UBIFS: background thread "ubifs_bgt1_0" started, PID 778
ln: /usr/bin/siglent/config/www/web_img/usr: File exists
Starting Lighttpd Web Server: Initializing framebuffer device /dev/fb0...
xres=800, yres=480, xresv=800, yresv=480, xoffs=0, yoffs=0, bpp=16
Initializing touch device /dev/input/event0 ...
Initializing VNC server:
width:  800
height: 480
bpp:    16
port:   5900
Initializing server...
01/01/1970 00:00:04 Listening for VNC connections on TCP port 5900
[    4.504615] random: lighttpd urandom read with 17 bits of entropy available
lighttpd.
[    4.643624] UBIFS: background thread "ubifs_bgt1_0" stops
rcS Complete

Processing /etc/profile... Done

/ # [INFO]:calibrate_t():line=81:calibrate_t::calibrate_t()
product_type SDS1004X_E
mkdir: can't create directory '/usr/bin/siglent/usr/wifi/': File exists
rm: can't remove '/usr/bin/siglent/usr/wifi/wpa_supplicant': No such file or directory

                                                       $Task start:: SCPI
 
                                                       $Task start:: Devce
 
                                                       $Task start:: WLAN
 
                                                       $Task start:: Udisk&Lan
 vxi11_main = 6821.64

                                                       $Task start:: Vxi11_client
sh: write error: Invalid argument
 drv_instance_manage_t: produce_id: 13501
(DRV_PRODUCT_PIKACHU)
_drv_product=4
acq_scal_user = -1.000000
ready...
ready...
ready...
ready...
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_awg_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_wifi_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_mso_license.txt
[    7.232355] export_store: invalid GPIO 115
sh: write error: Invalid argument
sh: can't create /sys/class/gpio/gpio115/direction: nonexistent directory
sh: can't create /sys/class/gpio/gpio115/value: nonexistent directory
open file %s fail !!!!/usr/bin/siglent/config/arb/2ASK.wav
scpi_register_cmd_boardtest
ready...
cp: can't stat '/usr/bin/siglent/usr/usr/save_setting.xml': No such file or directory
/usr/bin/siglent/usr/usr/save_setting.xml  not exist

                                                       $Task start:: UI
ifconfig: SIOCGIFFLAGS: No such device
 
                                                       $Task start:: awg_thread
 mod_if_exit_handler:signal=11
Clean Up Ready!
Clean Up - nlog
Clean Up - Main Thread
Clean Up - scpi
Clean Up - timer
Clean Up - dev_thread
Clean Up - ui
Clean Up - acq_thread
Clean Up - acq_data
Clean Up - draw_wave
Clean Up - bu_cfg
Clean Up - bu_main
Clean Up - bu_app
Clean Up - key
Clean Up - other
Clean Up - usbtmc
Clean Up - VXI_11
Clean Up - dev_interrupt
Clean Up - wlan_manager
Clean Up - power_off
Clean Up - telnet_scpi
Clean Up - socket_scpi
Clean Up - vxi11_client
Clean Up - Config
Clean Up - sdg_Timer
Clean Up - awg_threa[   10.912150] Free all channel resources.
d
Clean Up - usbtmc_assistant_interrupt
Clean Up Over!
sds100[   10.919150] Free all channel resources.
0b.app: mempool.h:81: MemoryChunk::~MemoryChunk(): Assertion `tempcount==count' failed.


2. Booting of scope with OS stored in external USB drive

Code: [Select]
Start menu vdma ...
Config AXI VDMA...
Start menu vdma done.


U-Boot 2014.07-svn32760 (Mar 23 2018 - 01:35:12)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 243 MiB
NAND:  256 MiB
MMC:   zynq_sdhci: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
int board_late_init(void)+++++
[INFO]int fb_display_logo(void)++++++++++++
[INFO]pStorageMem=0xfa00000, logo_data=0x200036, width=800, height=480
 [INFO]int fb_display_logo(void)----------
int board_late_init(void)-----
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
USB1:   ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
       scanning usb for storage devices... 1 Storage Device(s) found
Copying Linux from USB to RAM...
** Invalid partition 1 **
** Invalid partition 1 **
Copying Linux from NAND flash to RAM...

NAND read: device 0 offset 0x780000, size 0x400000
 4194304 bytes read: OK

NAND read: device 0 offset 0xb80000, size 0x80000
 524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-3.19.0-xilinx-svn8988
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3614680 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
   Loading Kernel Image ... OK
   Loading Device Tree to 0e00d000, end 0e013e8b ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
 enabled
 0.356649] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.356703] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.356761] TCP: Hash tables configured (established 2048 bind 2048)
[    0.356810] TCP: reno registered
[    0.356828] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.356863] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.357070] NET: Registered protocol family 1
[    0.357416] RPC: Registered named UNIX socket transport module.
[    0.357429] RPC: Registered udp transport module.
[    0.357438] RPC: Registered tcp transport module.
[    0.357447] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.357873] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.359290] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.360978] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.362068] io scheduler noop registered
[    0.362090] io scheduler deadline registered
[    0.362140] io scheduler cfq registered (default)
[    0.364310] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.364330] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.364832] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[    0.943655] console [ttyPS0] enabled
[    0.947840] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4f878000
[    0.954616] [drm] Initialized drm 1.1.0 20060810
[    0.967322] brd: module loaded
[    0.974502] loop: module loaded
[    0.985953] libphy: MACB_mii_bus: probed
[    1.062452] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 150 (00:0a:35:00:01:22)
[    1.072328] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.083738] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.356703] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.356761] TCP: Hash tables configured (established 2048 bind 2048)
[    0.356810] TCP: reno registered
[    0.356828] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.356863] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.357070] NET: Registered protocol family 1
[    0.357416] RPC: Registered named UNIX socket transport module.
[    0.357429] RPC: Registered udp transport module.
[    0.357438] RPC: Registered tcp transport module.
[    0.357447] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.357873] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.359290] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.360978] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.362068] io scheduler noop registered
[    0.362090] io scheduler deadline registered
[    0.362140] io scheduler cfq registered (default)
[    0.364310] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.364330] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.364832] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[    0.943655] console [ttyPS0] enabled
[    0.947840] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4f878000
[    0.954616] [drm] Initialized drm 1.1.0 20060810
[    0.967322] brd: module loaded
[    0.974502] loop: module loaded
[    0.985953] libphy: MACB_mii_bus: probed
[    1.062452] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 150 (00:0a:35:00:01:22)
[    1.072328] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.083738] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.090186] ehci-pci: EHCI driver usb
[    0.339429] phy0 supply vcc not found, using dummy regulator
[    0.339536] phy1 supply vcc not found, using dummy regulator
[    0.339670] --------------usb_udc_init ------
[    0.339897] pps_core: LinuxPPS API ver. 1 registered
[    0.339911] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.339967] PTP clock support registered
[    0.340296] EDAC MC: Ver: 3.0.0
[    0.341900] cfg80211: Calling CRDA to update world regulatory domain
[    0.342332] Switched to clocksource arm_global_timer
[    0.355865] NET: Registered protocol family 2
48 (order: 1, 8192 bytes)
[    0.356703] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.356761] TCP: Hash tables configured (established 2048 bind 2048)
[    0.356810] TCP: reno registered
[    0.356828] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.356863] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.357070] NET: Registered protocol family 1
[    0.357416] RPC: Registered named UNIX socket transport module.
[    0.357429] RPC: Registered udp transport module.
[    0.357438] RPC: Registered tcp transport module.
[    0.357447] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.357873] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.359290] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.360978] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.362068] io scheduler noop registered
[    0.362090] io scheduler deadline registered
[    0.362140] io scheduler cfq registered (default)
[    0.364310] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.364330] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.364832] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 6249999) is a xuartps
[    0.943655] console [ttyPS0] enabled
[    0.947840] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4f878000
[    0.954616] [drm] Initialized drm 1.1.0 20060810
[    0.967322] brd: module loaded
[    0.974502] loop: module loaded
[    0.985953] libphy: MACB_mii_bus: probed
[    1.062452] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 150 (00:0a:35:00:01:22)
[    1.072328] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.083738] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.090186] ehci-pci: EHCI driver usb
[    0.339429] phy0 supply vcc not found, using dummy regulator
[    0.339536] phy1 supply vcc not found, using dummy regulator
[    0.339670] --------------usb_udc_init ------
[    0.339897] pps_core: LinuxPPS API ver. 1 registered
[    0.339911] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.339967] PTP clock support registered
[    0.340296] EDAC MC: Ver: 3.0.0
[    0.341900] cfg80211: Calling CRDA to update world regulatory domain
[    0.342332] Switched to clocksource arm_global_timer
[    0.355865] NET: Registered protocol family 2
[   tch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode PCI platform driver
[    1.094784] usbcore: registered new interface driver usbtmc
[    1.100365] usbcore: registered new interface driver usb-storage
[    1.106534] e0002000.usb supply vbus not found, using dummy regulator
[    1.113235] ci_hdrc ci_hdrc.0: EHCI Host Controller
[    1.118047] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[    1.142353] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[    1.148519] hub 1-0:1.0: USB hub found
[    1.152214] hub 1-0:1.0: 1 port detected
[    1.156695] e0003000.usb supply vbus not found, using du2c: 20 kHz mmio e0005000 irq 144
[    1.176481] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.182760] Xilinx Zynq CpuIdle Driver started
[    1.187808] ledtrig-cpu: registered to indicate activity on CPUs
[    1.193902] usbcore: registered new interface driver r8188eu
[    1.200310] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.206606] nand: Micron MT29F2G08ABAEAWP
[    1.210572] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.218145] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.229703] Bad block table found at page 131008, version 0x01
[    1.235974] Bad block table found at page 130944, version 0x01
[    1.242082] 11 ofpart partitions found on MTD device pl353-nand
[    1.247931] Creating 11 MTD partitions on "pl353-nand":
[    1.253145] 0x000000000000-0x000000780000 : "fsbl"
[    1.259061] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.265382] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.271670] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.278360] 0x000001100000-0x000001600000 : "reserved1"
[    1.284536] 0x000001600000-0x000003e00000 : "rootfs"
[    1.290490] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.296725] 0x000004800000-0x000007000000 : "siglent"
[    1.302817] 0x000007000000-0x00000d400000 : "datafs"
[    1.308894] 0x00000d400000-0x00000fc00000 : "upgrade_cramdisk"
[    1.315820] 0x00000fc00000-0x000010000000 : "reserved2"
[    1.324034] TCP: cubic registered
[    1.327276] NET: Registered protocol family 17
[    1.331716] lib80211: common routines for IEEE802.11 drivers
[    1.337825] Registering SWP/SWPB emulation handler
[    1.349593] cramfs_fill_nand blocks is 320-----------------------
[    1.349593]
[    1.349593]
[    1.349593]
[    1.363081] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.369933] devtmpfs: mounted
[    1.373116] Freeing unused kernel memory: 192K (40626000 - 40656000)
[    1.472440] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.623754] hub 1-1:1.0: USB hub found
[    1.627935] hub 1-1:1.0: 3 ports detected
Starting rcS...
 Mounting filesystem
[    1.804378] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.206471] UBI-0: scan_all:scanning is finished
[    2.218867] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[    2.226325] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.234884] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.243387] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.252052] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[    2.259802] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.268735] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 10/4, WL threshold: 4096, image sequence number: 950638423
[    2.279582] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[    2.290534] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 662
[    2.294871] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[    2.456155] UBI-1: scan_all:scanning is finished
[    2.467921] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 40 MiB)
[    2.475371] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.483930] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.492433] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.501232] UBI-1: ubi_attach_mtd_dev:good PEBs: 320, bad PEBs: 0, corrupted PEBs: 0
[    2.508958] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.517855] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 13/9, WL threshold: 4096, image sequence number: 1819264682
[    2.528786] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 320, PEBs reserved for bad PEB handling: 40
[    2.539818] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 666
[    2.544307] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[    2.586871] UBI-2: scan_all:scanning is finished
[    2.597656] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    2.608741] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[    2.616346] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.624925] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.633428] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.642096] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.649747] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.658688] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 10/6, WL threshold: 4096, image sequence number: 1777018790
[    2.669646] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.680416] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 670
[    2.742578] usb 1-1.2: new high-speed USB device number 3 using ci_hdrc
[    2.767135] UBIFS: mounted UBI device 1, volume 0, name "siglent", R/O mode
[    2.774059] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.783150] UBIFS: FS size: 33775616 bytes (32 MiB, 266 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.792774] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.797803] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 52ED3690-D3C2-49A9-9055-7EBFF2762FCB, small LPT model
[    2.874537] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.881260] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.890386] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.895761] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[    2.899916] scsi host0: usb-storage 1-1.2:1.0
[    2.910329] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.915380] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C429C489-76D4-469B-8BFE-043289ABBD0F, small LPT model
[    2.929148] UBIFS: background thread "ubifs_bgt0_0" started, PID 682
[    2.960826] UBIFS: recovery needed
[    3.026853] UBIFS: recovery completed
[    3.030538] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.036487] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.045634] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.055228] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.060251] UBIFS: media format: w4/r0 (latest is w4/r0), UUID C886A817-B838-46DF-AE16-F9920045A7D7, small LPT model
Upgrade start
 Configure eth0
Starting mdev
[    3.893675] scsi 0:0:0:0: Direct-Access     Generic  Flash-Disk       1.09 PQ: 0 ANSI: 2
[    3.904053] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    3.909788] sd 0:0:0:0: [sda] 15728640 512-byte logical blocks: (8.05 GB/7.50 GiB)
[    3.919526] sd 0:0:0:0: [sda] Write Protect is off
[    3.926123] sd 0:0:0:0: [sda] No Caching mode page found
[    3.931375] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    3.945598]  sda:
[    3.953257] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    4.106171] xilinx-dma 40400000.dma: Probing xilinx axi dma engine...Successful
[    4.132424] xilinx-vdma 43010000.dma: Xilinx AXI VDMA Engine Driver Probed!!
[    4.148108] sigdma_init++++++
[    4.171856] siglentkb probe
[    4.174840] ##### siglentkb registers 4fc3c580 4fc3e5a4 4fc525b8
[    4.201999] usbcore: registered new interface driver mt7601u
[    4.215120] irq = 170
config read
###### Config vdma for wave transform #######
config write
config read
dump s2mm registers
dump mm2s registers
####### done! ########
Config vnc  data to memory
Config done!
[    4.434381] UBIFS: background thread "ubifs_bgt1_0" started, PID 792
ln: /usr/bin/siglent/config/www/web_img/usr: File exists
Starting Lighttpd Web Server: Initializing framebuffer device /dev/fb0...
xres=800, yres=480, xresv=800, yresv=480, xoffs=0, yoffs=0, bpp=16
Initializing touch device /dev/input/event0 ...
Initializing VNC server:
width:  800
height: 480
bpp:    16
port:   5900
Initializing server...
01/01/1970 00:00:04 Listening for VNC connections on TCP port 5900
[    4.619329] random: lighttpd urandom read with 27 bits of entropy available
lighttpd.
[    4.757138] UBIFS: background thread "ubifs_bgt1_0" stops
rcS Complete

Processing /etc/profile... Done

/ # [    5.064577] macb e000b000.ethernet eth0: link up (100/Full)
[INFO]:calibrate_t():line=81:calibrate_t::calibrate_t()
product_type SDS1004X_E
mkdir: can't create directory '/usr/bin/siglent/usr/wifi/': File exists
rm: can't remove '/usr/bin/siglent/usr/wifi/wpa_supplicant': No such file or directory

                                                       $Task start:: SCPI
 
                                                       $Task start:: Devce
 
                                                       $Task start:: WLAN
 vxi11_main = 6861.09

                                                       $Task start:: Udisk&Lan
sh: write error: Invalid argument
 
                                                       $Task start:: Vxi11_client
 drv_instance_manage_t: produce_id: 13501[    6.916941] FAT-fs (sda): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

(DRV_PRODUCT_PIKACHU)
_drv_product=4
acq_scal_user = -1.000000
eth0 on

[    6.984507] device eth0 entered promiscuous mode
ready...
ready...
ready...
ready...
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_awg_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_wifi_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_mso_license.txt
[    7.336193] export_store: invalid GPIO 115
sh: write error: Invalid argument
scpi_register_cmd_boardtest
sh: can't create /sys/class/gpio/gpio115/direction: nonexistent directory
sh: can't create /sys/class/gpio/gpio115/value: nonexistent directory
open file %s fail !!!!/usr/bin/siglent/config/arb/2ASK.wav
ready...
cp: can't stat '/usr/bin/siglent/usr/usr/save_setting.xml': No such file or directory
/usr/bin/siglent/usr/usr/save_setting.xml  not exist

                                                       $Task start:: UI
ifconfig: SIOCGIFFLAGS: No such device
 
                                                       $Task start:: awg_thread
 mod_if_exit_handler:signal=11
Clean Up Ready!
Clean Up - nlog
Clean Up - Main Thread
Clean Up - scpi
Clean Up - timer
Clean Up - dev_thread
Clean Up - ui
Clean Up - acq_thread
Clean Up - acq_data
Clean Up - draw_wave
Clean Up - bu_cfg
Clean Up - bu_main
Clean Up - bu_app
Clean Up - key
Clean Up - other
Clean Up - usbtmc
Clean Up - VXI_11
Clean Up - dev_interrupt
Clean Up - wlan_manager
Clean Up - power_off
Clean Up - telnet_scpi
Clean Up - socket_scpi
Clean Up - vxi11_client
Clean Up - Config
Clean Up - sdg_Timer
Clean Up - awg_thread
Clean Up - usbtmc_assistant_interrupt
Clean Up Over!
sds1000b.app: mempool.h:81: MemoryChunk::~M[   11.072046] Free all channel resources.
emoryChunk(): Assertion `tempcount==count' failed.
tempcount=0,[   11.077790] Free all channel resources.


3. Start sds1000b.app commnd

Code: [Select]
/usr/bin/siglent/sds1000b.app &
[1]-  Aborted                    /usr/bin/siglent/sds1000b.app
/ #
/ # [INFO]:calibrate_t():line=81:calibrate_t::calibrate_t()
product_type SDS1004X_E
mkdir: can't create directory '/usr/bin/siglent/usr/wifi/': File exists
rm: can't remove '/usr/bin/siglent/usr/wifi/wpa_supplicant': No such file or directory

                                                       $Task start:: SCPI
route: SIOCADDRT: File exists
 
                                                       $Task start:: Devce
sh: write error: Device or resource busy
sh: write error: Device or resource busy
sh: write error: Device or resource busy
sh: write error: Device or resource busy
 vxi11_main = 1.89248e+06
drv_instance_manage_t: produce_id: 13501
(DRV_PRODUCT_PIKACHU)
_drv_product=4

                                                       $Task start:: WLAN
 
                                                       $Task start:: Udisk&Lan
 acq_scal_user = -1.000000

                                                       $Task start:: Vxi11_client
[ 1892.568522] export_store: invalid GPIO 115
sh: write error: Invalid argument
sh: can't create /sys/class/gpio/gpio115/direction: nonexistent directory
sh: can't create /sys/class/gpio/gpio115/value: nonexistent directory
 open file %s fail !!!!/usr/bin/siglent/config/arb/2ASK.wav
ready...
ready...
ready...
ready...
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_awg_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_wifi_license.txt
bu_cfg module error:mode-type:/usr/bin/siglent/firmdata0/options_mso_license.txt
scpi_register_cmd_boardtest
ready...
cp: can't stat '/usr/bin/siglent/usr/usr/save_setting.xml': No such file or directory
/usr/bin/siglent/usr/usr/save_setting.xml  not exist

                                                       $Task start:: UI
 mod_if_exit_handler:signal=11
Clean Up Ready!
Clean Up - nlog
Clean Up - Main Thread
Clean Up - scpi
Clean Up - timer
Clean Up - dev_thread
Clean Up - ui
Clean Up - acq_thread
Clean Up - acq_data
Clean Up - draw_wave
Clean Up - bu_cfg
Clean Up - bu_main
Clean Up - bu_app
Clean Up - key
Clean Up - other
Clean Up - usbtmc
Clean Up - VXI_11
Clean Up - dev_interru[ 1894.929648] Free all channel resources.
pt
Clean Up - wlan_manager
Clean Up - power_off
Clean Up - te[ 1894.937666] Free all channel resources.
lnet_scpi
Clean Up - socket_scpi
Clean Up - vxi11_client
Clean Up - Config
Clean Up - sdg_Timer
Clean Up - awg_thread
Clean Up - usbtmc_assistant_interrupt
Clean Up Over!
sds1000b.app: mempool.h:81: MemoryChunk::~MemoryChunk(): Assertion `tempcount==count' failed.

 
The following users thanked this post: ssaenek

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #185 on: September 25, 2019, 09:08:21 pm »
So, you can place back the missing files, right?
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #186 on: September 26, 2019, 07:24:21 am »
turned out that languages files are on right place. ???
 

Offline aimc

  • Contributor
  • Posts: 22
  • Country: ca
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #187 on: September 26, 2019, 02:02:27 pm »
Thank you for all this work! I would be interested if anyone really measured the bandwidth after this "upgrade" that merely shows a different Siglent product which is capable of 200MHz. Just seeing a different model name is not really convincing! No one in this forum has posted a sweep up to 200MHz before and after the hack. Could someone please do so to satisfy my curiosity but more importantly the fact that this upgrade indeed is valid?

Thanks
Lutz
 

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #188 on: September 26, 2019, 02:15:18 pm »
No one in this forum has posted a sweep up to 200MHz before and after the hack. Could someone please do so to satisfy my curiosity but more importantly the fact that this upgrade indeed is valid?

There are plenty of those validations in the right threads. You just didn't search enough. No need to start over that theme.
 
The following users thanked this post: aimc

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #189 on: September 26, 2019, 02:17:27 pm »
turned out that languages files are on right place. ???

 :o  :o
 

Offline aimc

  • Contributor
  • Posts: 22
  • Country: ca
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #190 on: September 27, 2019, 02:33:51 am »
Indeed, my bad - sorry. I found the validations in a different thread.
Thanks
Lutz
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #191 on: September 27, 2019, 12:26:14 pm »
I'm a little bit farther with my work:)

Using UART interface there is an option to stop autoboot by taping any key during starting of scope.

Code: [Select]
Start menu vdma ...
Config AXI VDMA...
Start menu vdma done.


U-Boot 2014.07-svn32760 (Mar 23 2018 - 01:35:12)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 243 MiB
NAND:  256 MiB
MMC:   zynq_sdhci: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
int board_late_init(void)+++++
[INFO]int fb_display_logo(void)++++++++++++
[INFO]pStorageMem=0xfa00000, logo_data=0x200036, width=800, height=480
 [INFO]int fb_display_logo(void)----------
int board_late_init(void)-----
Net:   Gem.e000b000
Hit any key to stop autoboot:  0

I'm using putty (serial mode) to tapping any key. This giving me access to uboot command line. Using uboot it is possible to read and write NAND memory without any limits.

here is uboot commands list:

Code: [Select]
zynq-uboot> help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootvx  - Boot vxWorks from an ELF image
bootz   - boot Linux zImage image from memory
clk     - CLK sub-system
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dcache  - enable or disable data cache
dfu     - Device Firmware Upgrade
dhcp    - boot image via network using DHCP/TFTP protocol
echo    - echo args to console
editenv - edit environment variable
env     - environment handling commands
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls  - list files in a directory (default /)
ext4write- create a file in the root directory
false   - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fatwrite- write file into a dos filesystem
fdt     - flattened device tree utility commands
fpga    - loadable FPGA image support
go      - start application at address 'addr'
help    - print command description/usage
i2c     - I2C sub-system
icache  - enable or disable instruction cache
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
mdio    - MDIO utility commands
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
showvar - print local hushshell variables
sleep   - delay execution for some time
source  - run script from memory
spl     - SPL configuration
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
tftpput - TFTP put command, for uploading files to a server
thordown- TIZEN "THOR" downloader
true    - do nothing, successfully
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version

using it I've updated OS manually. All necessery comands and adresses for uboot are in sds1004x_e_udiskEnv.txt file from official siglent SDS1004X-E_OSV1_EN pack. All need to be done is putting files(uImage, devicetree.dtb, rootfs.cramfs) to USB drive, insert it to scope and  mount by command:

usb start

and then flash files to nand by:

Code: [Select]
if fatload usb 0 0x100000 uImage; then nand erase 0x780000 0x400000;nand write 0x100000 0x780000 ${filesize};mw.b 0x100000 0x0 ${filesize}; fi
if fatload usb 0 0x100000 devicetree.dtb; then nand erase 0xB80000 0x80000;nand write 0x100000 0xB80000 ${filesize};mw.b 0x100000 0x0 ${filesize}; fi
if fatload usb 0 0x100000 rootfs.cramfs; then nand erase 0x1600000 0x2800000;nand write 0x100000 0x1600000 ${filesize};mw.b 0x100000 0x0 ${filesize}; fi

I've done it, but my scope still can't start sds1000b.app
Probably the mess is somewhere else. Maybe flash of others files (firmdata0.img, siglent.img, datafs.img) from sds1004x_e_udiskEnv.txt would fix this problem but I don't have them.  Seems like this data are included in .ads firmware file. In my case I can't use .ads file before sds1000b.app starting.

In fact I have memdump.bin file with all data inside but I'm scare to erase all NAND content(including uboot) and then flash it because comparinng contents of dump with OS pack files I see some differences: e.g.
begining of uImage file should be on address 0x780000 regarding sds1004x_e_udiskEnv.txt but this content in dump file are started in two points: 0x2080000 and 0x6B7C000

devicetree.dtb:
sds1004x_e_udiskEnv.txt -> 0xB80000
memdump.bin -> 0x2000000 and 0x6AFC000

rootfs.cramfs:
sds1004x_e_udiskEnv.txt -> 0x1600000
memdump.bin -> 0xEA27000

I'm not sure is my logic correct?
« Last Edit: September 27, 2019, 12:33:34 pm by ucognitive »
 
The following users thanked this post: ssaenek

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #192 on: September 27, 2019, 12:45:30 pm »
Probably the mess is somewhere else. Maybe flash of others files (firmdata0.img, siglent.img, datafs.img) from sds1004x_e_udiskEnv.txt would fix this problem but I don't have them.  Seems like this data are included in .ads firmware file. In my case I can't use .ads file before sds1000b.app starting.

Don't flash the whole NAND!

You've done a great job. Just continue with it, methodically.

Later today I'll decrypt those .ADS where you can extract the .img files. Then you can flash them individually.

Which was the FW version that you had in the scope?
 
The following users thanked this post: ssaenek

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #193 on: September 27, 2019, 01:22:16 pm »
Thanks in advance. I have 6.1.25R2 now.
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #194 on: September 27, 2019, 04:52:59 pm »
tv84

it works:)

I found "siglent" backup folder and replaced files manually.
After this operation sds1000b.app got up. I updated to .33 version and did trick with language files names using putty serial(it works exactly like a root).
Now it's ok. Scope is fully unlocked with english language.

thanks for help. I hope our conversation can help others also. This serial access to root and uboot is pretty interesting. I'm wondering is this option also on others siglent devices.
« Last Edit: September 27, 2019, 04:54:39 pm by ucognitive »
 
The following users thanked this post: ssaenek

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #195 on: September 27, 2019, 07:00:19 pm »
it works:)

What's the answer to this SCPI command?

MD5_PR?
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #196 on: September 28, 2019, 03:35:00 pm »
SDS1000X-E
 

Online tv84

  • Super Contributor
  • ***
  • Posts: 2345
  • Country: pt
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #197 on: September 28, 2019, 03:48:38 pm »
So, can you simply update with the latest FW and it will stay in english? Or does it revert to chinese?

Besides the label on the scope box, where do you see the "X-C" reference? (in what screen/menu)
 

Offline aimc

  • Contributor
  • Posts: 22
  • Country: ca
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #198 on: September 28, 2019, 05:56:10 pm »
No need to start over that theme.

You are absolutely right, there is no need to warm up old stories. To my excuse, I wasn't aware of them. Nonetheless, I am attaching the max. DFT's (direct 50 Ohm BNC-T terminated) of a 50-400MHz sweep from the VCO of a "Geekcreit® Spectrum Analyzer USB LTDZ 35-4400M" from Banggood - before and after the hack. Its an absolute Bobby Dazzler  ;D. A different can of worms seems to be the questions of what probes to use now. I know there is tons of material on the EEVBlog forums and comprehensive reviews, so I will find my way.
« Last Edit: September 28, 2019, 06:04:38 pm by aimc »
 

Offline ucognitive

  • Contributor
  • Posts: 13
  • Country: pl
Re: Unlocking Siglent SDS1104X-E, step by step
« Reply #199 on: September 29, 2019, 04:01:34 pm »
After updating FW language is changing back to Chinese.

I see X-C label on scope info screen with versions.
Also *IND? command return X-C model name.
 
The following users thanked this post: ssaenek


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf