I can tell you that I performed the changes per this post (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577) and nothing else and it was painless. Perhaps start over and go through that list.
That is exactly what I did, with several exceptions: I did not modify NSP_config_upgrade_info.xml to change the product ID's, since I had already crossflashed to the sva1032x, and even after mount -o remount,rw /usr/bin/siglent/firmdata0, I had to add write permission chmod o=rw NSP_sn_bandwidth.xml in order to modify it. maybe I should change it back to read only. I can't see how that would make any difference, but who knows?
It will not flash back to SSA3021_3032XP_V3.2.2.4.0.ADS so I cannot start over from scratch. I could try reflashing with the factory SVA1032X_V3.2.2.4.0.ADS, maybe something went wrong with the first time. That will likely remove telnet access, so I hope that telnet_11410.ads will get me back in.
Another difference from peter's summary, he says "serial number shows XXXX." however my serial number is shown in the system info screen, and starts with "SSA3....). Maybe I should change it to XXXX
Does anyone have a better idea?
update: I found a solution. I deleted /usr/bin/siglent/firmdata0/nsp_data_b1 once more, then sync && reboot. Voila! All options enabled and now the serial number shows as XXXXX. I do not know what happened the first time around. After my changes, I entered sync, but then cycled the power from the front panel. This time, I did sync && reboot. That is the only thing I can think of.
Many thanks to all who unlocked this gem! The built-in directional bridge works well over the full 3.2 Ghz band. After calibration, measuring S11 of a 20 dB pad reads 40 db return loss, just as it should. Clearly my unit has the internal reference cable that was missing on some units.
I too followed electr_peter's great instructions sort of(see below). But like dirtcooker ended up with the same problem of nsp_data_b1 not being deleted. Looking back at my terminal log, the first rename in part V step 5 in the firmdata0 directory
mv nsp_data_b1 nsp_data_b1x
caused a read only message I responded y to but result was a renamed copy and the original still there. Turns out I had previously done an incorrect copy paste of
mount -o remount,rw /usr/bin/siglent
in step 3 instead of
mount -o remount,rw /usr/bin/siglent/firmdata0
Then I had difficulty deleting the file as it kept reappearing. The solution was to use top to find the process number of the Aladdin process, kill it, do the correct mount remount, then rm nsp_data_b1, then sync, reboot... SUCCESS! YA!
To help others who might travel this path, I did this on macOS Catalina. I could not get telnet or PuTTy to work from MacPorts or Brew so I tried to use the Apple sanctioned nc as the secure telnet replacement. Unfortunately nc and vi don't get along too good. I tested vi by making a new file on the SA as in vi crap. The problem is that the Esc key doesn't work to get back to command mode in vi! So if you open a file you can't close it! Had to apple-c which closed the telnet session. Googling found many questions but no correct answers. Experimenting found that whenever an esc is needed esc followed immediately with ctrl-d works. So to get out esc ctrl-d :q! Also all the command sequences and escapes end up all over the screen as it doesn't do telnet screen emulation(just the display, not the file). Even moving the arrows requires the escape sequence and leaves artifacts. Not really what you want to play with for something critical. Perhaps nc could be setup to work correctly but I ended up coping all the files needing editing to the desktop and editing with BBedit, although TextEdit would have done.
So the bottom line is follow
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3563577/#msg3563577 exactly, including using a proper telnet emulator.
Oh, thanks tv84, electr_peter, all the early nurds and brave testers and 'Linux for Dummies'! I'm a linux geek soon to be a rf geek!
They keep forgetting the that everyone is a linux geek until access is lost (in a sealed machine)...
Quote of the month....
Edit: Got PuTTy to work on macOS. Reinstalled XQuartz and all was good.