Hack of Sigllent spectrum analyzer ssa3021X?

[guiscale]

Hello,
I've done something wrong, I have no more screen only Telnet.
I've upload last firmware to clear everything, no change.
Screen is flashing at boot and stay black.
Does anybody can help me ?

Device SSA 3014X Plus

Many thanks
Gui

[tautech]

Hello,
I've done something wrong, I have no more screen only Telnet.
I've upload last firmware to clear everything, no change.
Screen is flashing at boot and stay black.
Does anybody can help me ?

Device SSA 3014X Plus

Many thanks
Gui

Welcome to the forum.

While doing what ? <serious question.

Device SSA 3014X Plus

Typo ? No such model !

[tv84]

You have a SSAX+ with a SVA S/N??   

[tautech]

You have a SSAX+ with a SVA S/N??   

SSA3015X Plus do by default. 

[guiscale]

Hello
Many thanks for your feedback
You are right my model is SSA3015X Plus.
I've tried to convert to a SVA1032 with firmware SVA1032X_V3.2.2.4.0_EN.
To do that I've changed NSP_config_upgrade_info.xml to allow firmware.
after flashing screen was flashing 10 times and stayed off.
I've generated and installed some licenses can it explain that?
I've tried to reflash with SSA3000X-Plus_V3.2.2.6.0R7_EN to come to the initial state.
Where can I get the boot log?

[tv84]

Humans are naturally curious...

3015X doesn't accept 3032X FW. You should rollback the .xml change and see what happens.

Then you should try to flash the oldest 3015X FW acceptable.

Option licenses shouldn't be the problem.

[tautech]

Hello
Many thanks for your feedback
You are right my model is SSA3015X Plus.
I've tried to convert to a SVA1032 with firmware SVA1032X_V3.2.2.4.0_EN.
To do that I've changed NSP_config_upgrade_info.xml to allow firmware.
after flashing screen was flashing 10 times and stayed off.
I've generated and installed some licenses can it explain that?
I've tried to reflash with SSA3000X-Plus_V3.2.2.6.0R7_EN to come to the initial state.
Where can I get the boot log?

Not possible as SSA/SVA 1.5 GHz products are different HW to 2.1/3.2 GHz products.
Best you can do is convert to SVA1015X and install licenses. 

The info is in this or one of the Siglent analyzer threads.

[hmisy]

Hi. I purchased an SSA3021x plus, I would like to activate all the options and the bandwidth expansion, I read the descriptions on the forum about the modification process. I got to the stage where I can access via telnet on port 10101, I ran the key generator python script on the PC, I have the keys but I didn't find any details or I missed something about what I have to do with these keys. can someone help me to make this change? I'm not very good at linux and I'm also afraid of destroying the analyzer.
SW1  3.2.2.6.0R8
SW2  20230524-1501
SW3  000000D4
HW   01.00.00
  Thank you, Mihaly

[807]

Hi. I purchased an SSA3021x plus, I would like to activate all the options and the bandwidth expansion, I read the descriptions on the forum about the modification process. I got to the stage where I can access via telnet on port 10101, I ran the key generator python script on the PC, I have the keys but I didn't find any details or I missed something about what I have to do with these keys. can someone help me to make this change? I'm not very good at linux and I'm also afraid of destroying the analyzer.
SW1  3.2.2.6.0R8
SW2  20230524-1501
SW3  000000D4
HW   01.00.00
  Thank you, Mihaly

I haven't done the crossmod to VNA. I have only opened all the options & upgraded to 3.2GHz. To enter the keys you have generated go to System > system info > Load option. A license key pop up will appear where you enter the keys that were generated by the script. When I did mine, rather than enter the ALL option, I entered the keys that were relevant one at a time i.e. AMK, EMI, DMA, AMA, CAT (for Refl) and 3032.

[hmisy]

wow, how simple . I entered the codes and now everything is OK, 3.2Ghz active, and all the options. I'll probably turn it into a VNA in the future, I'll have to study more, or ask for help .
Thank you for help 807.

