Author Topic: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers (Read 630442 times)

Crambone · « **Reply #2125 on:** January 05, 2023, 06:15:49 pm »

What Python program is suggested? I see IDOL and several other available?

tubularnut · « **Reply #2126 on:** January 05, 2023, 06:19:35 pm »

Search for Python in the box at the top of this page. Search within ‘this topic’

As you scroll down the results, you’ll find the script.

DeDe · « **Reply #2127 on:** January 05, 2023, 06:55:54 pm »

Python-Script: https://www.online-python.com/PX3v0J8nbs
Select the System|System Info menu on your device and read the "Host ID" (not serial) and modify the script on that web-site.
Uncomment your model, e.g. Model = 'SSA3000X_Plus'
Execute script and then you should be able with menu option System|Load Option to enter the keys you want (e.g. ALL + 3032).

Regarding not working backup SSA3000X+_backup_11411.ADS - of course script will only work under following conditions;:

Before crossflash on original SS3000X *Plus* devices with V3.2.x.y.z firmware
Plugged in USB-Stick formatted with a single FAT32 partition
USB-Stick should allow write access: try with File|Create Folder if you can create a new folder on your stick

Here some useful links:
Python Script Discussion a few pages back in this thread: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4355635/#msg4355635
Another list of steps in this thread: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4355635/#msg4355635
Very detailed description form electr_peter: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577
Newer checklist from user uski in the "Hack it.." thread: https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg4596574/#msg4596574

Major1206 · « **Reply #2128 on:** January 05, 2023, 07:06:14 pm »

Hi everyone,
I wasn't sure about crossflash, so first did PYTHON to have ALL + 3032.
2: Full Backup
3: Crossflash from SSA 5.1R20 to SVA 5.1R1 using TV84 hex mod
4: No need to python again - ALL permanent, 3.2GHz working, VNA working
Issue: no Telnet for me either SSA telnet.ads notr SVA telnet.ads -> can't copy na_1p, na_2p ,
Question un-crossflash -> copy cal -> crosflash again? Or sth else?

Edit:
found solution -> SCPI 'DEBTTT'
telnet IP port 23
username:root paswd:ding1234
Currently I am struggling with:

Quote

To fix this, it was necessary to copy those 2 files na_1p + na_2p to /usr/bin/siglent/firmdata0/cali

Now I have permission issue to firmdata0/cali " Read-only file system"

DeDe · « **Reply #2129 on:** January 05, 2023, 08:15:18 pm »

You need to make filesystem writable, login via telnet and:
mount -o remount,rw /usr/bin/siglent/firmdata0

BTW: this was also required for me as a first step in order to perform a successful backup with SSA3000X+_backup_11411.ADS on the USB stick - make U-disk0 fs writable:
mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0

After you are done just restart the device once, then all filesystems are read only again.

Thomas · « **Reply #2130 on:** January 05, 2023, 08:17:02 pm »

Quote from: tomud on August 13, 2022, 10:59:43 am

Quote from: tv84 on August 13, 2022, 10:11:42 am
No more time to hand in homework...

To close things off:

"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"

Summarizing the collected information

Script to run:
https://www.online-python.com/PX3v0J8nbs

And added to the attachment (as if the links stopped working).

I used this (excellent!) script to enhance my aging SSA 3021X (non-Plus).

Analyzer data:
SW1: 1.3.9.8
SW2: 20201230-1
SW3: 000000D1
HW: 07.03.00
Bought with TG included permanently and 48 hours of trial for the other options (expired now).

I uncommented Model = 'SSA3000X' and filled in HOSTID as instructed, ran the script and got a list of license keys for all options. Plain and simple

But I am only able to activate options 3032 and EMI, even though that is great in itself.
I don't understand why AMK and Refl won't activate. I get an "Invalid License!" message on the screen when entering the license key for these.

The order of activating licenses is irrelevant, right? I think we're supposed to be able to buy these and activate at any time?
In hindsight I realize I should have activated 3032 and then ALL, but I find it hard to believe this is essential.
Any pointers or suggestions are welcome!

Major1206 · « **Reply #2131 on:** January 05, 2023, 08:23:41 pm »

