Semirandom but careful mistakes

[tv84]

Some people have been asking for some mistakes regarding the SSA3015XPlus and SVA1015X models.

If anyone has succeeded in this crossflash, please put it here.

Maybe I'll have a look one of these days...

[tv84]

ATTENTION: This is an untested procedure so proceed at your own risk.

It's an adaptation of the successful procedure used to crossflash the SSA3032X+ into SVA3032X.

Procedure to try crossflash from SSA3015X+ to SVA1015X:

Code: [Select]

1. Telnet into the SSA3015X+
2. rename
   /usr/bin/siglent/ecomb_p
   to
   /usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
   /usr/bin/siglent/ecomb_p &
   to
   /usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
   <upgrade_static_id>11407</upgrade_static_id>
   to
   <upgrade_static_id>11402</upgrade_static_id>
5. Sync and Reboot
6. If everything is OK, now you can update your SSA with the latest SVA1015X stock FW.
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.

As always: do it at your own risk.
The script to open telnet at port 10101 is attached.

BEFORE STARTING THE OPERATION YOU SHOULD DO A FULL NAND BACKUP.


When flashing the stock SVA FW, use at least this FW version. Previous versions may get you into trouble.

[Elasia]

Buyer beware, looking at the datasheets this should be converted into an SVA3021+ or 32+.. the 15 does not look like the same hardware so if someone does that you may get unexpected results trying to run it at 1.5GHz license mode

Also of note.. the tracking gen mysteriously goes to 3.2GHz

https://siglentna.com/product/ssa3015x-plus/

IMHO this is a serious misleading mistake in NA's shop page. 

No where in any datasheet is it specified SSA3015X Plus TG will do 3.2 GHz !
https://siglentna.com/wp-content/uploads/dlm_uploads/2020/02/SSA3000X-Plus_DataSheet_DS0703P_E03A.pdf

More than misleading... the pdf side by side shows a completely different spec..  I recant my earlier post

compare both pdf spec sheets side by side.. the SSA3015X+ should be the same hardware as the SVA1015X

https://siglentna.com/wp-content/uploads/dlm_uploads/2020/02/SVA1000X_DataSheet_DS0701X_E04A.pdf

[tautech]

Buyer beware, looking at the datasheets this should be converted into an SVA3021+ or 32+.. the 15 does not look like the same hardware so if someone does that you may get unexpected results trying to run it at 1.5GHz license mode

Also of note.. the tracking gen mysteriously goes to 3.2GHz

https://siglentna.com/product/ssa3015x-plus/

IMHO this is a serious misleading mistake in NA's shop page. 

No where in any datasheet is it specified SSA3015X Plus TG will do 3.2 GHz !
https://siglentna.com/wp-content/uploads/dlm_uploads/2020/02/SSA3000X-Plus_DataSheet_DS0703P_E03A.pdf

One email to the US and it's been fixed already !  
Time now to clean some posts.

[tv84]

Curiosity:

Product IDs:
11401 - SVA initial models
11402 - SVA1015X
11403 - SVA1032X
11404 - SVA1075X
11405 - SSA3032X+
11406 - SSA3075X+
11407 - SSA3015X+   <- Wasn't Siglent initially planning on releasing this one?
11408 - SSA3000X-R
11409 - ? ? ?
11410 - SVA1000X    (with V3.2.2.4.0 FW and up)  all models
11411 - SSA3000X+    (with V3.2.2.4.0 FW and up)  all models
11412 - SSA3000X-R   (with V3.2.2.4.0 FW and up)  all models

[tautech]

Curiosity:

Product IDs:
11407 - SSA3015X+   <- Wasn't Siglent initially planning on releasing this one?

They did:
It has same capability as early SVA1015X when VNA mode was an additional $ option then later VNA mode was included as standard at an increased retail price.
Back then SVA1015X cost plus VNA option = SVA1015X cost today.

This seemingly new SSA3015X Plus = early SVA1015X without VNA option.

[tv84]

Here is the demonstration of another "semirandom mistake":

