Siglent SSA3000X and SSA3000X-Plus Spectrum Analyzers

[techneut]

Hallo,
I own a SSA3021X Plus and I wondered what would happen if I just by mistake uploaded the SVA1032 firmware file. Would it work and would the telnet firmware upgrade file for the SSA3021X Plus stil work?
Just wondering.

"Hallo"!  You definitely can't do that by mistake! Nonetheless I have a feeling it will work. But that is one of the current open questions. Any volunteer?

Regarding the telnet FW: the SSA probably will not work, but the SVA one should work...

Ok I volonteerd,
first I did it with the upgrade intact and there was the same upgrade window as with the telnet session. After 20 min I did a soft powerdown and the Analyzer booted up fine as a SSA.
After that I rolled bach the upgrade and tryed again with the same result.
It could have been so nice.

[tv84]

Ok I volonteerd,
first I did it with the upgrade intact and there was the same upgrade window as with the telnet session. After 20 min I did a soft powerdown and the Analyzer booted up fine as a SSA.
After that I rolled bach the upgrade and tryed again with the same result.
It could have been so nice.

Explain with details what you did since I think you may not be able to do it by yourself. Maybe I can help.

[techneut]

I put the SVA1032X_2.2.1.2.5.ADS on a memory stick and did a Firmware Update. That gave me a screen with "Updating" for 20 min. Then I aborted bij a soft powerdown.
No harm done but no gain

[tv84]

I put the SVA1032X_2.2.1.2.5.ADS on a memory stick and did a Firmware Update. That gave me a screen with "Updating" for 20 min. Then I aborted bij a soft powerdown.
No harm done but no gain

SVA1032X has Product_ID = 11403
SSA3000X Plus has Product_ID = 11405

without changing this in the FW package you'll never be able to load a different FW package as I had hinted. Do you want me to change it for you?

[techneut]

I would be very gratefull if you would do that for me

[tautech]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Release notes
Improvements:
Add Limit mask offset in SA mode
TG Level adjustable in Reflection Meas
 
Solved Issues:
Fixed AM and FM symbol rate error, Lpf coefficient error, in AMA mode
Fixed Filter bandwidth error in DMA mode
Fixed Freq counter error in SA mode
Fixed Harmonic error in SA mode
Fixed Help Display error

[tubularnut]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

One thing to be mindful off, is that the official update install will often overwrite the start script, so loose any custom telnet start that has been added.

[tautech]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

[tubularnut]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

Ah, ok 

[tautech]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

Ah, ok 

Makes sense don't it ? 

[tubularnut]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

Ah, ok 

Makes sense don't it ? 

Lol, indeed, I’m being an idiot  But never been in this situation before, so new territory for me 

[tautech]

New firmware for SSA3021X and SSA3032X Plus models.

Version V2.2.1.2.7
15.8MB
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SSA3021&32X%20Plus_2.2.1.2.7_EN.zip

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

Ah, ok 

Makes sense don't it ? 

Lol, indeed, I’m being an idiot  But never been in this situation before, so new territory for me

All of us ! 

[tv84]

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

The answer is not so easy as all the "hybrid" SSAs up to now are precisely that: hybrid. 

The best way would be for what techneut has "volunteered" to do: test a crossflash with the full SVA FW.

If that goes OK, then he would have a true SVA from then on.

[tubularnut]

Hmm  Now is this going to work out of the box for an SSA3032X Plus that "thinks" it's an SVA with all options.

Then why would you use an SSA update ? 

The answer is not so easy as all the "hybrid" SSAs up to now are precisely that: hybrid. 

The best way would be for what techneut has "volunteered" to do: test a crossflash with the full SVA FW.

If that goes OK, then he would have a true SVA from then on.

Thank you both, fingers crossed!

[tv84]

Anyway, since there is a lot of activity going on, i strongly suggest you all to make a NAND backup before doing anything.

Doesn't do any harm and may one day become useful.   

I think you can use this script.

Today I'm a bit lazy to pack it into a .ADS file...

[tv84]

Member Elasia took the plunge and the SVA crossflash was not successful!
 
  for his decision!

Now, there's some restoration to do...

[tubularnut]

Oh dear   

[Elasia]

yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt work

I'll have to console it later and see what its doing now

[Sighound36]

Respect for trying my good man 

[tv84]

I'll have to console it later and see what its doing now

U-Boot 2014.07-svn32893 (Jul 23 2018 - 14:42:02)

This is the parsing of the boot.bin in the FW package:

