Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[Bicurico]

The cross flash by itself will not change the device model name. See homework in tv84 previous posts.

Also, feedback is required on modified ADF files since not all of us own the SSA3000X-Plus.

Finally, regarding warranty. Even if the device is not opened and the sticker is intact: once you start hacking your device, the warranty is gone. Modifications will show in FW and any technician will see if the device has been tampered with, unless you restore a full flash backup.

Regards,
Vitor

[Venturi962]

Added telnet line to startup_app.sh, so don't need UART anymore.  Updated the NSP_trends_config_info.xml, model is now SVA1032X.  VNA options show up in the Mode menu.  Waiting on some N connectors, haven't been able to test out any measurements yet.

[RoV]

Interesting...    Maybe some countermeasures have indeed made their way into this latest version.

Can any of you telnet with this file?  (should only work on SSA3021_3032XP_V3.2.2.4.0 or up)

Remember that it's port 10101.

Yes, it works for me (3.2.2.4.0)

Thanks,
Roberto

[RoV]

In a nutshell:

1 - Flash the latest SSA+ FW.
2 - Go in with a telnet .ADS.
3 - Make the FS RW.
4 - Change the ProdID in config/NSP_config_upgrade_info.xml to 11403.
5 - Sync & Reboot
6 - Flash the latest SVA1032X FW.

Hi tv84, am I correct in saying that, having an SSA3021+ with FW 3.2.2.4, I should change ProdID from 11411 to 11410 and not 11403 before upgrading to SVA 3.2.2.4?
Regarding telnet, is it still a good idea to add the line to start the daemon before rebooting to try the update (just in case of problems), or there are side effects? I haven't seen the telnet line cited in recent posts.
Thank you for your excellent work!
Roberto

[sbehnke]

I received my SSA3021X-Plus that shipped with version V3.2.2.4.0 today and everything is working as expected. Thanks!

[RoV]

I received my SSA3021X-Plus that shipped with version V3.2.2.4.0 today and everything is working as expected. Thanks!

... by doing what, exactly? I am in the same situation, but I have only tested telnet by now. Not sure what procedure is best to follow.

[tv84]

Hi tv84, am I correct in saying that, having an SSA3021+ with FW 3.2.2.4, I should change ProdID from 11411 to 11410 and not 11403 before upgrading to SVA 3.2.2.4?

No, you should change to 11403 because SVA v3.2.2.4 will still install over 11403.

Only AFTER SVA 3.2.2.4 is installed, the SVA will begin to accept the 11410 (only).

We are precisely at a transition point and that's the reason why so many confusion is going on.

BEWARE: Nonetheless the upgrade starting from a SSA+ 3.2.2.4 has not been confirmed by anyone AFAIK, without going to UART access. But I suppose it should work unless Siglent made any special arrangements which are yet to be shown clearly.

ALSO: You should add the telnet line whenever possible.  (I haven't been referring to it because I fear many guys can mess up the boot script if they don't know how to edit files in these filesystems.)

[kkessler]

I also successfully upgraded mine, but I had the exact same issues as Venturi962; lost the TG after the SVA firmware upgrade, had to hook up the UART console to get telnet, and then everything worked when I did post 1224.

To try to get telnet working, I'm using the SVA1032X_telnet.ADS dated March 16, 2021, downloaded from the latest post I could find (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3516520/#msg3516520). It just jumps back to the file manager with Update Failed. Since I have the serial console hooked up, I can see the console output, but no errors or logging are shown when I open the ADS file. I don't see any logging in any of the rw filesystems either. If someone can tell me where to look, I try to get some debug info while I have the serial console connected.

I'm going to start the telnet daemon in startup_app.sh, but I did that before I did the SVA flash, and maybe that was a difference which caused the upgrade issue.

[Bicurico]

The cross-upgrades that people have done, cause confusion due to different issues:

