Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[1793997762]

I'm very sorry for turning the SSA3015x plus device into a brick
1. I am modifying startup_ During app. sh, due to my lack of understanding of the VI editor and how to exit, some statements in this file may have been mistakenly deleted
2. The device is currently unable to start normally and seems unable to send commands through uart
Below is the log. I hope someone can help analyze and provide a solution. Thank you

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:  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 06d13ec2 ... 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.000478] Console: colour dummy device 80x30
[    0.000497] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090269] pid_max: default: 32768 minimum: 301
[    0.090419] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090435] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091060] CPU: Testing write buffer coherency: ok
[    0.091254] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.091321] Setting up static identity map for 0x39c880 - 0x39c8d8
[    0.240256] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.240334] Brought up 2 CPUs
[    0.240353] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[    0.240362] CPU: All CPU(s) started in SVC mode.
[    0.240864] devtmpfs: initialized
[    0.241588] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.247222] NET: Registered protocol family 16
[    0.249126] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.271078] cpuidle: using governor ladder
[    0.301040] cpuidle: using governor menu
[    0.309307] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.309323] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.309451] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[    0.320136] vgaarb: loaded
[    0.320546] SCSI subsystem initialized
[    0.320929] usbcore: registered new interface driver usbfs
[    0.321043] usbcore: registered new interface driver hub
[    0.321154] usbcore: registered new device driver usb
[    0.321298] phy0 supply vcc not found, using dummy regulator
[    0.321385] phy1 supply vcc not found, using dummy regulator
[    0.321516] --------------usb_udc_init ------
[    0.321762] pps_core: LinuxPPS API ver. 1 registered
[    0.321775] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.321823] PTP clock support registered
[    0.321960] EDAC MC: Ver: 3.0.0
[    0.323480] Switched to clocksource arm_global_timer
[    0.335236] NET: Registered protocol family 2
[    0.335962] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.336012] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.336070] TCP: Hash tables configured (established 2048 bind 2048)
[    0.336117] TCP: reno registered
[    0.336134] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.336164] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.336356] NET: Registered protocol family 1
[    0.336669] RPC: Registered named UNIX socket transport module.
[    0.336682] RPC: Registered udp transport module.
[    0.336691] RPC: Registered tcp transport module.
[    0.336699] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.337069] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.338408] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.339989] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.341002] io scheduler noop registered
[    0.341022] io scheduler deadline registered
[    0.341074] io scheduler cfq registered (default)
[    0.343097] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.343117] dma-pl330 f8003000.dmac:         DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.343643] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[    0.916938] console [ttyPS0] enabled
[    0.921086] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[    0.927835] [drm] Initialized drm 1.1.0 20060810
[    0.940232] brd: module loaded
[    0.947231] loop: module loaded
[    0.955892] libphy: MACB_mii_bus: probed
[    1.033613] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[    1.043513] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[    1.055057] i2c /dev entries driver
[    1.060263] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[    1.066709] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[    1.074050] zynq-edac f8006000.memory-controller: ecc not enabled
[    1.080258] Xilinx Zynq CpuIdle Driver started
[    1.085299] ledtrig-cpu: registered to indicate activity on CPUs
[    1.092294] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.098601] nand: Micron MT29F2G08ABAEAWP
[    1.102579] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.110172] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.121677] Bad block table found at page 131008, version 0x01
[    1.127948] Bad block table found at page 130944, version 0x01
[    1.134081] 11 ofpart partitions found on MTD device pl353-nand
[    1.139926] Creating 11 MTD partitions on "pl353-nand":
[    1.145182] 0x000000000000-0x000000780000 : "fsbl"
[    1.151008] 0x000000780000-0x000000b80000 : "kerneldata"
[    1.157266] 0x000000b80000-0x000000c00000 : "device-tree"
[    1.163604] 0x000000c00000-0x000001100000 : "Manufacturedata"
[    1.170305] 0x000001100000-0x000001600000 : "reserved1"
[    1.176506] 0x000001600000-0x000003e00000 : "rootfs"
[    1.182404] 0x000003e00000-0x000004800000 : "firmdata0"
[    1.188538] 0x000004800000-0x000006c00000 : "siglent"
[    1.194590] 0x000006c00000-0x00000d000000 : "datafs"
[    1.200596] 0x00000d000000-0x00000da00000 : "log"
[    1.206281] 0x00000da00000-0x000010000000 : "upgrade_cramdisk"
[    1.215007] TCP: cubic registered
[    1.218252] NET: Registered protocol family 17
[    1.222928] Registering SWP/SWPB emulation handler
[    1.229657] rtc-ds1307 0-0068: setting system clock to 2023-08-07 22:53:36 UTC (1691448816)
[    1.242999] cramfs_fill_nand blocks is 320-----------------------
[    1.242999]
[    1.242999]
[    1.242999]
[    1.256080] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[    1.262946] devtmpfs: mounted
[    1.266201] Freeing unused kernel memory: 196K (40553000 - 40584000)
Starting rcS...
[    1.538880] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[    1.686996] UBI-1: scan_all:scanning is finished
[    1.697972] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[    1.709111] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[    1.716574] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.725157] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.733681] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.742365] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.750137] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.759085] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 8/3, WL threshold: 4096, image sequence number: 995858657
[    1.769873] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[    1.780762] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 574
[    1.783121] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[    1.827346] UBI-2: scan_all:scanning is finished
[    1.838131] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    1.849161] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[    1.856782] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.865381] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.873904] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.882592] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    1.890260] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.899221] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 15/8, WL threshold: 4096, image sequence number: 725220286
[    1.910112] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    1.920900] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 578
[    1.923042] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[    1.967465] UBI-3: scan_all:scanning is finished
[    1.978241] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[    1.989273] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[    1.996378] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.004979] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.013529] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.022184] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.029858] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.038815] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL threshold: 4096, image sequence number: 898190011
[    2.049614] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[    2.060415] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 582
[    2.062554] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[    2.462347] UBI-0: scan_all:scanning is finished
[    2.474547] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[    2.481963] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    2.490595] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    2.499112] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[    2.507811] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[    2.515561] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.524518] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 8/5, WL threshold: 4096, image sequence number: 1537676743
[    2.535392] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[    2.546367] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 586
[    2.566280] UBIFS: background thread "ubifs_bgt1_0" started, PID 589
[    2.597836] UBIFS: recovery needed
[    2.661972] UBIFS: recovery completed
[    2.665669] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[    2.671692] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.680846] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[    2.690493] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.695544] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 5C5CCD6E-B776-45EE-88E7-DEEF45ABC232, small LPT model
[    2.776996] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[    2.783746] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.792858] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.802265] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.807313] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 28B4FA39-A856-4B39-8D0F-996D0C2183E7, small LPT model
[    2.820914] UBIFS: background thread "ubifs_bgt3_0" started, PID 592
[    2.852470] UBIFS: recovery needed
[    2.875155] UBIFS: recovery completed
[    2.878818] UBIFS: mounted UBI device 3, volume 0, name "log"
[    2.884514] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.893644] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[    2.903022] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.908084] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 13FF4DCA-F17A-42CE-A91A-1BCF38124B00, small LPT model
[    2.921465] UBIFS: background thread "ubifs_bgt0_0" started, PID 594
[    2.952971] UBIFS: recovery needed
[    3.027173] UBIFS: recovery completed
[    3.030841] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.036831] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.045954] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.055582] UBIFS: reserved for root: 0 bytes (0 KiB)
[    3.060621] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 3535A866-5122-4B8D-B7B9-F062E23F9C13, 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.506012] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f65380
Bus error
[    5.531517] irq = 170
[    5.542155] <<-GTP-INFO->> GTP driver installing...
[    5.547193] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[    5.553042] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[    5.559169] <<-GTP-INFO->> GTP I2C Address: 0x14
[    5.563875] 0-0014 supply vdd_ana not found, using dummy regulator
[    5.570030] 0-0014 supply vcc_i2c not found, using dummy regulator
[    5.576239] <<-GTP-INFO->> Guitar reset
[    5.703956] <<-GTP-INFO->> IC Version: 928_1060
[    5.714378] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[    5.733499] <<-GTP-INFO->> create proc entry gt9xx_config success
[    5.739770] input: goodix-ts as /devices/virtual/input/input0
[    5.745771] <<-GTP-INFO->> GTP works in interrupt mode.
[    5.761546] gpib_usb_init
[    5.764309] usbcore: registered new interface driver usb-gpib
/bin/sh: can't access tty; job control turned off
/usr/bin/siglent #