[HamDancer]

Today I received a brand new SSA3021X Plus and, with a little help from this forum, it now believes it is a 3.2 GHz SVA1032X. The upgrade process was quite simple, using the Python keygen to enable options, and then using telnet to change the product id by hand to allow cross-flash of the SVA firmware. Then I used the keygen again to turn on DTF. The model number is correct and my serial number is back in place. For anyone wondering about whether things still work, I started with firmware 3.2.2.6.0R8 on HW 01.00.00 and did a cross-flash directly to the latest SVA firmware, 3.2.2.6.0R7.

There is one thing I have a question about, though. The various instructions say to rename two files:

Code: [Select]

mv nsp_data_b1 nsp_data_b1x
mv nsp_data_b nsp_data_bx
but nowhere can I find an explanation as to why this is necessary. I didn't do it, and as far as I can tell everything is working perfectly. Is renaming these files actually required?

Thanks to everyone who made this such a simple process!

[tv84]

Is renaming these files actually required?

Definitely no. These are remnants of old procedures.

[SK]

Hello,

I have here a just delivered SSA3021 plus with

SW1 3.2.2.5.1R20
HW 00.00.00

...and (of course ;-) I like to upgrade it to SVA.

I tried to backup as described above via the SSA3000X+_backup_NAND+mem+firmdata0_11411.ads.

I also tried to get Telnet-Access using the SSA3000X+_telnet_11411.ads

In both cases I can select the ADS-Files and press "Enter". The "firmware-update" starts. The screen changes to "Upgrading now - pleas wait" an the hourglass turns around for about 30 seconds. Then it ends up in the same screen as before (the file-menu) were I can select the ADS-Files. (there is no reboot)

Telnet does not connect on Port 23 or 10101.

I tried to continue with the procedure described her: https://www.eevblog.com/forum/testgear/hack-of-sigllent-spectrum-analyzer-ssa3021x/msg4596574/?topicseen#msg4596574

After sending DEBTTT via SCPI I can telnet to port 23 with "root" PW "1234ding"

Trying to copy the backups (Step II) I get cp: "can't create directory '/usr/bin/siglent/usr/mass_storage/U-disk0/SA-config': Read-only file system"

So I had to

mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0 to make the stick writeable (this step is missing in the description)

Then I was able to copy the Folders, but all together tah are only about 8 Mbytes (413 Files)  - not 480 Mbytes like in the description

by the way: the folder : "/usr/bin/siglent/usr/backup" is empty => should it be?


Does anybody have an idea what I could do to manage the backup?

I worry about only installing the modified SVA-Firmware without a backup.

Would be very nice if someone could post something helpful

Greets


If needed: Here is my content of three often postet files:

Code: [Select]

...<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
        <device>
                <language>english</language>
                <pid>0x1305</pid>
                <vid>0xf4ec</vid>
                <product_type_1>SSA3075X Plus</product_type_1>
                <product_type_2>SSA3075X Plus</product_type_2>
                <product_type_3>SSA3032X Plus</product_type_3>
                <product_type_4>SSA3021X Plus</product_type_4>
                <product_type_5>SSA3015X Plus</product_type_5>
                <manufacturer>Siglent</manufacturer>
                <Support_Touch_Flag>1</Support_Touch_Flag>
                <Support_VXI11_Flag>1</Support_VXI11_Flag>
                <file_prefix>CP_</file_prefix>
        </device>
</nsp_trends_info_root>


<?xml version="1.0" encoding="UTF-8"?>
<nsp_system_info_root>
  <device>
    <system_information>
      <serial_number>
        <chip>SSA3xxxxxxxxxx</chip>
      </serial_number>
    </system_information>
  </device>
<Device><Mac>xx:xx:xx:xx:xx:xx</Mac></Device></nsp_system_info_root>