1) The Prod-ID is checked by the upgrade routine and you can only upgrade a FW that has the same Prod-ID as the device.
2) The SSA+ and the SVA have different Prod-ID's, which is why the TELNET.ADS needs to match the current Prod-ID. I.e., after crossgrading the SSA+ to SVA, the previously working TELNET.ADS will no longer work, because the Prod-ID changed.
3) A successfull crossgrate will not change the MODEL. The device will still say it's an SSA+.
4) There seem to be different Prod-ID's according with the FW version: the SSA+ and SVA may have different Prod-ID, depending on the current FW version. This is to prevent downgrading!
5) Currently, it is recommended to start with the latest FW on the SSA+ and crossgrade to the lates SVA FW.

Did you successfully corssgrade? Why not post how you did it and which troubles you had? The topic is full of "I successfully cross-grade", but next to zero contributions for others... Only take an no giving back.

Regards,
Vitor

[kkessler]

If you already know that the SVA1032X_telnet.ADS doesn't work because the upgrade changes the Prod ID from 11403 to 11410, I will close up my disconnect my serial and close up my SA because no you don't need any more debug info.

Kevin

[sbehnke]

I followed the instructions from https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3180802/#msg3180802 And it all worked out just fine.

[tv84]

If you already know that the SVA1032X_telnet.ADS doesn't work because the upgrade changes the Prod ID from 11403 to 11410, I will close up my disconnect my serial and close up my SA because no you don't need any more debug info.

Kevin

Horses for courses.

The telnet_11410 is here.

The telnet_11411 is here.

People keep forgetting that after crossflashing the SSA+ to a SVA, the forum thread should change.

[RoV]

I am really happy to say I managed to perform the upgrade from SSA3021X+ FW 3.2.2.4.0 to SVA1032X FW 3.2.2.4.0

Since it took me a couple days to study this discussion thread and the parallel one on the SVA, I copy the procedure I followed, even if I don't have any merit in this: I can only thank specially tv84    for all the work and maximevince  (posts #1223/1224) who made a previous summary, still mostly valid, with a few exceptions with this FW release.

Starting from an SSA3021X-E with FW 3.2.2.4.0
------------------------------------------------------------
connect Ethernet, configure IP (tipically DHCP)
launch update with SSA3000X_Plus_telnet_11411.ads (e.g. reply #1508 of this thread)
enter telnet <SSA address> 10101 (e.g. from Putty on your PC)
backup a few dirs, you never know... (an USB stick must be in)
   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/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-vnacalikitdata
    cp -R /usr/bin/siglent/fimdata0 /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0
make r/w fs
   mount -o remount,rw /usr/bin/siglent
edit file /usr/bin/siglent/startup_app.sh to add telnet server:
   vi /usr/bin/siglent/startup_app.sh
enter the following line close to the end, just before line "/usr/bin/siglent/Aladdin &"
   /sbin/telnetd -l /bin/sh -p 10101 &
edit /usr/bin/siglent/config/NSP_config_upgrade_info.xml to change accepted kind of upgrade:
replace
   <upgrade_static_id>11411</upgrade_static_id>
with
   <upgrade_static_id>11403</upgrade_static_id>
update fs and reboot with:
   sync && reboot
After reboot, check that telnet still works without launching the update
Update with Siglent stock firmware SVA1032X_V3.2.2.4.0.ADS (exactly this version!)
After reboot, launch update with SSA3000X_Plus_telnet_11410.ads (found here: https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3454656/#msg3454656)
enter telnet <SSA address> 10101
repeat add telnet server as above
make r/w other fs
   mount -o remount,rw /usr/bin/siglent/firmdata0
   cd /usr/bin/siglent/firmdata0
in NSP_sn_bandwidth.xml, erase the complete <license> .. </license> part (including <license> </license> lines).
    vi NSP_sn_bandwidth.xml
replace the contents of NSP_trends_config_info.xml with the one attached to reply #1224 (edit differences or replace file)
    vi NSP_trends_config_info.xml
rename two files, one in another directory
    mv nsp_data_b1 nsp_data_b1x   
    cd /usr/bin/siglent/usr/backup   
    mv nsp_data_b nsp_data_bx
update fs and reboot with:
   sync && reboot

Now I have to learn how to install licenses associated to real SN. Any pointer?

Thanks to everyone again,
RoV

[toshas]

Is it possible to use integrated bridge instead of external one (RB3x25) for SWR measurement with SSA3000X-Plus models ?

[tautech]

Is it possible to use integrated bridge instead of external one (RB3x25) for SWR measurement with SSA3000X-Plus models ?

No, not unless you convert the SSA3kX Plus into something else  with a different feature set that allows for single port SWR measurements.
Do some research here and it will all become clear.

[toshas]

Is it possible to use integrated bridge instead of external one (RB3x25) for SWR measurement with SSA3000X-Plus models ?

No, not unless you convert the SSA3kX Plus into something else  with a different feature set that allows for single port SWR measurements.
Do some research here and it will all become clear.

Thanks! It's clear now.

[toshas]

This is a report about one more success cross-flashing.

SSA3021XP (3.2.2.3.2) to SVA1032X conversion script:

I) initial backup (3.2.2.3.2)

1. 8GB empty usb flash drive with FAT32
2. copy SSA3032X+_backup.ADS from SSA3032X+_backup_NAND+mem+firmdata0.zip to usb flash
3. turn on SSA3021XP
4. put usb flash drive in the front usb port
5. go to system - system info - fw upgrade - open - "enter"
6. wait until device reboot to normal state again
7. turn off, eject usb flash and copy files to safe place

*backup size is ~416MB

II) flash to "safe" 3.2.2.3.3R1 fw

