Hack of Sigllent spectrum analyzer ssa3021X?

[rf-loop]

Hi rf-loop!
Thanks for your reply.

I followed the exact instruction v05.

Yes, the analyzer created new files.... before restart I just had files with "namex.xml" but now the system recreated new files.... including backup folder.

before restart:

NSP_sn_bandwidthx.xml
NSP_trends_config_infox.xml
calib - I didn't change it....
nsp_data_bx.xml


after restart: new xml files....
 
 

Please do you have terminal communications log. If you have,  analyzing this log may show where something have gone wrong. (because something have gone wrong)

[dotto]

Hi rf-loop!
Thanks for your reply.

I followed the exact instruction v05.

Yes, the analyzer created new files.... before restart I just had files with "namex.xml" but now the system recreated new files.... including backup folder.

before restart:

NSP_sn_bandwidthx.xml
NSP_trends_config_infox.xml
calib - I didn't change it....
nsp_data_bx.xml


after restart: new xml files....
 
 

Please do you have terminal communications log. If you have,  analyzing this log may show where something have gone wrong. (because something have gone wrong)

ok. sorry.

[dotto]

It is working here!
In my case, I entered in system informations before change the file and quickly sent the sync command and reboot.
I don't know but if I wait long time to reboot the file is save again by the system...

Thank you for your help!

[IgorAVR]

It is working here!
In my case, I entered in system informations before change the file and quickly sent the sync command and reboot.
I don't know but if I wait long time to reboot the file is save again by the system...

Have you done hack with FW 8.2 version?

[dotto]

It is working here!
In my case, I entered in system informations before change the file and quickly sent the sync command and reboot.
I don't know but if I wait long time to reboot the file is save again by the system...

Have you done hack with FW 8.2 version?

Yes! Everything ok here!


Enviado do meu iPhone usando Tapatalk

[Safar]

Have you done hack with FW 8.2 version?

Yes! Everything ok here!

Enviado do meu iPhone usando Tapatalk

Agree, but for a strange reason, I was able to rename files in second time only

[IgorAVR]

Thank you for yours answers! I will buy this nice device!

[Joel_l]

So, there is the rename one file method that gets you unlocked and 3.2GHz but no serial number with new FW. It seems that several FWs ago, you could mess with the features file ( seems to no longer be used ) and get all the apps, 3.2GHz, and keep the serial number. I think this survived upgrades from that point. Anyone take a new unit, downgrade the FW, then bring it back to current FW?

[arturfra]

New firmware 8.3 available

http://www.siglent.com/ENs/gjjrj.aspx?id=15

http://www.siglent.com/Uploadfile/image/20170626/SSA3000X-V1.2.8.3.png

[rf-loop]

So, there is the rename one file method that gets you unlocked and 3.2GHz but no serial number with new FW. It seems that several FWs ago, you could mess with the features file ( seems to no longer be used ) and get all the apps, 3.2GHz, and keep the serial number. I think this survived upgrades from that point. Anyone take a new unit, downgrade the FW, then bring it back to current FW?

For what measurement purpose there need serial number?

[Bicurico]

So, there is the rename one file method that gets you unlocked and 3.2GHz but no serial number with new FW. It seems that several FWs ago, you could mess with the features file ( seems to no longer be used ) and get all the apps, 3.2GHz, and keep the serial number. I think this survived upgrades from that point. Anyone take a new unit, downgrade the FW, then bring it back to current FW?

You cannot just dongrade the FW, as this requires a complete reflash of the flash IC. This can be done on the bootloader, but you will lose warranty to access it.
Also, you need a flash dump of the older firmware (does exist with some forum members if required).
But the main issue is that the flash IC can have faulty pages. This is apparently within specs/tolerance. However, if you flash back a good backup of an IC without faulty pages on an IC with faulty pages, the firmware will not work. You need to partition and write the firmware in a propper way that avoids writing to erroneous flash IC's.

I hope to have explained it in a comprehensive way, certainly it could be explained at more detail and without errors. But I guess this makes it clear why a downgrade has risks (lost warranty, problem with faulty flash pages, etc.).

As mentioned by rf-loop, there is no real issue in not having the serial number displayed.

Regards,
vma

[Joel_l]

That does actually make sense. The FW update is not a full install of the SA software. You are right, the missing serial number is not a big deal.

Thanks

Joel

So, there is the rename one file method that gets you unlocked and 3.2GHz but no serial number with new FW. It seems that several FWs ago, you could mess with the features file ( seems to no longer be used ) and get all the apps, 3.2GHz, and keep the serial number. I think this survived upgrades from that point. Anyone take a new unit, downgrade the FW, then bring it back to current FW?