Jeez,
i was trying
"mount -o remount,rw /usr/bin/siglent"
and mount -o remount,rw /usr/bin/siglent/firmdata0/cali"

Edit
restored classic telnet: "/sbin/telnetd -l /bin/sh -p 10101" & and "/sbin/telnetd -1 /bin/sh -p 10101 &" are not the same

el_man · « **Reply #2132 on:** January 05, 2023, 10:22:39 pm »

Thank so much for your help DeDe!

I succeeded in everything and the upgrade is finished successfully now i have SVA1032X
But unfortunately It seem like something is missing in VNA part maybe This VNA cable

The Smith chart was total Mess and after adding the two configuration files na_1p na_2p it becomes more or less normal at least now it is in the contour of the chart

But the port Doesn't react to any Load 50ohm Close - Nothing!

Where is this "VNA cable" and is there a fix to this?
Any other guy with same version of this firmware 3.2.2.5.1R20 Does Experience the same problem?
My unit is quite New - manufacture date is 13.12.2022 Maybe because of the unlucky date they stop putting the cables

or at lest at This date

Any help will be Highly appreciated!

DeDe · « **Reply #2133 on:** January 06, 2023, 11:45:44 am »

To check the internal TG cable you would have to open the device, see here:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3412882/#msg3412882

But first check what RoV has written:

S11 Port1 is the left TG port
You must first perform a full 1-port calibration and then activate it (turn correction on) as well
You need a fairly decent CAL kit for that

I don't own one of this Siglent-specific CAL.-Kits like F503ME (ca. 400€/$) but I purchased an SMA-Cal-Kit for 40€ from Amazon which even was fully characterized.
I applied it as "User 1" CAL-Kit and set all the parameter.
For a simple test you simply try with some low-cost Short/Open/Load Cal-Kit.

Instrument should display a blue "Cor" in the upper left corner of the screen and not something like "---" or "Off".

DL4JY · « **Reply #2134 on:** January 06, 2023, 04:16:17 pm »

Quote from: Thomas on January 05, 2023, 08:17:02 pm

Quote from: tomud on August 13, 2022, 10:59:43 am
Quote from: tv84 on August 13, 2022, 10:11:42 am
No more time to hand in homework...

To close things off:

"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"

Summarizing the collected information

Script to run:
https://www.online-python.com/PX3v0J8nbs

And added to the attachment (as if the links stopped working).

I used this (excellent!) script to enhance my aging SSA 3021X (non-Plus).

Analyzer data:
SW1: 1.3.9.8
SW2: 20201230-1
SW3: 000000D1
HW: 07.03.00
Bought with TG included permanently and 48 hours of trial for the other options (expired now).

I uncommented Model = 'SSA3000X' and filled in HOSTID as instructed, ran the script and got a list of license keys for all options. Plain and simple
But I am only able to activate options 3032 and EMI, even though that is great in itself.
I don't understand why AMK and Refl won't activate. I get an "Invalid License!" message on the screen when entering the license key for these.

The order of activating licenses is irrelevant, right? I think we're supposed to be able to buy these and activate at any time?
In hindsight I realize I should have activated 3032 and then ALL, but I find it hard to believe this is essential.
Any pointers or suggestions are welcome!

Reply #2007

Major1206 · « **Reply #2135 on:** January 06, 2023, 07:25:52 pm »

It looks like they calibrated VNA oly up to 1.5 Ghz.
On a full span, the response look funny, but one calibrated you should see decent response for 50ohm load and through measurement.
Best

Thomas · « **Reply #2136 on:** January 06, 2023, 08:22:35 pm »

Quote from: Thomas on January 05, 2023, 08:17:02 pm

Quote from: tomud on August 13, 2022, 10:59:43 am
Quote from: tv84 on August 13, 2022, 10:11:42 am
No more time to hand in homework...

To close things off:

"SSA3000X", "SSA3000X_Plus", "SVA1000X", "SSA3000R"

Summarizing the collected information

Script to run:
https://www.online-python.com/PX3v0J8nbs

And added to the attachment (as if the links stopped working).

I used this (excellent!) script to enhance my aging SSA 3021X (non-Plus).