8. erase flash content, copy SSA3021_3032XP_V3.2.2.3.3R1.ADS from SSA3021_3032XP_V3.2.2.3.3R1_EN.zip to usb flash
9. turn on SSA3021XP
10. put usb flash drive in the front usb port
11. go to system - system info - fw upgrade - open - "enter"
12. wait until device reboot to normal state again
13. turn off, eject usb flash

III) backup before cross (3.2.2.3.3R1)

14. erase flash content, copy SSA3032X+_backup.ADS from SSA3032X+_backup_NAND+mem+firmdata0.zip to usb flash
15. turn on SSA3021XP
16. put usb flash drive in the front usb port
17. go to system - system info - fw upgrade - open - "enter"
18. wait until device reboot to normal state again
19. turn off, eject usb flash and copy files to safe place

*in my case only second attempt of this step was successful, at first run no files were created on usb flash

IV) cross to SVA1032X part 1

20. erase flash content, copy SSA3000X_Plus_telnet.ADS from SSA3000X_Plus_telnet_port_10101.zip to usb flash
21. connect ethernet cable and turn on SSA3021XP
22. find assigned ip address via system - interface - LAN, ping this ip for test purposes
23. put usb flash drive in the front usb port
24. go to system - system info - fw upgrade - open - "enter"
25. upgrade process will be "infinite", it is ok
26. connect via telnet to SSA3021XP, port is non default - 10101
telnet x.x.x.x 10101
27. remount file system with rw access
mount -o remount,rw /usr/bin/siglent
28. change device ID in NSP_config_upgrade_info.xml ("upgrade_static_id" from 11405 to 11403)
vi /usr/bin/siglent/config/NSP_config_upgrade_info.xml
29. add telnet service to autorun in startup_app.sh
vi /usr/bin/siglent/startup_app.sh
add this line just before "/usr/bin/siglent/Aladdin &" line
/sbin/telnetd -l /bin/sh -p 10101 &
30. sync fs and reboot
sync && reboot

*ecomb/ecomb_p/Aladdin renaming is not needed for 3.2.2.3.3R1 fw
*telnet will be available after reboot without running SSA3000X_Plus_telnet.ADS again
*for file editing use linux or virtual machine with linux otherwise carriage return symbols can be incorrect

V) cross to SVA1032X part 2

31. erase flash content, copy SVA1032X_V3.2.2.3.3R1.ADS from SVA1032X_V3.2.2.3.3R1_EN.zip to usb flash
32. put usb flash drive in the front usb port
33. go to system - system info - fw upgrade - open - "enter"
34. wait until device reboot to normal state again

now device will have SSA3032XP name with span 2.1GHz and new modes will be inactive (VNA) but it is true SVA1032X
*use 3.2.2.3.3R1 fw version when crossing !

VI) backup after cross (3.2.2.3.3R1)

35. erase flash content, copy SVA1032X_backup.ADS from SVA1032X_backup_NAND+mem+firmdata0.zip to usb flash
36. put usb flash drive in the front usb port
37. go to system - system info - fw upgrade - open - "enter"
38. wait until device reboot to normal state again
39. turn off, eject usb flash and copy files to safe place

