Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[Elasia]

The uImage file to reflash that portion with can be extracted from any of their firmware files

This one is from 2.2.1.2.5

[tv84]

So, the contents of MTD1 (kernel) is the uImage file that Elasia shared.

You go in uboot and flash that file in the MTD1 address.

That will solve the Kernel problem. Then send the boot log to see how it ends.

[Elasia]

So, the contents of MTD1 (kernel) is the uImage file that Elasia shared.

You go in uboot and flash that file in the MTD1 address.

That will solve the Kernel problem. Then send the boot log to see how it ends.

I suspect that will take care of it.. as the fact that its corrupt should mean he either stopped it or it crashed mid flash of that partition and the others should be ok

Then if his program partition is full that can be easily fixed up with some basic clean up like i had to do

[Precut]

Here are 2 ZIPs with the stock firmwares of both SVA and SSA (latest versions).  I unpacked the .ADS files for you.

Below is the NAND map of the SSA X+:
(Attachment Link)

Study the stuff.

(Maybe you can ask someone to send you their NAND dump and you flash the necessary MTDs.)

Everything works like a charm. Big thumb up to you!

[Precut]

So, the contents of MTD1 (kernel) is the uImage file that Elasia shared.

You go in uboot and flash that file in the MTD1 address.

That will solve the Kernel problem. Then send the boot log to see how it ends.

I suspect that will take care of it.. as the fact that its corrupt should mean he either stopped it or it crashed mid flash of that partition and the others should be ok

Then if his program partition is full that can be easily fixed up with some basic clean up like i had to do

Yes, it boots normally after flashing MTD1. 

[Elasia]

Good job, glad to hear

[tv84]

Everything works like a charm. Big thumb up to you!

You owe us a beer!   

Now, go slowly and do the crossflash as required.   

[TurboTom]

Beforehand, it would be a good idea to back up all the FLASH partitions, especially the firmdata0 one since it contains the calibration data. After that, you can commence much more relaxed withe the task of "improving" your instrument... 

[Precut]

Everything works like a charm. Big thumb up to you!

You owe us a beer!   

Now, go slowly and do the crossflash as required.   

Certainly 

BTW, after uboot loading the kernel image, login is needed. blank user name and password do not play trick here... any hints?

[Precut]

wanna find a "untouched" version of rootfs.cramfs to flash/reset mtd5 partition in my ssa. does it come with FW?  Thx

[Precut]

Just update my progress. After several rounds of trials, my SSA eventually becomes a 3.2GHz band of SSA and SVA hybrid. Many thanks to tv84, elasia and folks.