<?xml version="1.0" encoding="UTF-8"?>^M
<nsp_upgrade_info_root>^M
        <device>^M
                <upgrade_static_id>11411</upgrade_static_id>^M
                <upgrade_start_id>11400</upgrade_start_id>^M
                <upgrade_end_id>11499</upgrade_end_id>^M
        </device>^M
</nsp_upgrade_info_root>        ^M
                ^M

[RoV]

The procedure to start telnet with the ADS file worked for me in 2021 with telnet on port 10101, but I think it is now obsoleted by the SCPI command. I remember it didn't reboot the system, because the ADS file just run an executable, but it didn't return control to the instrument, remaining busy there.
As regards the read-only USB stick, perhaps now they make it writable only when needed. Try:
mount -o remount,rw /usr/bin/siglent/usr/mass_storage/U-disk0

[HamDancer]

I also had to mount the USB drive rw before I could copy to it.

The backups that you do with cp are very different from the backups you do with that ads file. The latter backs up the whole firmware, not just some configuration files.

With my brand new SSA3021X+, which came with 3.2.2.6.0R8, I was able to run the firmware backup on the second try. The first didn’t do much but did reboot. So I’d try it again. You might also try upgrading to the latest firmware before trying it.

[SK]

Thank you - i had small success:

meanwhile I tried it several times with 3 different USB-Sticks

2 of them USB 2.0 which normally work well when doing jobs like this...

the 3. stick was USB 3.0 (Jetflash JF 780, 16GB) finally did the job by the second attempt.

Now I have a file named memdump, a folder firmdata0 and mtd0.bin to mtd11.bin 

Funny question how could this backup be restored - does anybody did this ever?

[hmisy]

Hi. I finally managed to convert my SSA3021x+ to SVA1032x and it seems to work well. I have only one problem, when I want to activate the relf or meas option it gives me an invalid key, is this normal or did I miss something. Before I did the transformation it worked.

