Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[arturfra]

Excuse me guys i know probably you told a lot of time but i’m a little bit confused, if i’ll buy a SSA3021XPLUS the exact and best procedure is first to port it into SSA3032XPLUS or is it enought to follow the procedure to crossflash it into SVA? I’d like to have all option on and keep the serial number, thanks

[Sighound36]

Tv84 never ceases to deliver the coding goods 

Top stuff the wizard of 1's & 0's does it again

Perhaps a EEV  award for one of the most decent helpful members of the community 

More from the Dumbledore of the datastreams  has also been busy on other fronts more on that project in new thread later

[Ghislain]

Excuse me guys i know probably you told a lot of time but i’m a little bit confused, if i’ll buy a SSA3021XPLUS the exact and best procedure is first to port it into SSA3032XPLUS or is it enought to follow the procedure to crossflash it into SVA? I’d like to have all option on and keep the serial number, thanks

Hi, have a look at post #1223, that explains it pretty well 
To my understanding it is basically a four step procedure starting from a 'standard' SSA3021x+:
1. Gain Telnet access to your SSA+ device
2. Perform a backup (optional but highly recommended)
3. Perform the SSA+ upgrade procedure
4. Transform the upgraded SSA+ into the corresponding SVA type
Keeping (actually reconfiguring) the serial number and all of the licenses attached to that is another challenge, the procedure is not public but some here may be able to help.

[mairas]

Hey, just got myself a spanking new SSA 3021X Plus and successfully upgraded it with maximevince's instruction summary to SVA 1032X firmware version 2.2.1.2.8. Thanks a lot for everyone participating in this thread! I feel giddy with excitement!

Q: My device has at the moment a serial number with all X's. I wonder is it safe to update the firmware to the latest V3.2.2.3.3R1 available on Siglent's website? Do I lose any of the upgrades and if I do, can I just reapply the process to reacquire them?

[tv84]

It's safe.

[mairas]

It's safe.

Yep, worked without a hitch. Thank you, sir!

[derek1ee]

Hi -

I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.

However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".

I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?