[yuhar]

Hi,

I had some basic questions:

this Siglent Spectrum Analyzers have around -160dBm DANL

maximum input level +30dBm

dinamic range: 90dBm only

where is the rest 100dBm?
It's all taken up by harmonic distortion?
- Tell me I'm wrong. 

[DL4JY]

- Tell me I'm wrong. 

in short, yes.

+30dBM is the max which the SA under certain conditions will survive. (no preamp - and Internal att set to 20+ dB)
 
- 160 dBm is with preamp on.

Preamp is making no real sense if looking at an intermodulation free range.

Therefore, I would assume 0 to - 130dBm is the max overall range (if you look at the datasheet) - from this are possibly 40 db eaten by intermodulation. If you are really take care and have an external attenuator to see what is internal and what is external intermodulation, you might be lucky to have even a higher usefull range for your intermodulation measurements.

90 db is good for this price range.

[genugeo85]

Hello!
I have a Siglent SSA3021X with the data in the photo.
Is it possible to upgrade it to 3.2GHz and switch to permanent all options with firmware 2.1.1.1?
Thanks!

[genugeo85]

Let me ask the question differently...
Is it possible to downgrade to a previous version of the software to solve the problems stated above?

[DL4JY]

did you try the online python script? this is probably all you need . No downgrade required.