Code: [Select]

**********  Zynq-7000 SoC Boot Header  **********
00000000 -            ARM Vector Table: 8 x EAFFFFFE
00000020 -             Width Detection: AA995566
00000024 -            Header Signature: XLNX
00000028 -                  Key Source: 00000000  -  Not Encrypted
0000002C -                     Version: 01010000  (0x01010000)
00000030 -           FSBL Image Offset: 00001700
00000034 -           FSBL Image Length: 00014014
00000038 -     FSBL Load Address (RAM): 00000000
0000003C -     FSBL Exec Address (RAM): 00000000
00000040 -           Total FSBL Length: 00014014
00000044 -          QSPI Configuration: 00000001  (0x00000001)
00000048 -        Boot Header Checksum: FC16C518  CHKSUM OK
0000004C -                User Defined: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00000098 -   Image Header Table Offset: 000008C0
0000009C - Partit. Header Table Offset: 00000C80
**********  Zynq-7000 SoC Device Register Initialization Table  **********
000000A0 - Register Initialization Pairs  [000000A0-0000089F]
**********  Zynq-7000 SoC Device Image Header Table  **********
000008C0 -                     Version: 01020000  (0x01020000)
000008C4 -             # Image Headers: 00000003
000008C8 - 1st Partition Header Offset: 00000C80
000008CC -     1st Image Header Offset: 00000900
000008D0 -   Header Auth Certif Offset: 00000000
000008D4 -                    Reserved: FFFFFFFF
**********  Zynq-7000 SoC Device Image Headers  **********
           Partitio Reserved  Length  Name
00000900 - 00000C80 00000000 00000001 fsbl.elf
00000940 - 00000CC0 00000000 00000001 fpga_top_sva3000x.bit
00000980 - 00000D00 00000000 00000001 u-boot.elf
**********  Zynq-7000 SoC Device Partition Headers  **********
           EncryLen UnencLen TotalLen DestLoad DestExec ImgOffst AttrBits Sections Checksm  ImHdOffs AuthOffs HdChkSum
00000C80 - 00014014 00014014 00014014 00000000 00000000 00001700 00000010 00000001 00000000 00000900 00000000 FFFF07DF   CHKSUM OK
00000CC0 - 003DBB00 003DBB00 003DBB00 00000000 00000000 00080000 00000020 00000001 00000000 00000940 00000000 FFCFB14E   CHKSUM OK
00000D00 - 0006D21C 0006D21C 0006D21C 04000000 04000000 00580000 00000010 00000001 00000000 00000980 00000000 F7E4DFF9   CHKSUM OK

The extracted files in the attached .zip.

[noreply]

Just to be clear ...

Crossflash in this context ;-

Is it

Flashing SSA3000x Plus firmware to SVA1032x Device  (yet to be successful?)

as opposed to

Flashing SVA1032x firmware to SSA3000x Plus Device (proven to be successful by some members already)

??

At least there is one thing we know (thanks tv84) that are some obvious parameters which need to be changed in the FW package to reflect the different products when doing crossflash

[tv84]

To avoid any misunderstanding:

1. What was now attempted:

- crossflashing the SSA3032X Plus FW into a SVA1032X machine. NOT SUCCESSFULL  (as we speak)

2. What had also been successfully accomplished before:

- overwriting ONLY the SSA3032X app with the SVA1032X app (of the same FW version package).


The first would transform the SSA Plus into a "pure" SVA. The second creates a hybrid specimen. This has nothing to do with the older SSA3000X brother.

Edit: To remove the NOT. See the next msgs and you'll understand what was the problem. 

[jemangedeslolos]

yeah i got smoked, stuck at boot screen and also the prior system key trick doesnt work

I'll have to console it later and see what its doing now

Titanium balls 

I hope you will succeed in restarting it !
I also have a SSA3021X Plus if you need a file or something even if I think you must have everything you need and  the  tv84 help.

[noreply]

OK that makes it totally clear, but ...

- overwriting ONLY the SSA3032X app with the SVA1032X app (of the same FW version package).

Can you elaborate what exactly happens in an overwriting ??

What elements (modules?) of the firmware are device specific as opposed to the app part of the firmware which may or may not be device specific?

I guess true crossflash of untouched firmware would not be possible unless we can somehow make BOTH of the devices look identical to the firmware?

How is that possible? (if not already identical  )

[tv84]

A NAND map plus a device tree blob taken from a SSA3000X+ NAND dump, just for reference.