But before the ultimate conversion, my SSA went bricked again. This time is due to missing of some critical files (ecomb_p, vncserver etc) and directories (/usr/bin/siglent/usr/*) under /usr/bin/siglent (mtd7). The kernel was loaded successfully but it stuck in the splash screen. Telnetd did not work as the "Firmware Update" menu could not be reached. Badly, these files were also missing in my mtd7 backup image ...  

Since the filesystem of mtd7 is UBIFS, the only solution came to my mind is to mount the mtd7 backup image on a linux box, and extract the missing files from the stock FW and copy them back to mtd7. After tons of hassles, my SSA becomes functional again.

Interestingly, I didn't rename ecomb_p to ecomb; just did the rename-to-x and licence blocks tricks. Currently, vsftp and udc-xilinx.ko are still missing in my SSA but everything just goes fine.

[tv84]

I think you don't have a reliable setup. You didn't follow the instructions correctly or else you wouldn't be in such troubles.

In order to verify that all is correct, try to upgrade the equipment with the latest stock SVA firmware.

[Precut]

I think you don't have a reliable setup. You didn't follow the instructions correctly or else you wouldn't be in such troubles.

In order to verify that all is correct, try to upgrade the equipment with the latest stock SVA firmware.

I did the firmware update again right after the SSA resumes function. The missing files are still missing however...

[tv84]

Don't call it SSA. Now you should call it SVA.   

The files are not in these latest FWs. You add them manually or will have to wait for a FW that contains that part of the filesystem.

Don't understand why you didn't reflash the whole MTD7 from uboot... 

[Precut]

I did reflash the mtd7 from uboot but the files was still missing. I found these files are also missing in my backup mtd7 image. Don't ask me why.     Indeed, I only backup (not nanddump) the whole filesystem from telnet before trying my first attempt of FW update.

To fix the problem, I had to fix my backup mtd7 image. The simplest solution was to ask you all to share with me an untouched mtd7 image and reflash it. I didn't do so simply because I wanna fix it by myself first.

[tomud]

I did reflash the mtd7 from uboot but the files was still missing. I found these files are also missing in my backup mtd7 image. Don't ask me why.     Indeed, I only backup (not nanddump) the whole filesystem from telnet before trying my first attempt of FW update.

To fix the problem, I had to fix my backup mtd7 image. The simplest solution was to ask you all to share with me an untouched mtd7 image and reflash it. I didn't do so simply because I wanna fix it by myself first.

http://lantech.pl/SSA3000X_Plus/mtd7

[Joel_l]

Does post #963 still work with the latest shipping SSA3021X Plus?

[Precut]

Does post #963 still work with the latest shipping SSA3021X Plus?

Yes, works like a charm. 

P.S.shipped directly from SZ and received it by the end of June.

[Joel_l]

What was the stock firmware version yours shipped with?
Thanks!

Does post #963 still work with the latest shipping SSA3021X Plus?

Yes, works like a charm. 

P.S. My SSA was shipped directly from SZ. I received it by the end of June.

[Precut]

2.2.1.2.7

[MathWizard]

Someday I'll probably be getting 1 of these. If scopes in general have way more features than they did in the 1980s, what all extras are on modern digital SA ?

[brokeit]

So, Long time lurker but first poster. Awesome work going on here!

I'm rather ashamed my first is to ask for help.... but here goes!

Just got my hands on a SSA3021X Plus.

Used SSA3000X_Pluas_telnet.ADS to gain telnet access, no issue.

Followed  post #963, including adding the telnet line. No issues. Had to remount rw to edit the files  and did some syncs (and indeed remounted ro) before I rebooted.

Used reboot on the command line and the box came back up.

Used the system -> firmware update menu to upgraded to SVA1032X_2.2.1.2.5_EN from siglentna.com.

Box reboots, and comes back up, no issues. It did seem to reboot twice, but don't know if thats just a normal part of the upgrade process or not.

Going to System -> System Info I now says it's a SSA3032XPlus ! (Not an SVA!)
SW1 2.2.1.2.5
SW2 20191022-5
SW3 000000D4
HW 00.00.00

Options are all Time limited except TG, which was Permanent out of the box.

Hitting Span full span only goes to 2.1G even though it now thinks it's a SSA3032!

Now the mode button Does include Vector Network Analyzer and Distance To Fault but both of these are greyed out. I'm pretty sure these are not there at all before hand.

The thing that's stopping me dig into this further is that despite adding the telnetd line it didn't come back with telnet working.  The SSA3000X_Plus_telnet.ADS trick no longer works.

Is there anyway I can get back into this without opening up for a serial console ?

I could try repeating the upgrade. Not sure if it would even let me upgrade to the same version?


Shout if I can provide more info.
Thanks!

~
Mike

[tv84]

Going to System -> System Info I now says it's a SSA3032XPlus ! (Not an SVA!)

All is good. The machine is a SVA but shows previous model. No problem there as it has no consequences and I'm not in the mood for photoshop ops.

The procedure that is public doesn't include the licensing of the options.

The telnetd line was a backup plan before the crossflash operation. After you finish crossflash, that script is replaced by the stock one.

You have changed the equipment to SVA so, now, you must use the telnet script for a SVA machine.

[brokeit]

Hi tv84,

Thanks for the pointer, I'm back in the console.

I must have misunderstood, I thought the 3GHz span was a done deal on the pluses. Kind of sucks as I need it for 2.4GHz work  (there's probably a moral to that story).

I'll have a dig around but need to make some serious backups first.

~
Mike

[brokeit]

Ok, terrible form replying to myself but I've got it up and running with 3.1GHz span and options just with a XXX serial number.

That'll do for now but not sure what a legit firmware upgrade would do to that. I think I'd be reverting it first unless anyone knows otherwise.

~
Mike