Hello comrades!
I have acquired
SSA3021X-Plus SW1: 3.2.2.6.0R1
SW2: 20221117-1301
SW3: 000000D4
HW: 01.00.00I want to update it to
SSA3032X-PlusThe site has the latest firmware:
SSA3000X Plus_Firmware_V3.2.2.6.0R7 (Release Date 06.09.23 )What is the hacking procedure?
I have to upgrade to the firmware first
3.2.2.6.0R7 ?
Reading the topic, I realized that I had to do the following:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg35635771) Initial backup of SSA3021X Plus1.1. Turn on SSA, put USB stick (FAT32) with
SSA3000X+_backup_11411.ADS in the front USB port on SSA
1.2. Navigate to USB directory, select
*.ADS via
File -
Open/Load and press
Enter1.3. Wait until device reboots itself, then turn off, eject USB flash
and copy backup files to PC. Total backup size is ~483MB
https://tis.kz/temp/Siglent/SSA3000X+_backup_NAND+mem+firmdata0_11411.zip2) Telnet access for SSA3021X Plus & Manual backup2.1. Connect Ethernet cable to SSA3021X and network, configure IP (DHCP option recommended)
2.2. Internal product ID should be 11411. Launch fake update
SSA3000X+_telnet_11411.ADS from USB stick to start telnet. SSA hangs with update screen, that's normal.
2.3. Open telnet,
telnet <SSA IP address> 10101 2.4. Backup main directories:
cd /
cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent/usr/mass_storage/U-disk0/SA-backup
cp -R /usr/bin/siglent/usr/config /usr/bin/siglent/usr/mass_storage/U-disk0/SA-config
cp -R /usr/bin/siglent/firmdata0 /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0
cp -R /usr/bin/siglent/usr/usr /usr/bin/siglent/usr/mass_storage/U-disk0/SA-usr
cp -R /usr/bin/siglent/usr/vnacalikitdata /usr/bin/siglent/usr/mass_storage/U-disk0/SA-vnacalikitdata2.5. Make files writeable:
mount -o remount,rw /usr/bin/siglent and add telnet server startup line in file “/usr/bin/siglent/startup_app.sh” :
vi /usr/bin/siglent/startup_app.sh enter the following line exactly close to the end, just before line "/usr/bin/siglent/Aladdin &" :
/sbin/telnetd -l /bin/sh -p 10101 &2.6. Finalise changes and reboot
sync && reboot After SSA reboots, telnet should be started automatically without fake update via USB.
https://tis.kz/temp/Siglent/SSA3000X+_telnet_11411.zip3) Generating keys to open optionsSummarizing the collected information (Updated August 29, 2023)
In the Python compiler, run the script
The script itself is in the file:
Keygen_for_Siglent_Spectrum_Analyzers.pyIn the
HOSTID = '0000000000000000' field, enter your ID
Removing the comment
# before the line
Model = 'SSA3000X_Plus'https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4355635/#msg4355635https://tis.kz/temp/Siglent/Keygen_for_Siglent_Spectrum_Analyzers.zipAfter compilation, we enter the code from the
ALL field into the SSA
Are options 3021, 3050, 3075 superfluous? Is it better to remove them from the code? What other extra options are not available on the SSA3032X?
Did I get it right?
Why is the CAT field not active in the compilation results?
After entering the code into the SSA device from the
ALL field, will the device model name also change to SSA3032X?
---
At the link below, there is an instruction on renaming files, why rename files?
NSP_sn_bandwidth.xml --> NSP_sn_bandwidthx.xml
NSP_trends_config_info.xml --> NSP_trends_config_infox.xml
nsp_data_b --> nsp_data_bx
https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg1299182/#msg1299182