Analyzer data:
SW1: 1.3.9.8
SW2: 20201230-1
SW3: 000000D1
HW: 07.03.00
Bought with TG included permanently and 48 hours of trial for the other options (expired now).

I uncommented Model = 'SSA3000X' and filled in HOSTID as instructed, ran the script and got a list of license keys for all options. Plain and simple
But I am only able to activate options 3032 and EMI, even though that is great in itself.
I don't understand why AMK and Refl won't activate. I get an "Invalid License!" message on the screen when entering the license key for these.

The order of activating licenses is irrelevant, right? I think we're supposed to be able to buy these and activate at any time?
In hindsight I realize I should have activated 3032 and then ALL, but I find it hard to believe this is essential.
Any pointers or suggestions are welcome!

Why don't I just answer myself, since I found the solution

I played around with the (still excellent!) python script by tomud and also made a small script myself for reading and activating options (got tired of typing those license keys).
Then I noticed in the Siglent SSA3000X Programming Guide that valid options are Meas | EMI | CAT | TG. No mention of 3032, but that works.
So AMK is Meas and Refl is CAT. I added Meas and CAT to otheropt in tomud's script:

Code: [Select]

otheropt = ('AMK', 'EMI', 'TG', 'Refl', 'DMA', 'AMA', 'WDMA', 'DTF', 'VNA', 'RT40', '3021', '3032', '3050', '3075', 'ALL', 'Meas', 'CAT')

And now I have all options unlocked and full 3.2GHz bandwidth

Huge thanks to tomud, tv84 and all the others who contributed to this!

DL4JY · « **Reply #2137 on:** January 06, 2023, 09:25:00 pm »

as in reply #2007?

Thomas · « **Reply #2138 on:** January 07, 2023, 05:08:24 am »

Quote from: DL4JY on January 06, 2023, 09:25:00 pm

as in reply #2007?

Oh, someone did answer my question, sorry I missed that

And replies #2006-2009 summarize the same as I found. I missed that too

Summary:
3000X (non-Plus) can get all options and full bandwidth with python on reply #1968.
5 options work: Meas, EMI, CAT, TG and 3032.
ALL does not work, options must be activated separately.

cubitus · « **Reply #2139 on:** January 09, 2023, 03:47:27 pm »

Hello
This afternoon we turned on the analyzer the curve was displayed but everything remained frozen... I turned it off and restarted it and since then it remains on a black screen with the logo Siglent to display

I still have access to the ssa3000 via ssh
What do you advise me to do?
SSA 3021 plus transformed into SVA1032 with all enabled options and the latest firmware.

Code: [Select]

/usr/bin/siglent # ps
PID   USER     TIME   COMMAND
    1 root       0:00 {linuxrc} init
    2 root       0:00 [kthreadd]
    3 root       0:00 [ksoftirqd/0]
    5 root       0:00 [kworker/0:0H]
    6 root       0:00 [kworker/u4:0]
    7 root       0:00 [rcu_preempt]
    8 root       0:00 [rcu_sched]
    9 root       0:00 [rcu_bh]
   10 root       0:00 [migration/0]
   11 root       0:00 [migration/1]
   12 root       0:00 [ksoftirqd/1]
   13 root       0:00 [kworker/1:0]
   14 root       0:00 [kworker/1:0H]
   15 root       0:00 [khelper]
   16 root       0:00 [kdevtmpfs]
   19 root       0:00 [perf]
   56 root       0:01 [kworker/1:1]
  202 root       0:00 [writeback]
  205 root       0:00 [bioset]
  207 root       0:00 [kblockd]
  238 root       0:00 [edac-poller]
  326 root       0:01 [kworker/0:1]
  327 root       0:00 [rpciod]
  341 root       0:00 [kswapd0]
  342 root       0:00 [fsnotify_mark]
  343 root       0:00 [nfsiod]
  441 root       0:00 [spi0]
  455 root       0:00 [spi1]
  564 root       0:00 [irq/23-f8007100]
  571 root       0:00 [deferwq]
  574 root       0:00 [kworker/0:1H]
  575 root       0:00 [kworker/1:1H]
  582 root       0:00 [ubi_bgt1d]
  586 root       0:00 [ubi_bgt2d]
  590 root       0:00 [ubi_bgt3d]
  594 root       0:00 [ubi_bgt0d]
  597 root       0:00 [ubifs_bgt1_0]
  600 root       0:00 [ubifs_bgt3_0]
  602 root       0:00 [ubifs_bgt0_0]
  648 root       0:00 [goodix_wq]
  692 root       0:00 telnetd
  716 root       0:00 [ci_otg]
  730 root       0:00 [kworker/0:2]
  739 root       0:00 /usr/bin/siglent/vsftpd
  742 1          0:00 portmap
  774 root       0:00 [kworker/u4:3]
  882 root       0:00 /usr/bin/siglent/vncserver
  887 root       0:00 /usr/sbin/lighttpd -f /usr/bin/siglent/lighttpd.conf
  888 root       0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
  890 root       0:00 /sbin/getty -L ttyPS0 115200 vt100
  894 root       0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini
  895 root       0:00 -sh
  897 root       0:00 ps