You cannot just dongrade the FW, as this requires a complete reflash of the flash IC. This can be done on the bootloader, but you will lose warranty to access it.
Also, you need a flash dump of the older firmware (does exist with some forum members if required).
But the main issue is that the flash IC can have faulty pages. This is apparently within specs/tolerance. However, if you flash back a good backup of an IC without faulty pages on an IC with faulty pages, the firmware will not work. You need to partition and write the firmware in a propper way that avoids writing to erroneous flash IC's.

I hope to have explained it in a comprehensive way, certainly it could be explained at more detail and without errors. But I guess this makes it clear why a downgrade has risks (lost warranty, problem with faulty flash pages, etc.).

As mentioned by rf-loop, there is no real issue in not having the serial number displayed.

Regards,
vma

[Joel_l]

Has anyone tried 8.3, is the hack in tact? Or do you just need to redo it?

Joel

[Bicurico]

Hi,

The new firmware seems safe to flash. The telnet access is still there with the usual root account and apparently nothing changed.

I did it and have no issues, but I am not using the file delete hack. Should work, though, as before.

Regards,
Vitor

[Joel_l]

I also just did the 8.3 update, no issues, didn't have to change anything. Mine was the single file rename/delete method.

Joel

[arturfra]

So did I, everything has gone in the right way

[MilkmanCDN]

Hello,

Got my SSA-3021x about a month ago and it has been sitting on my bench unused since.  FW8.2 (1.2.8.2) installed on it.   I plan to 'upgrade' it using the instructions contained in post #289.   Couple of questions:

1. Should I upgrade to firmware 8.3 before performing this?
2. Is there anyway to retain the serial number?

Thanks.

[Bicurico]

1. Doesn't matter.
2.

As mentioned by rf-loop, there is no real issue in not having the serial number displayed.

[Joel_l]

Look at post 363/364. That's all you have to do. Use the original instruction to log into and get to where you can rename files, but deleting/renaming ( rename would be recommended ) the one file is it. Do not know of a method that preserve SN.

Hello,

Got my SSA-3021x about a month ago and it has been sitting on my bench unused since.  FW8.2 (1.2.8.2) installed on it.   I plan to 'upgrade' it using the instructions contained in post #289.   Couple of questions:

1. Should I upgrade to firmware 8.3 before performing this?
2. Is there anyway to retain the serial number?

Thanks.

[fact]

Has anyone been able to create a SD-image to boot from in case the update fails?
I experienced a failure while updating to 8.2 and would like to be able to fix the problem myself without having to send the SA in for repair.

[videobruce]

I received my unit this week. It came with firmware 1.2.8.2
I did several experiments with the described mod and found out that it is ALL in the file NSP_sn_bandwith in the firmdata0 directory. so the procedure can be even simpler, just rename this file and the factory mode is operational

sorry for the type error: file name must be NSP_sn_bandwidth of course

You rename that file first, then just flash from 8.2 to 8.3 without restoring first? 

[cesarpaz]

Hi everybody.

I need litle help, My SSA3021X come with 1.2.8.2 firmware, I was update to 1.2.8.3 but it´s imposible get old firmware versions 7.5, 8.1 etc. How Can I do make for hack to 3.2 Ghz? Thanks so much.

[Joel_l]

A bit earlier in the thread I think someone mentioned that 8.3 still lets you log in, so you could do the hack after going to 8.3
You do not need to undo the file rename to upgrade from 8.2 to 8.3.

[videobruce]

So that so called "chapter 5" (restore back to initial state) isn't necessary, one just does the modification (chapter 3)?

[etienne51]

Hi guys, new owner of the Siglent SSA3021X here. It was delivered just yesterday.

