I just got a SSA3021X Plus and right out of the box it is a very nice piece of gear. I'm an EE who is about to retire after over forty years and for much of that time I have been an RF engineer. Since I restore old tube radios and plan to get my amateur station on the air again the thought of life without a spectrum analyzer seemed bleak indeed. Old spectrum analyzers are easily available and often relatively cheap. Nothing wrong with them. But my last few years of doing digital radio work with modern Keysight MXA's has spoiled me, I guess. So I was delighted to find how close to that equipment. Certainly not in the same league but clearly close enough for my purposes. If all I was able to do was to make the trial licenses permanent it would be a great piece of gear.
But the allure of a VNA too is just too much to resist!
I'm a hardware guy who often has to do software installs and adjustments on product code that is not ready for prime time. It's part of the development process and its not like the SW guys don't have to deal with HW that is not ready for prime time! So I have some familiarity with what needs to be done to improve these products but I am close to being a babe in the woods even so. The instructions found here are great and a huge thanks to those of you who are able to figure all this out and are willing to share it with the rest of us!
I followed tv84's direct crossflash procedure,
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3564805/#msg3564805, and it worked first time. Of course it leaves the unit in a partially functional state that is basically useless. And that is why he directs you to point V in electr_peter's latest summary of the process, see the link in tv84's post.
This is my third piece of Siglent test equipment in the last few years and I have always had some difficulty getting my laptop to connect to them via telnet. This time was no different and I had to both start with step IV of electr_peter's procedure and connect through an ethern et router as I had to do on the other products. But once I started doing that the process was straightforward with a couple of minor wrinkles. So some tips for other newbies:
1) I often finished a vi edit only to find that the file was read only. So I found myself needing to repeat the appropriate remount command to make files writeable before every file edit.
2) Several times I found myself lost during vi edits and unsure that I had not overwritten something by accident. If you do that hit esc to make sure you are in vi command mode and then :q! to force vi to quit without saving. Then start the edit process again and be more careful this time!
3) Whether you do the full electr_peter process or start with the tv84 direct crossflash as I did look at the early steps in the electr_peter process and pull up a browser tab with the vi instructions, you will need them.
4) Sometimes the electr_peter instructions tell you to issue the telnet command "sync && reboot" but if you were editing a file in vi just before this you will need to do a :wq command in vi to save your work before you can issue any telnet commands. This is obvious to old hands but it can be confusing to you and I
5) There is a lot of typing involved and it has to be accurate. From windows you can select electr_peter's text with your mouse, hit CNTRL-C to copy, and then paste the commands into your telnet window by hitting the right mouse button.
6) I got a command not found error when I tried to start the telnet link. Do a web search on telnet for windows to get instructions on how to fix this
That may seem like a lot of issues to solve but they were all easily solved and hopefully my comments will help those of you who have trouble with any of these points. In the end it is pretty simple and oddly satisfying even though you are just parroting the fine work of others. Thanks again to all of you who made this possible!