Bicurico · « **Reply #2140 on:** January 09, 2023, 06:06:19 pm »

Post the result of a df -k
My guess is that the flash is full.

cubitus · « **Reply #2141 on:** January 09, 2023, 06:09:01 pm »

Code: [Select]

/usr/bin/siglent # df -k
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                63152     63152         0 100% /
devtmpfs                 69852         0     69852   0% /dev
none                     78140         4     78136   0% /tmp
ubi1_0                   30388     20864      9524  69% /usr/bin/siglent
ubi2_0                    5848       192      5656   3% /usr/bin/siglent/firmdata0
ubi3_0                    5848        24      5824   0% /usr/bin/siglent/log
ubi0_0                   84752      7784     76968   9% /usr/bin/siglent/usr
/usr/bin/siglent #

Bicurico · « **Reply #2142 on:** January 09, 2023, 09:46:10 pm »

Ask Tautech for a magic file.
It's not the flash being full.

DeDe · « **Reply #2143 on:** January 09, 2023, 10:14:38 pm »

Is the process list complete? I don't see the main application process /usr/bin/siglent/Aladdin?
Please check also the log files in /usr/bin/siglent/usr/logs (debug.log for instance)

You may try to start main application manually (see how it is done in usr/bin/siglent/startup_app.sh):
/usr/bin/siglent/Aladdin &

Additionally please post output of command: dmesg

Quote from: cubitus on January 09, 2023, 03:47:27 pm

Hello
This afternoon we turned on the analyzer the curve was displayed but everything remained frozen... I turned it off and restarted it and since then it remains on a black screen with the logo Siglent to display
I still have access to the ssa3000 via ssh
What do you advise me to do?
SSA 3021 plus transformed into SVA1032 with all enabled options and the latest firmware.

Code: [Select]
/usr/bin/siglent # ps PID USER TIME COMMAND 1 root 0:00 {linuxrc} init 2 root 0:00 [kthreadd] 3 root 0:00 [ksoftirqd/0] 5 root 0:00 [kworker/0:0H] 6 root 0:00 [kworker/u4:0] 7 root 0:00 [rcu_preempt] 8 root 0:00 [rcu_sched] 9 root 0:00 [rcu_bh] 10 root 0:00 [migration/0] 11 root 0:00 [migration/1] 12 root 0:00 [ksoftirqd/1] 13 root 0:00 [kworker/1:0] 14 root 0:00 [kworker/1:0H] 15 root 0:00 [khelper] 16 root 0:00 [kdevtmpfs] 19 root 0:00 [perf] 56 root 0:01 [kworker/1:1] 202 root 0:00 [writeback] 205 root 0:00 [bioset] 207 root 0:00 [kblockd] 238 root 0:00 [edac-poller] 326 root 0:01 [kworker/0:1] 327 root 0:00 [rpciod] 341 root 0:00 [kswapd0] 342 root 0:00 [fsnotify_mark] 343 root 0:00 [nfsiod] 441 root 0:00 [spi0] 455 root 0:00 [spi1] 564 root 0:00 [irq/23-f8007100] 571 root 0:00 [deferwq] 574 root 0:00 [kworker/0:1H] 575 root 0:00 [kworker/1:1H] 582 root 0:00 [ubi_bgt1d] 586 root 0:00 [ubi_bgt2d] 590 root 0:00 [ubi_bgt3d] 594 root 0:00 [ubi_bgt0d] 597 root 0:00 [ubifs_bgt1_0] 600 root 0:00 [ubifs_bgt3_0] 602 root 0:00 [ubifs_bgt0_0] 648 root 0:00 [goodix_wq] 692 root 0:00 telnetd 716 root 0:00 [ci_otg] 730 root 0:00 [kworker/0:2] 739 root 0:00 /usr/bin/siglent/vsftpd 742 1 0:00 portmap 774 root 0:00 [kworker/u4:3] 882 root 0:00 /usr/bin/siglent/vncserver 887 root 0:00 /usr/sbin/lighttpd -f /usr/bin/siglent/lighttpd.conf 888 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini 890 root 0:00 /sbin/getty -L ttyPS0 115200 vt100 894 root 0:00 /usr/bin/php-cgi -c /usr/bin/siglent/php.ini 895 root 0:00 -sh 897 root 0:00 ps