VII) re-enable telnet

40. erase flash content, copy SVA1032X_telnet.ADS from SVA1032X_telnet_port_10101.zip to usb flash
41. connect ethernet cable and turn on SVA1032X
42. find assigned ip address via system - interface - LAN, ping this ip for test purposes
43. put usb flash drive in the front usb port
44. go to system - system info - fw upgrade - open - "enter"
45. upgrade process will be "infinite", it is ok
46. connect via telnet to SVA1032X, port is non default - 10101
telnet x.x.x.x 10101
47. remount file system with rw access
mount -o remount,rw /usr/bin/siglent
48. add telnet service to autorun in startup_app.sh
vi /usr/bin/siglent/startup_app.sh
add this line just before "/usr/bin/siglent/Aladdin &" line
/sbin/telnetd -l /bin/sh -p 10101 &
49. sync fs and reboot
sync && reboot

*telnet will be available after reboot without running SVA1032X_telnet.ADS again
*for file editing use linux or virtual machine with linux otherwise carriage return symbols can be incorrect

VIII) apply bw and vna options

50. there are two ways - "pro" mode (according #1224) and "secret sauce" which is not public


p.s. this will work till 3.2.2.3.3R1 (including), 3.2.2.4.0 requires another telnet scripts, check posts above

Links to firmwares:
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021_3032XP_V3.2.2.3.3R1_EN.zip
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SVA1032X_V3.2.2.3.3R1_EN.zip

All used scripts are attached, they are not mine, just collected through reading related thread here from cover to cover.

Special thanks to @tv84 @noreply @maximevince @Bicurico

[hpw]

Use currently the latest EasySpectrum V1.0.6.1 as given to download and on the Res BW as Video BW, the drop down goes only now to to 10Hz as on gear easy to setup 1Hz possible..

Have a 100Hz Span and do not know why it gets 3Hz RBW & VBW..

Any know issue about this limitation, nice is the 3D view but without 1Hz RBW no beef  ?

Hp

[hostile]

I am still a little confused.  I have a new ssa 3021x plus with firmware 3.2.2.4.0
I have tried putting on a flash drive ssa3000x_plus_11411.ads, ssa3000x_plus_telnet.ads, and the the SSA3032X+_backup.ADS.
When I try running any of these is just waits for a while doing the hour glass then drops back to the upgrade file explore window.
Do you know have to open it up to get access to telnet ?
I was hoping it was able to do it over ethernet.
Sorry if it has already been covered, I read through the entire thread but still a little confused and not wanting to brick my nice unit. 

[tv84]

Change USB disk.

[hostile]

Change USB disk.

I have tried 4 different usb sticks. I will have to order some more.  I do not have an 8G as I see a lot of people using.  tried 16G, 32G and a 64G.  I can try to order some more

[Bicurico]

Try to partition and format your USB disk to a 2gb FAT32 partition. No need to buy a new disk.

[hostile]

Try to partition and format your USB disk to a 2gb FAT32 partition. No need to buy a new disk.

I took the 16G sandisk and made a 2G partition as fat32.  I re-formated it without quick format enabled.  tried running the SSA3032X+_backup.ADS on the ssa3021x plus.  same thing,  ran for about 30 seconds and drops back to file selection window.   Can this thing really be that picky about usb sticks or am I missing something. 

[Bicurico]

Can you write the screenshot to that USB stick?

Anyway, I think you have a totally different issue.

The SSA3000+ will have different HostID according to installed FW. You can only used the fake update if you are currently on the compatible FW. Otherwise the HostID does not match and the upgrade is refused.

[hostile]

Can you write the screenshot to that USB stick?

Anyway, I think you have a totally different issue.

The SSA3000+ will have different HostID according to installed FW. You can only used the fake update if you are currently on the compatible FW. Otherwise the HostID does not match and the upgrade is refused.

I am able save a screenshot to the usb. 
I thought others were successful in running the fake updates with sw1:3.2.2.4.0 ?
what is the SW2 number signify ? looks like a date. 
Let me know if the hostid is needed