(I haven't completed the step to enable all options with serial # turning into all Xs).

Thanks!

[gussy]

(I haven't completed the step to enable all options with serial # turning into all Xs).

From memory, you need to unlock the options to get the bandwidth and VNA enabled.

[Kibabalu]

Hi -

I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.

However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".

I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?

(I haven't completed the step to enable all options with serial # turning into all Xs).

Thanks!

How did you get to FW V3.2.2.3.3R1?

How did you handle the renaming of ecomb_p to ecomp and changing the call of it inside "startup_app.sh"?

For the newest FW the name of the application changed from ecomp to Aladdin, thus an application like ecomp should not exist for FW V3.2.2.3.3R1.

--> See post 1368 from tv84!

[techneut]

Hi -

I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.

However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".

I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?

(I haven't completed the step to enable all options with serial # turning into all Xs).

Thanks!

3.2 GHz is one of the options, so you have to unlock them to get it.

[derek1ee]

Hi -

I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.

However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".

I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?

(I haven't completed the step to enable all options with serial # turning into all Xs).

Thanks!

How did you get to FW V3.2.2.3.3R1?

How did you handle the renaming of ecomb_p to ecomp and changing the call of it inside "startup_app.sh"?

For the newest FW the name of the application changed from ecomp to Aladdin, thus an application like ecomp should not exist for FW V3.2.2.3.3R1.

--> See post 1368 from tv84!

The unit arrived with 3.2.2.3.3R1 already installed.

I did not - "except step 2/3 since it's no longer required per a later post".

[derek1ee]

(I haven't completed the step to enable all options with serial # turning into all Xs).

From memory, you need to unlock the options to get the bandwidth and VNA enabled.

Hi -

I have a SSA3021X Plus with the latest V3.2.2.3.3R1 firmware, and followed post #1223 (except step 2/3 since it's no longer required per a later post), and was able to flash the factory SVA 1032X V3.2.2.3.3R1 firmware.

However, after the upgrade, I have TG menu disabled (and TG not even showing a permanently enabled option under info like before the flash), I also don't see disabled VNA option under "Mode".

I then updated "NSP_trends_config_info.xml" as per instruction, and have since got TG option back. However, I'm still capped at 2.1G, but it's my understanding that it should now have been expanded to 3.2G, what am I doing wrong?

(I haven't completed the step to enable all options with serial # turning into all Xs).

Thanks!

3.2 GHz is one of the options, so you have to unlock them to get it.

Thanks! That's indeed the case, I'm now unlocked all options with SN becoming all Xs. Now to research how to get the actual SN back.

Thanks everyone and happy new year!

[Kibabalu]

I have a question regarding the "EMI Measurement" option.

My LISN, in fact the design comes here from this forum, attenuates by 10dB.

During "normal" SA operation I can take an external attenuation into account by using the parameter "Ref Offset" of the Menu "Amplitude".

But during the "EMI Measurement" mode this parameter doesn't affect the measurement curve, it just shifts the reference level of the graph and "Ref Offset" is not added to the measured spectrum.

Thus I have to lower the EMI limits by 10dB to take the external attenuation into account. This seems not right for me, it should exactly be like during SA operation.

Is it a bug or is there a misunderstanding on my side?

[rogersstuart]

Do these support external mixing to extend the frequency range?

[NCG]

tv84 -  could there be hope for glimpse into the realtime versions internals? It seems there is no teardowns up anywhere I have managed to look.

[tv84]

tv84 -  could there be hope for glimpse into the realtime versions internals? It seems there is no teardowns up anywhere I have managed to look.

Don't know anyone who is wiling to open it up.

[stoepie2002]

On the plus devices, is there a way to re-enable the options for 128 hours, by backup & restore of some file?

I am not (yet ) looking to hack the analyzer and turn the serial number into all x's. Maybe after some time....

Also, for me, the VNA is not really interesting. It's not four port, the smith chart is so-so (no values) and from what I've read, only 201 points.

I'd rather keep it close to stock for warranty purposes.

Maybe I need to unbox it first haha - it just arrived.

Cheers to all for all the good work and info provided here.

[Bicurico]

Once you try to restore the timed options, you might as well fully hack your device.

[stoepie2002]

If there would be a way to do that and keep the serial number in place then I'd do that straight away.

But you are probably right, Siglent would probably be able to see that no license was bought for the unit anyway.

[Bicurico]

What difference would it make?

If you are concerned that your device would need a repair under warranty, having it hacked with or without serial number would make no difference at all: Siglent would be aware that a hack has been carried out anyway.

You could backup the flash of your device prior to any hack and in case of need restore the backup, but if the device is broken, chances are that you could not restore the backup.

A hack is what it is: you get more functionality without paying for it, in exchange of giving up your warranty.

If you want increased functionality AND warranty/support, you need to pay for it and purchase the offical keys.

Regards,
Vitor

[stoepie2002]

Thanks, Vitor. You are right. For that reason I already got the SSA3032X-plus...

[Bicurico]

When you change your mind and decide to hack your device, come back and you will be helped.

Regards,
Vitor

[tautech]

Also, for me, the VNA is not really interesting. It's not four port, the smith chart is so-so (no values) and from what I've read, only 201 points.

201 is the default setting applied with a factory Preset however max VNA points are 751.

[stefkpl]

I do the same error! 

I had a SSA3021X-PLUS => upgrade to SSA3032X-PLUS
I would like to upgrade to SVA1032X and now my siglent wont boot after update firmware

At serial boot I have this :

Code: [Select]

U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 128 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)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net:   Gem.e000b000
Hit any key to stop autoboot:  1  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... 1 Storage Device(s) found
Copying Linux from USB to RAM...
reading boot_uImage
** Unable to read file boot_uImage **
reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
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.2-omg-xilinx-svn35686
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3121840 Bytes = 3 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 06d0d000, end 06d13db2 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.19.2-omg-xilinx-svn35686 (ding@ding-T5810) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #11 SMP PREEMPT Fri Jan 4 15:28:26 CST 2019
[    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 0x09000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 9 pages/cpu @48e92000 s8128 r8192 d20544 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 40640
[    0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=3
[    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: 139704K/163840K available (3835K kernel code, 213K rwdata, 1580K rodata, 196K init, 216K bss, 7752K 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 : 0x4a800000 - 0xff000000   (2888 MB)
[    0.000000]     lowmem  : 0x40000000 - 0x4a000000   ( 160 MB)
[    0.000000]     pkmap   : 0x3fe00000 - 0x40000000   (   2 MB)
[    0.000000]     modules : 0x3f000000 - 0x3fe00000   (  14 MB)
[    0.000000]       .text : 0x40008000 - 0x40552200   (5417 kB)
[    0.000000]       .init : 0x40553000 - 0x40584000   ( 196 kB)
[    0.000000]       .data : 0x40584000 - 0x405b96a0   ( 214 kB)
[    0.000000]        .bss : 0x405b96a0 - 0x405ef914   ( 217 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 4a804000
[    0.000000] zynq_clock_init: clkc starts at 4a804100
[    0.000000] Zynq clock init
[    0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000128] timer #0 at 4a806000, irq=17
[    0.000477] Console: colour dummy device 80x30
[    0.000495] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090270] pid_max: default: 32768 minimum: 301
[    0.090420] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090436] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091059] CPU: Testing write buffer coherency: ok
[    0.091253] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.091320] Setting up static identity map for 0x39c880 - 0x39c8d8
[    0.240257] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.240333] Brought up 2 CPUs
[    0.240353] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[    0.240361] CPU: All CPU(s) started in SVC mode.
[    0.240863] devtmpfs: initialized
[    0.241585] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.247260] NET: Registered protocol family 16
[    0.249163] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.271077] cpuidle: using governor ladder
[    0.301042] cpuidle: using governor menu
[    0.309216] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.309232] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.309362] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[    0.319988] vgaarb: loaded
[    0.320392] SCSI subsystem initialized
[    0.320773] usbcore: registered new interface driver usbfs
[    0.320860] usbcore: registered new interface driver hub
[    0.321047] usbcore: registered new device driver usb
[    0.321200] phy0 supply vcc not found, using dummy regulator
[    0.321295] phy1 supply vcc not found, using dummy regulator
[    0.321414] --------------usb_udc_init ------
[    0.321658] pps_core: LinuxPPS API ver. 1 registered
[    0.321670] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.321728] PTP clock support registered
[    0.321874] EDAC MC: Ver: 3.0.0
[    0.323408] Switched to clocksource arm_global_timer
[    0.335318] NET: Registered protocol family 2
[    0.336059] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.336110] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.336168] TCP: Hash tables configured (established 2048 bind 2048)
[    0.336212] TCP: reno registered
[    0.336228] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.336258] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.336455] NET: Registered protocol family 1
[    0.336768] RPC: Registered named UNIX socket transport module.
[    0.336781] RPC: Registered udp transport module.
[    0.336790] RPC: Registered tcp transport module.
[    0.336798] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.337166] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.338495] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.340105] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.341126] io scheduler noop registered
[    0.341146] io scheduler deadline registered
[    0.341197] io scheduler cfq registered (default)
[    0.343216] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.343236] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.343754] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[    0.917282] console [ttyPS0] enabled
[    0.921432] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[    0.928171] [drm] Initialized drm 1.1.0 20060810
[    0.940640] brd: module loaded
[    0.947608] loop: module loaded
[    0.956769] libphy: MACB_mii_bus: probed
[    1.033526] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[    1.043428] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.054940] i2c /dev entries driver
[    1.060164] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[    1.066614] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[    1.073887] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.080100] Xilinx Zynq CpuIdle Driver started
[    1.085189] ledtrig-cpu: registered to indicate activity on CPUs
[    1.092190] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.098503] nand: Micron MT29F2G08ABAEAWP
[    1.102482] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.110076] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.121581] Bad block table found at page 131008, version 0x01
[    1.127857] Bad block table found at page 130944, version 0x01
[    1.133986] 12 ofpart partitions found on MTD device pl353-nand
[    1.139837] Creating 12 MTD partitions on "pl353-nand":
[    1.145093] 0x000000000000-0x000000780000 : "fsbl"
[    1.150912] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.157160] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.163529] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.170216] 0x000001100000-0x000001600000 : "reserved1"
[    1.176418] 0x000001600000-0x000003e00000 : "rootfs"
[    1.182297] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.188441] 0x000004800000-0x000006c00000 : "siglent"
[    1.194472] 0x000006c00000-0x00000d000000 : "datafs"
[    1.200494] 0x00000d000000-0x00000da00000 : "log"
[    1.206168] 0x00000da00000-0x00000f800000 : "upgrade_cramdisk"
[    1.212968] 0x00000f800000-0x000010000000 : "reserved2"
[    1.221035] TCP: cubic registered
[    1.224522] NET: Registered protocol family 17
[    1.229141] Registering SWP/SWPB emulation handler
[    1.235795] rtc-ds1307 0-0068: setting system clock to 2021-01-07 16:25:40 UTC (1610036740)
[    1.249172] cramfs_fill_nand blocks is 320-----------------------
[    1.249172]
[    1.249172]
[    1.249172]
[    1.262187] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.269090] devtmpfs: mounted
[    1.272232] Freeing unused kernel memory: 196K (40553000 - 40584000)
Starting rcS...
[    1.544516] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[    1.692213] UBI-1: scan_all:scanning is finished
[    1.703199] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[    1.714340] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[    1.721757] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.730414] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.738913] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.747611] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.755362] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.764317] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 14/2, WL threshold: 4096, image sequence number: 1331120951
[    1.775276] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[    1.786165] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 582
[    1.788517] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[    1.832666] UBI-2: scan_all:scanning is finished
[    1.843444] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    1.854474] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[    1.862071] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.870712] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.879222] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.887920] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    1.895576] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.904538] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 25/13, WL threshold: 4096, image sequence number: 2009223325
[    1.915604] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    1.926390] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 586
[    1.928526] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[    1.972834] UBI-3: scan_all:scanning is finished
[    1.983606] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    1.994595] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[    2.001662] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.010298] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.018813] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.027512] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.035193] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.044187] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 1866265482
[    2.055009] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.065807] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 590
[    2.074476] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.474095] UBI-0: scan_all:scanning is finished
[    2.486319] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[    2.493781] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.502346] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.510890] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.519586] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[    2.527340] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.536293] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 626955013
[    2.547079] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[    2.558055] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 594
[    2.571547] UBIFS: background thread "ubifs_bgt1_0" started, PID 597
[    2.603045] UBIFS: recovery needed
[    2.701549] UBIFS: recovery completed
[    2.705247] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[    2.711268] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.720423] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.730074] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.735121] UBIFS: media format: w4/r0 (latest is w4/r0), UUID F1827086-F8DE-48BE-B9C2-AF1F551BC6EE, small LPT model
[    2.780797] UBIFS: recovery needed
[    2.821225] UBIFS: recovery deferred
[    2.824822] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.831546] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.840702] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.850088] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.855136] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 68D1D634-0B41-44C3-8EE7-5B148BE8F0D7, small LPT model
[    2.868520] UBIFS: background thread "ubifs_bgt3_0" started, PID 600
[    2.899988] UBIFS: recovery needed
[    2.922587] UBIFS: recovery completed
[    2.926264] UBIFS: mounted UBI device 3, volume 0, name "log"
[    2.931944] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.941097] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.950484] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.955535] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 35E3C92F-68EC-461E-A46E-9F549FBFB3F1, small LPT model
[    2.969176] UBIFS: background thread "ubifs_bgt0_0" started, PID 602
[    3.000723] UBIFS: recovery needed
[    3.091182] UBIFS: recovery completed
[    3.094874] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.100811] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.109966] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.119613] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.124663] UBIFS: media format: w4/r0 (latest is w4/r0), UUID AB78C81C-0D18-4506-91AE-D6D46AF0DBD0, small LPT model
rm: can't remove '/usr/bin/siglent/usr/mass_storage/U-disk*': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/tmp/*_U-disk*': No such file or directory
[    5.556271] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f0a380
Bus error
[    5.583000] irq = 170
[    5.595039] <<-GTP-INFO->> GTP driver installing...
[    5.600037] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[    5.605918] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[    5.611975] <<-GTP-INFO->> GTP I2C Address: 0x14
[    5.616624] 0-0014 supply vdd_ana not found, using dummy regulator
[    5.622834] 0-0014 supply vcc_i2c not found, using dummy regulator
[    5.629063] <<-GTP-INFO->> Guitar reset
[    5.753919] <<-GTP-INFO->> IC Version: 928_1060
[    5.764591] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[    5.783429] <<-GTP-INFO->> create proc entry gt9xx_config success
[    5.789709] input: goodix-ts as /devices/virtual/input/input0
[    5.795699] <<-GTP-INFO->> GTP works in interrupt mode.
[    5.811437] gpib_usb_init
[    5.814208] usbcore: registered new interface driver usb-gpib
[    5.909323] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.920626] ehci-pci: EHCI PCI platform driver
[    5.949646] e0002000.usb supply vbus not found, using dummy regulator
[    5.956418] ci_hdrc ci_hdrc.0: EHCI Host Controller
[    5.961252] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[    5.983503] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[    5.988988] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.995786] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.002941] usb usb1: Product: EHCI Host Controller
[    6.007830] usb usb1: Manufacturer: Linux 3.19.2-omg-xilinx-svn35686 ehci_hcd
[    6.014983] usb usb1: SerialNumber: ci_hdrc.0
[    6.019965] hub 1-0:1.0: USB hub found
[    6.023721] hub 1-0:1.0: 1 port detected
[    6.028201] e0003000.usb supply vbus not found, using dummy regulator
[    6.067631] usbcore: registered new interface driver usb-storage
[    6.087229] usbcore: registered new interface driver usbhid
[    6.092742] usbhid: USB HID core driver
[    6.102279] mousedev: PS/2 mouse device common for all mice
0x00000000
0x00000000
[    6.343496] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    6.477558] random: lighttpd urandom read with 17 bits of entropy available
Initializing framebuffer device /dev/fb0...
xres=1024, yres=600, xresv=1024, yresv=600, xoffs=0, yoffs=0, bpp=16[    6.505149] input: PolyVision Touch Screen as /devices/virtual/input/input1