cubitus · « **Reply #2144 on:** January 10, 2023, 08:33:03 am »

Hello and thank you for your help

In the logs, there are almost only warnings, s I did not find anything relevant...
By launching aladdin by hand, the screen appears but this immediately blocks with the error message below.

I also put you the command dmesg

Code: [Select]

/usr/bin/siglent # dmesg
[    0.336218] TCP: reno registered
[    0.336234] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.336264] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.336460] NET: Registered protocol family 1
[    0.336805] RPC: Registered named UNIX socket transport module.
[    0.336818] RPC: Registered udp transport module.
[    0.336827] RPC: Registered tcp transport module.
[    0.336836] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.336867] PCI: CLS 0 bytes, default 64
[    0.337196] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.338540] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.340126] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.341154] io scheduler noop registered
[    0.341174] io scheduler deadline registered
[    0.341231] io scheduler cfq registered (default)
[    0.343272] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.343360] dma-pl330 f8003000.dmac:         DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.343828] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[    0.917296] console [ttyPS0] enabled
[    0.921446] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[    0.928185] [drm] Initialized drm 1.1.0 20060810
[    0.940673] brd: module loaded
[    0.947643] loop: module loaded
[    0.956927] libphy: MACB_mii_bus: probed
[    1.043419] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[    1.053307] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.064867] i2c /dev entries driver
[    1.070148] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[    1.076593] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[    1.083835] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.090051] Xilinx Zynq CpuIdle Driver started
[    1.095137] ledtrig-cpu: registered to indicate activity on CPUs
[    1.102140] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.108452] nand: Micron MT29F2G08ABAEAWP
[    1.112430] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.120023] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.131531] Bad block table found at page 131008, version 0x01
[    1.137807] Bad block table found at page 130944, version 0x01
[    1.143935] 12 ofpart partitions found on MTD device pl353-nand
[    1.149785] Creating 12 MTD partitions on "pl353-nand":
[    1.155041] 0x000000000000-0x000000780000 : "fsbl"
[    1.160857] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.167142] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.173491] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.180156] 0x000001100000-0x000001600000 : "reserved1"
[    1.186367] 0x000001600000-0x000003e00000 : "rootfs"
[    1.192260] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.198384] 0x000004800000-0x000006c00000 : "siglent"
[    1.204412] 0x000006c00000-0x00000d000000 : "datafs"
[    1.210426] 0x00000d000000-0x00000da00000 : "log"
[    1.216087] 0x00000da00000-0x00000f800000 : "upgrade_cramdisk"
[    1.222900] 0x00000f800000-0x000010000000 : "reserved2"
[    1.230968] TCP: cubic registered
[    1.234458] NET: Registered protocol family 17
[    1.239084] Registering SWP/SWPB emulation handler
[    1.245704] rtc-ds1307 0-0068: setting system clock to 2023-01-10 08:53:07 UTC (1673340787)
[    1.259101] cramfs_fill_nand blocks is 320-----------------------
[    1.259101]
[    1.259101]
[    1.259101]
[    1.272121] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.279013] devtmpfs: mounted
[    1.282156] Freeing unused kernel memory: 196K (40553000 - 40584000)
[    1.554972] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[    1.703267] UBI-1: scan_all:scanning is finished
[    1.714262] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[    1.725400] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[    1.732818] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.741476] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.749975] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.758672] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.766427] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.775376] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 27/10, WL threshold: 4096, image sequence number: 1996219743
[    1.786425] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[    1.797314] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 582
[    1.799673] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[    1.843974] UBI-2: scan_all:scanning is finished
[    1.854764] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    1.865756] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[    1.873376] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.881961] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.890504] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.899203] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    1.906857] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.915819] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 158/101, WL threshold: 4096, image sequence number: 1168290863
[    1.927041] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    1.937849] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 586
[    1.944942] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[    1.990185] UBI-3: scan_all:scanning is finished
[    2.000959] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    2.011967] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[    2.019099] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.027668] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.036189] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.044899] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.052534] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.061508] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 16/9, WL threshold: 4096, image sequence number: 479844541
[    2.072388] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.083185] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 590
[    2.085348] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.485725] UBI-0: scan_all:scanning is finished
[    2.497905] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[    2.505374] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.513957] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.522464] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.531179] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[    2.538933] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.547886] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 19/12, WL threshold: 4096, image sequence number: 1984375540
[    2.558932] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[    2.569907] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 594
[    2.583511] UBIFS: background thread "ubifs_bgt1_0" started, PID 597
[    2.615063] UBIFS: recovery needed
[    2.686073] UBIFS: recovery completed
[    2.689742] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[    2.695795] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.704917] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.714577] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.719610] UBIFS: media format: w4/r0 (latest is w4/r0), UUID DFEF06B5-93BD-405D-955B-0D192442F33A, small LPT model
[    2.785946] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.792670] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.801829] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.811213] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.816263] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 89BA13B0-5EF6-4E0F-BE2E-B95726632087, small LPT model
[    2.830634] UBIFS: background thread "ubifs_bgt3_0" started, PID 600
[    2.862228] UBIFS: recovery needed
[    2.884958] UBIFS: recovery completed
[    2.888634] UBIFS: mounted UBI device 3, volume 0, name "log"
[    2.894332] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.903463] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.912839] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.917903] UBIFS: media format: w4/r0 (latest is w4/r0), UUID DBC2ADDB-2E45-46BE-8553-F5AEAB2F89BD, small LPT model
[    2.931544] UBIFS: background thread "ubifs_bgt0_0" started, PID 602
[    2.963172] UBIFS: recovery needed
[    3.044372] UBIFS: recovery completed
[    3.048042] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.054006] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.063119] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.072786] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.077836] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 27A2060B-95C4-4CE0-ACBD-280A13E9C15D, small LPT model
[    5.516861] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f2e380
[    5.542077] irq = 170
[    5.553152] <<-GTP-INFO->> GTP driver installing...
[    5.558186] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[    5.564081] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[    5.570124] <<-GTP-INFO->> GTP I2C Address: 0x14
[    5.574775] 0-0014 supply vdd_ana not found, using dummy regulator
[    5.580961] 0-0014 supply vcc_i2c not found, using dummy regulator
[    5.587265] <<-GTP-INFO->> Guitar reset
[    5.713798] <<-GTP-INFO->> IC Version: 928_1060
[    5.724470] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[    5.743323] <<-GTP-INFO->> create proc entry gt9xx_config success
[    5.749597] input: goodix-ts as /devices/virtual/input/input0
[    5.755587] <<-GTP-INFO->> GTP works in interrupt mode.
[    5.771618] gpib_usb_init
[    5.774381] usbcore: registered new interface driver usb-gpib
[    7.043496] macb e000b000.ethernet eth0: link up (100/Full)
[   10.602623] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   10.621906] ehci-pci: EHCI PCI platform driver
[   10.680048] e0002000.usb supply vbus not found, using dummy regulator
[   10.687358] ci_hdrc ci_hdrc.0: ChipIdea HDRC found, lpm: 0; cap: 4abfc100 op: 4abfc140
[   10.687380] ci_hdrc ci_hdrc.0: It is OTG capable controller
[   10.687400] ci_hdrc ci_hdrc.0: EHCI Host Controller
[   10.692233] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[   10.723343] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[   10.728863] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   10.735636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   10.742817] usb usb1: Product: EHCI Host Controller
[   10.747704] usb usb1: Manufacturer: Linux 3.19.2-omg-xilinx-svn35686 ehci_hcd
[   10.754839] usb usb1: SerialNumber: ci_hdrc.0
[   10.760001] hub 1-0:1.0: USB hub found
[   10.763823] hub 1-0:1.0: 1 port detected
[   10.768426] e0003000.usb supply vbus not found, using dummy regulator
[   10.775198] ci_hdrc ci_hdrc.1: ChipIdea HDRC found, lpm: 0; cap: 4abfe100 op: 4abfe140
[   10.775220] ci_hdrc ci_hdrc.1: It is OTG capable controller
[   10.831060] usbcore: registered new interface driver usb-storage
[   10.859701] usbcore: registered new interface driver usbhid
[   10.868287] usbhid: USB HID core driver
[   10.882227] mousedev: PS/2 mouse device common for all mice
[   12.540768] random: Aladdin urandom read with 21 bits of entropy available
[   12.892722] spidev spi1.1: setup: unsupported mode bits 60
[   13.036710] UBIFS: background thread "ubifs_bgt2_0" started, PID 756
[   13.080274] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.121244] UBIFS: background thread "ubifs_bgt2_0" started, PID 761
[   13.159043] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.177131] UBIFS: background thread "ubifs_bgt2_0" started, PID 778
[   13.221521] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.240604] UBIFS: background thread "ubifs_bgt2_0" started, PID 788
[   13.250671] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.265515] UBIFS: background thread "ubifs_bgt2_0" started, PID 794
[   13.293002] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.309112] UBIFS: background thread "ubifs_bgt2_0" started, PID 808
[   13.327784] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.351298] UBIFS: background thread "ubifs_bgt2_0" started, PID 813
[   13.366858] UBIFS: background thread "ubifs_bgt2_0" stops
[   13.822426] <<-GTP-INFO->> System resume.
[   13.822437] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[   13.833489] <<-GTP-INFO->> GTP wakeup sleep.
[   13.833498] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[   13.962236] UBIFS: background thread "ubifs_bgt2_0" started, PID 825
[   13.999042] UBIFS: background thread "ubifs_bgt2_0" stops
[   14.033277] UBIFS: background thread "ubifs_bgt2_0" started, PID 830
[   14.048697] UBIFS: background thread "ubifs_bgt2_0" stops
[   14.337720] UBIFS: background thread "ubifs_bgt2_0" started, PID 837
[   14.369317] UBIFS: background thread "ubifs_bgt2_0" stops
[   16.548160] UBIFS: background thread "ubifs_bgt2_0" started, PID 844
[   16.576941] UBIFS: background thread "ubifs_bgt2_0" stops
[   22.610170] input: PolyVision Touch Screen as /devices/virtual/input/input1
[  137.330684] random: nonblocking pool is initialized

Bicurico · « **Reply #2145 on:** January 10, 2023, 08:48:56 am »

Send a message to Tauchtech asking for help. I already told you to do that...

cubitus · « **Reply #2146 on:** January 10, 2023, 09:03:04 am »

It's done

tautech · « **Reply #2147 on:** January 10, 2023, 09:17:18 am »

Quote from: cubitus on January 10, 2023, 09:03:04 am

It's done

Sorry don’t have the correct tools.
Contact mailto:info-eu@siglent.com

cubitus · « **Reply #2148 on:** January 10, 2023, 10:17:51 am »

How am I going to shoot this?
Hello Siglent, I bought an SSA3021+, I tinkered with it in SVA1032, it is down what can you do for me?

Won't there be something to try before? Do a full reset?

tv84 · « **Reply #2149 on:** January 10, 2023, 10:51:23 am »

Try to reinstall the latest SVA FW again. Can you do it from the boot sequence?


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers (Read 630442 times)

Share me