[tomud]

did you try the online python script? this is probably all you need . No downgrade required.

so exactly you only need to use the script. The link to the script is given here:

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4355635/#msg4355635

In the case of the SSA3000X model (without plus), remove the comment as in the given screennshoot, enter your HOSTID instead of zeros and press the Execute button to generate codes for the required options.

[genugeo85]

Thank you very much for the information!

[Hitero]

Saturday, Amazon box shoved up by my door. Inside, loose and floating SSA3021X wrapped only in brown paper!? Power on OK. SW1: 2.1.1.3R1, SW2: 20211011-1001, SW3: 000 000D4, HW: 00.00.00. Is it possible to upgrade to SSA3032X without spending hard earned ducats? If yes could someone please point to the right Post# to start reading the process? Thanks

[killingtime]

Is it possible to upgrade to SSA3032X without spending hard earned ducats? If yes could someone please point to the right Post# to start reading the process? Thanks

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4399834/#msg4399834

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4462780/#msg4462780

Generate the keys.
Enter them in the normal way as you would any key purchased from Siglent.
The 'ALL' option gave me BW to 3.2GHz.
Reboot.
That's it. No need to downgrade, cross flash, mess with firmware, telnet over tcp/ip ...

[Hitero]

great, thank you!
didn't load the ALL key
just the AMK, EMI and the 3032. Now 3.2GHz full span
tried the Refl key 2x; is invalid for some reason
I will try the key re-gen later. happy for now
thank you again

[807]

great, thank you!
didn't load the ALL key
just the AMK, EMI and the 3032. Now 3.2GHz full span
tried the Refl key 2x; is invalid for some reason
I will try the key re-gen later. happy for now
thank you again

You need to change Refl to CAT in the script.

[tomud]

great, thank you!
didn't load the ALL key
just the AMK, EMI and the 3032. Now 3.2GHz full span
tried the Refl key 2x; is invalid for some reason
I will try the key re-gen later. happy for now
thank you again

You need to change Refl to CAT in the script.

I've updated the script in my post just in case:

https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4355635/#msg4355635

[807]