Initializing touch device /dev/input/event0 ...
Reading From :(goodix-ts)
buttonMask: xmin:0
xmax: 1024
ymin:0
ymax: 600
Initi[    6.527562] usb 1-1: New USB device found, idVendor=1f75, idProduct=0918
alizing VNC server:
width:  1024
height: 600
bpp:    16
[    6.535509] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4
port:   5900
Initializing server...
[    6.548187] usb 1-1: Product: STORAGE DEVICE
07/01/2021 16:25:45 [    6.556268] usb 1-1: SerialNumber: 201005KT202010000000424
Listening for VNC connections on TCP port 5900
[    6.564240] usb-storage 1-1:1.0: USB Mass Storage device detected
[    6.582779] scsi host0: usb-storage 1-1:1.0
rcS Complete

(none) login: [    7.587012] scsi 0:0:0:0: Direct-Access     Specific STORAGE DEVICE   0009 PQ: 0 ANSI: 4
[    7.596083] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    7.601372] sd 0:0:0:0: [sda] 61440000 512-byte logical blocks: (31.4 GB/29.2 GiB)
[    7.609938] sd 0:0:0:0: [sda] Write Protect is off
[    7.615432] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    7.630193]  sda: sda1
[    7.635972] sd 0:0:0:0: [sda] Attached SCSI removable disk
insert~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
devName ==sda
devName ==sda1
sda1
sleep time == 0
/usr/bin/siglent/usr/tmp/sda1_U-disk0
[  162.570846] usb 1-1: USB disconnect, device number 2
remove~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sda
name  == sda
mapfilelist  == /usr/bin/siglent/usr/tmp/sda1_U-disk0
mapfile  == /usr/bin/siglent/usr/tmp/sda1_U-disk0
mountFile  == /usr/bin/siglent/usr/mass_storage/U-disk0
[  162.623682] FAT-fs (sda1): unable to read boot sector to mark fs as dirty
[  226.213452] usb 1-1: new high-speed USB device number 3 using ci_hdrc
[  226.384188] usb 1-1: New USB device found, idVendor=1f75, idProduct=0918
[  226.390838] usb 1-1: New USB device strings: Mfr=0, Product=3, SerialNumber=4
[  226.397993] usb 1-1: Product: STORAGE DEVICE
[  226.402224] usb 1-1: SerialNumber: 201005KT202010000000424
[  226.410545] usb-storage 1-1:1.0: USB Mass Storage device detected
[  226.416874] scsi host1: usb-storage 1-1:1.0
[  227.417025] scsi 1:0:0:0: Direct-Access     Specific STORAGE DEVICE   0009 PQ: 0 ANSI: 4
[  227.426271] sd 1:0:0:0: Attached scsi generic sg0 type 0
[  227.431754] sd 1:0:0:0: [sda] 61440000 512-byte logical blocks: (31.4 GB/29.2 GiB)
[  227.440215] sd 1:0:0:0: [sda] Write Protect is off
[  227.445705] sd 1:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  227.460464]  sda: sda1
[  227.466117] sd 1:0:0:0: [sda] Attached SCSI removable disk
insert~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
devName ==sda
devName ==sda1
sda1
sleep time == 0
[  227.498323] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
/usr/bin/siglent/usr/tmp/sda1_U-disk0



I can enter in zynq-uboot

Code: [Select]

U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)

Board: Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 128 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)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net:   Gem.e000b000
Hit any key to stop autoboot:  1  0
zynq-uboot> j*hj*hj*ll
Unknown command 'j*hj*hj*ll' - try 'help'
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
md5check- check MD5 message digest
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 vers


The uImage file to reflash that portion with can be extracted from any of their firmware files

This one is from 2.2.1.2.5

How can I solve my mistake ?

The root password was know?

Please help me   

Thanks

[Bicurico]

stefkpl tried to upgrade with "SVA1032X_3.2.2.3.2_EN.ADS".

As explained before, this FW is not safe!

It will not delete the executable (ecomb_p) correctly and as a result the FW upgrade will run out of free flash memory and fail. The executable will be corrupt and the device will not start.

It is recommended to use the newer SVA1032X_V3.2.2.3.3R1_EN.ADS which is safe.

Regards,
Vitor