A SSA3015X+ that booted up as a SVA1015X.   

[alannz]

I can confirm this works fantastically.


A couple of things to watch out for;

1. Make sure your SSA is on the LATEST version.

2. the startup_app.sh script has had some escape characters inserted. Not sure why, this means that if you edit with vi' you will not see the line that you need to change. (It should be the last line in the file)

The way around this is to copy the script to your USB key, then edit using a PC (I used notepad++)

To copy to USB
cp /usr/bin/siglent/startup_app.sh /usr/bin/siglent/usr/mass_storage/U-disk0/startup_app.sh

To copy from USB back to SA
mv /usr/bin/siglent/startup_app.sh cp /usr/bin/siglent/startup_app.sh.old
cp /usr/bin/siglent/usr/mass_storage/U-disk0/startup_app.sh cp /usr/bin/siglent/startup_app.sh


3. Another issue I found that the /usr/bin/siglent and /usr/bin/siglent/usr/mass_storage/U-disk0/ were mounted "read only"

mount -o remount,rw /usr/bin/siglent


3. Ensure once all the changes are made you choose to "Sync and reboot" but CHECK all files first and make sure you have no errors!

sync && reboot

Thank you to the technical Gurus on this forum, you truly ROCK!

[luillo]

ATTENTION: This is an untested procedure so proceed at your own risk.

It's an adaptation of the successful procedure used to crossflash the SSA3032X+ into SVA3032X.

Procedure to try crossflash from SSA3015X+ to SVA1015X:

Code: [Select]

1. Telnet into the SSA3015X+
2. rename
   /usr/bin/siglent/ecomb_p
   to
   /usr/bin/siglent/ecomb
3. in file /usr/bin/siglent/startup_app.sh change the line
   /usr/bin/siglent/ecomb_p &
   to
   /usr/bin/siglent/ecomb &
4. in file /usr/bin/siglent/config/NSP_config_upgrade_info.xml change the line
   <upgrade_static_id>11407</upgrade_static_id>
   to
   <upgrade_static_id>11402</upgrade_static_id>
5. Sync and Reboot
6. If everything is OK, now you can update your SSA with the latest SVA1015X stock FW.
7. After having flashed your first SVA stock FW, the SSA has become a "true" SVA.

As always: do it at your own risk.
The script to open telnet at port 10101 is attached.

BEFORE STARTING THE OPERATION YOU SHOULD DO A FULL NAND BACKUP.


When flashing the stock SVA FW, use at least this FW version. Previous versions may get you into trouble.

Always impressed with your work @tv84.... Has anyone tested this procedure on the SSA3021X Plus model?

[tv84]

Always impressed with your work @tv84.... Has anyone tested this procedure on the SSA3021X Plus model?

It all started with that one. Have a look at its thread.

[tautech]

Some fella sent me an email yesterday and slipped it was to be his birthday today.....

Happy birthday tv84 ! 

I'll have one of these for you. 

[2N3055]

Some fella sent me an email yesterday and slipped it was to be his birthday today.....

Happy birthday tv84 ! 

I'll have one of these for you. 

Same here!!

[egonotto]

Hello,

Happy birthday tv84 also from me!

Best regards
egonotto

[tv84]

LOL, guys. No need but thank you very much. My birthday is not a random mistake. It happens periodically!

[minsik]

Question re a ssa3015x+ changing to a sva1015x procedure for the current 2024 OS, if it pleases my lords.
Yes, I am late to the party but because of so much smattering of information its all a bit of a muddy procedure, and one does not want to release the smoke!

This ssa3015x+ is on the latest firmware 3.2.2.6.2R5.

I have telnet access + RW access to the main directories and USB device. However there is no Ecomb or ecomb_p files existing, assumed because it is already above 3.2.2.4. The main configuration file is Aladdin in /usr/bin/siglent/.   

So is the only modification required to update the NSP file with the device ID changing from 11411 to 11410? sync and reboot, then load the new 1000x firmware which is at the same FW level?

thanks for at least some guidance.
Minsik.