You have added the comment:-
"If there is a problem with AMK and Refl licenses, use CAT for AMK and Meas for Refl"

Shouldn't that be "...use CAT for Refl"?

[tomud]

You have added the comment:-
"If there is a problem with AMK and Refl licenses, use CAT for AMK and Meas for Refl"

Shouldn't that be "...use CAT for Refl"?

I did as it says in this post:


https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4400242/#msg4400242

Jepp, the mistake he made was the option.
# Options:
# CAT  = AMK
# Meas = Refl
For AMK he must use CAT as an option also for Refl he must use Meas as an Option.

If he take this options everything is fine.

regards Chris

Although it might be worth tidying up what options work on what devices and firmware versions to make the script more user-friendly. Unfortunately, I hacked my device a long time ago and apparently it has changed a bit in that time. So I don't have full knowledge and it's based on what people describe in this topic.

[807]

It was tv84 who told me to use CAT for Refl in the hacking thread:-

https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg4834964/#msg4834964

Is it possible that both CAT and Meas will work?

CAT worked for me.

[tv84]

Meas is AMK ! 

[Hitero]

CAT for Refl -> Valid: Permanent
Thank you!

[lty1993]

I received my SHA800A today and conducted some reverse engineering on the software. It seems that the software is based on the SSA5000A software, which suggests that the hardware is likely similar. It probably doesn't share the same design as the SVX1000X.

[tautech]

I received my SHA800A today and conducted some reverse engineering on the software. It seems that the software is based on the SSA5000A software, which suggests that the hardware is likely similar. It probably doesn't share the same design as the SVX1000X.

SHA800A thread here:
https://www.eevblog.com/forum/testgear/siglent-sha800a/

What firmware version do you have installed ?

[genugeo85]

Hello!
Thanks again for your help!
I managed to generate the key with the online key generator made available by the master @tomud, I entered them and everything is ok.
I also entered the VNA option and the key was validated.
Question: can this option be used on my SIGLENT and if so, how?

[Bicurico]

The VNA option is for SVA series.

A SSA like yours cannot be converted into a SVA. You need a SSA+ for that.

You already have all activated. Nothing more to do.

[genugeo85]

Ok, thanks!

[tautech]

New firmware for SSA3000X models (not X Plus)

Version： V2.1.1.4
29.3MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3000X_V2.1.1.4_EN.zip

Release notes
Notice:
This firmware must be upgraded from v2.1.1.1 or later. If your analyzer has an earlier version, don’t use this FW to update.

Solved Issues:
• Fix the problem that the bandwidth of the emi filter in SA mode
• Fix the problem that setting the TG Level in SA mode may cause TG to have no output
• Fix the problem that the n dB Marker measurement results in SA mode are inconsistent with the OBW measurement results
• Fix the problem that there is an invalid frequency menu in Harmonic in SA mode
• Fix an issue where 'micro' relative units represented by 'u' were not recognized when reading files

[Bicurico]

Notice:
This firmware must be upgraded from v2.1.1.1 or later. If your analyzer has an earlier version, don’t
use this FW to update.

Most users have the "old" version that does not use the unified platform FW. Do NOT try to upgrade with this FW, you will probably just brick your device.

I looked at the package and the upgrade seems pretty inoffensive, at least it does not seem to remove any telnet access...

Because this is the unified platform FW, it includes VNC. I wonder if this can be used on the SSA3000X v2 model? Does this model include a touch screen? Also, I wonder if further hacks or even cross-conversions are possible...

From NSP_trends_config_info.xml:

Code: [Select]

<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SSA3075X</product_type_1>
<product_type_2>SSA3050X</product_type_2>
<product_type_3>SSA3032X</product_type_3>
<product_type_4>SSA3021X</product_type_4>
<product_type_5>SSA3015X</product_type_5>
<manufacturer>Siglent</manufacturer>
<Support_Touch_Flag>1</Support_Touch_Flag>
<Support_VXI11_Flag>1</Support_VXI11_Flag>
<file_prefix>CP_</file_prefix>
</device>
</nsp_trends_info_root>