I checked the firmware version, and I have 8.1! So I thought I would try this mod see how things goes. Thanks to the V0.5 tutorial (from post #289) things went pretty smoothly, and I have all features unlocked and 3.2GHz bandwidth as of now.

I just wanted to point something out though. When I was renaming the files, the filesystem apparently was remounted automatically, and went back to read only mode. It seems like the original files were rewritten as well, so I had to remove the _x previously moved files, and rename the newly created files again, after remounting the filesystem in rw mode. See below.

Code: [Select]


 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am335x-evm

Arago 2013.05 am335x-evm


am335x-evm login: root
Password:

root@am335x-evm:~# cd /usr/bin/siglent/firmdata0

root@am335x-evm:/usr/bin/siglent/firmdata0# ls -l
-rwxr-xr-x    1 root     root           471 Jul  8 --:-- NSP_sn_bandwidth.xml
-rwxr-xr-x    1 root     root           606 --- -- --:-- NSP_trends_config_info.xml
drwxrwxr-x    2 1000     1000          4240 Jan  1  2000 calib
-rwxr-xr-x    1 root     root           544 Jul  8 --:-- nsp_data_b

root@am335x-evm:/usr/bin/siglent/firmdata0# cd /usr/bin/siglent/usr/backup

root@am335x-evm:/usr/bin/siglent/usr/backup# ls -l
-rwxr-xr-x    1 root     root           471 Jul  8 --:-- NSP_sn_bandwidth.xml
-rwxr-xr-x    1 root     root           606 --- -- --:-- NSP_trends_config_info.xml
drwxr-xr-x    2 root     root          4240 --- -- --:-- calib
-rwxr-xr-x    1 root     root           544 Jul  8 --:-- nsp_data_b

root@am335x-evm:/usr/bin/siglent/usr/backup# cd /

root@am335x-evm:/# cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent/usr/mass_storage/U-disk0/SA-backup
root@am335x-evm:/# cp -R /usr/bin/siglent/firmdata0 /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0

root@am335x-evm:/# cp -R /usr/bin/siglent/usr/backup /usr/bin/siglent/usr/mass_storage/U-disk0/SA-backup
root@am335x-evm:/# cp -R /usr/bin/siglent/firmdata0 /usr/bin/siglent/usr/mass_storage/U-disk0/SA-firmdata0

root@am335x-evm:/# mount -o remount,rw /dev/ubi2_0 /usr/bin/siglent/firmdata0

root@am335x-evm:/# cd /usr/bin/siglent/firmdata0

root@am335x-evm:/usr/bin/siglent/firmdata0# mv NSP_sn_bandwidth.xml NSP_sn_bandwidthx.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv NSP_trends_config_info.xml NSP_trends_config_infox.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv nsp_data_b nsp_data_bx
mv: can't rename 'nsp_data_b': Read-only file system

root@am335x-evm:/usr/bin/siglent/firmdata0# ls -l
-rw-r--r--    1 root     root           471 Jul  8 --:-- NSP_sn_bandwidth.xml
-rw-r--r--    1 root     root           471 Jul  8 --:-- NSP_sn_bandwidthx.xml
-rwxr-xr-x    1 root     root           606 --- -- --:-- NSP_trends_config_infox.xml
drwxrwxr-x    2 1000     1000          4240 Jan  1  2000 calib
-rwxr-xr-x    1 root     root           544 Jul  8 --:-- nsp_data_b

root@am335x-evm:/usr/bin/siglent/firmdata0# cd /

root@am335x-evm:/# mount -o remount,rw /dev/ubi2_0 /usr/bin/siglent/firmdata0

root@am335x-evm:/# cd /usr/bin/siglent/firmdata0

root@am335x-evm:/usr/bin/siglent/firmdata0# rm NSP_sn_bandwidthx.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv NSP_sn_bandwidth.xml NSP_sn_bandwidthx.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv nsp_data_b nsp_data_bx

root@am335x-evm:/usr/bin/siglent/firmdata0# cd /usr/bin/siglent/usr/backup

root@am335x-evm:/usr/bin/siglent/firmdata0# mv NSP_sn_bandwidth.xml NSP_sn_bandwidthx.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv NSP_trends_config_info.xml NSP_trends_config_infox.xml
root@am335x-evm:/usr/bin/siglent/firmdata0# mv nsp_data_b nsp_data_bx

root@am335x-evm:/usr/bin/siglent/firmdata0# cd /

root@am335x-evm:/# sync

root@am335x-evm:/# logout

This is exactly what I have in both folders after the mod.

Code: [Select]

root@am335x-evm:/# ls -l /usr/bin/siglent/firmdata0
-rw-r--r--    1 root     root           471 Jul  8 15:52 NSP_sn_bandwidthx.xml
-rw-r--r--    1 root     root           150 Jul  8 15:55 NSP_trends_config_info.xml
-rwxr-xr-x    1 root     root           606 --- -- --:-- NSP_trends_config_infox.xml
drwxrwxr-x    2 1000     1000          4240 Jan  1  2000 calib
-rwxr-xr-x    1 root     root           544 Jul  8 15:52 nsp_data_bx

root@am335x-evm:/# ls -l /usr/bin/siglent/usr/backup
-rwxr-xr-x    1 root     root           471 Jul  8 15:42 NSP_sn_bandwidthx.xml
-rwxr-xr-x    1 root     root           606 --- -- --:-- NSP_trends_config_infox.xml
drwxr-xr-x    2 root     root          4240 --- -- --:-- calib
-rwxr-xr-x    1 root     root           544 Jul  8 15:52 nsp_data_bx

(The dates are masked for most files since I lost my logs, and I have no record of the original dates during the operation, I chose to mask them. I rewrote these commands to give you guys an idea of what happened.)

Anyway, my spectrum analyser is unlocked, I have XXXXXXXXXX serial number and "Permanent" validity on all options, so I assume everything is fine.

Now, I'm still on 1.2.8.1 firmware, and as far as I understand, I need to:
1. Revert the mod (CHAPTER 5)
2. Run the upgrade 1.2.8.1 -> 1.2.8.3
3. Do the mod again (CHAPTER 3)

Am I right?

As far as I heard, the latest firmware is still compatible with the mod, so it is safe to upgrade?

Thank you guys!