ok, I found the answer in a post by Tautech (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg5234703/#msg5234703) where he answers a question like "And what is the Refl option?
     I noticed that it is on SSA, but it is no longer on SVA. "

Reflection measurements are standard in SVA models and enhanced to provide Smith charts, Mag Loss, SWR and Phase of which you can overlay all using the 4 traces available.

Thank you, Mihaly

[tautech]

Hi. I finally managed to convert my SSA3021x+ to SVA1032x and it seems to work well. I have only one problem, when I want to activate the relf or meas option it gives me an invalid key, is this normal or did I miss something. Before I did the transformation it worked.
Thank you, Mihaly

Reflection option is not used in SVA models as VNA mode covers it.

For other options go look at the official options and their option names here:
https://www.siglenteu.com/spectrum-analyzers/sva1000x-spectrum-vector-analyzer/

[hmisy]

Thanks for the info. That's what I thought too, but I wasn't sure.

[Volcano]

Thanks guys! Just upgraded my SSA3021X Plus to SVA1032X plus full options 

[EE-digger]

SSA3021X+ arrived at noon.  It's now an SVA1032X except in model number.

I bought this as an experiment to see where these units are really at.  The threads have been great on "upgrading" methods but scant information (except good phase noise discussions) on other functions.

Initial thoughts:

Spectrum analyzer - pretty darned good, good speed, clean noise floor, good measurement functions.  Channel and occupied BW measurements match an Agilent PSA.

VNA - very disappointing, very basic operation.  Perhaps Siglent doesn't want to give away the code from it's higher end units, including IFBW and other functions.  But in the end, it works.  I have quality plots of antenna response for several eval boards with BT chip antennas.  It did a nice job of finding bandwidth and giving good graphics and table of results.

Suggestions

1.  *Correction* - missed the BACK arrow over the soft keys  -  -  - The lack of a BACK function is very painful and very lacking.  The units are low cost but that doesn't matter.  You NEED a back function.  A depth of 2 or 3 would be nice.

2.  The lack of VNA IF control except on their high end models hurts their noise floor for SOLT calibration.  The good news is that it seems very stable over several hours.  Unit came in from very cold weather and two hours inside, I'm not seeing drift.

3.  STRANGE - loading up a STA file does not flip to the function for that file (i.e. SA or VNA).  It will ignore a VNA STA if in SA mode but doesn't tell you.

For me this was a dry run for Siglent and a higher frequency, better performance model from them.  Hard to beat for $1600. 

And Saelig gives a 6% discount to EEVBlog members.  I was told by TEquipment that this discount is GONE with their acquisition by Test Equity.  TEq will now CHARGE a stocking fee for returns.  Like Keysight, they've gone off key.  Some years back you could get a demo unit, then were told to just buy one because you can return freely.  All gone for Test Equity.  Verified with two individuals so if this is not the case, feel free to respond and flog your support staff.   

Dooooh !!  I didn't even see the back arrow above the soft keys.   

[tautech]

For me this was a dry run for Siglent and a higher frequency, better performance model from them. 

SNA5000A ?
Prepared to be pleasantly shocked. A very different beast awaits you.

[EE-digger]

For me this was a dry run for Siglent and a higher frequency, better performance model from them. 

SNA5000A ?
Prepared to be pleasantly shocked. A very different beast awaits you.

I have a PNA.  I'm already shocked and adjusting.  That was $65k ... a long time ago, long before it was mine  .

Yes, the SNA5000A looks good.  At that price though, the competition in the used market is stiff.  Also, at that price point, the firmware better be a lot more complete and robust.

One thing that concerns me on this SVA1032X "upgraded" unit is that calibration with an Agilent cal kit does not look right.  I'm keying it in by hand as a user1 to see if that makes a difference.  The O,S,L look good visibly but when you turn on port extensions, it doesn't look like it used the correct constants.

[EE-digger]

So with the kit constants for an 85033D/E keyed in, the analyzer cals correctly.  Short and Open are two arcs of lengths that are close to the constants table for the kit.  Performing an AUTO-OPEN shows extension of proper delay.

With the built in 85033D/E menu selection, the results are clearly WRONG.  Both arcs are very short and extensions to make dots are way off.

Could this have any relation to how I "upgraded"?  I used the simplest method (downgraded then upgraded to the patched, matching version, then applied keys).

[EE-digger]

I believe that Siglent has a major problem with their internal calibration kits but since I have a hacked product, cannot pursue this with them.

Findings:

1. calibration results with an Agilent 85033D/E kit were way off when using the associated kit in the Siglent, as seen on OPEN and SHORT arcs being of incorrect length/delay
2. I hand entered the constants for this kit into USER1 and it worked perfectly
3. The two files in "cali" did not appear when I did the cross flash to an SVA
4. I copied the two files into the "cali" folder
5. They had no effect on the bad cal with the built in kit
6. * this confirmed that the two files NA1_P and NA2_P, DID NOT CONTAIN CAL KIT INFO, but something else
7. Discovered the vnacalikitdata folder and the *.CSV files it contains with cal kit names ... MAJOR PROBLEM HERE ...
    * the .csv files are incomplete, do not cover the kits shown in the menu
    * BIGGER PROBLEM - the .csv files contain frequency and two columns of data, not the typical cal kit constants, meaning that they are data
       or S parameter based *

So currently, this limits us to TWO cal kits, USER1 and USER2, that we need to key in by hand.

This is my assumption based on actual results on one kit and observations of an incomplete list of kits in the .csv files.  Perhaps the remainder are elsewhere, I don't know.  I do know that a .csv for the 85033D/E does not exist in this folder.

If Siglent has implemented their own data based kits for commercial kits whose data is well published, then Siglent's kits are useless.

I'm very interested in a high end model from them but this puts a damper on that.  Also, this encryption crap for all of their files helps no one.  The calibration kits should be picked up from external files that can be examined, or cloned and modified for special use.