Semirandom but careful mistakes - Page 1
Forum section: electronics / testgear

author: tv84
author_rank: Super Contributor
timestamp: December 10, 2020, 01:11:44 pm
content: 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...

author: tv84
author_rank: Super Contributor
timestamp: December 10, 2020, 02:58:08 pm
content: 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:1. Telnet into the SSA3015X+2. rename/usr/bin/siglent/ecomb_pto/usr/bin/siglent/ecomb3. 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 Reboot6. 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, useat leastthis FW version. Previous versions may get you into trouble.

author: Elasia
author_rank: Frequent Contributor
timestamp: December 10, 2020, 07:12:20 pm
content: Quote from: tautech on December 10, 2020, 06:59:21 pmMore than misleading... the pdf side by side shows a completely different spec.. I recant my earlier postcompare both pdf spec sheets side by side.. the SSA3015X+ should be the same hardware as the SVA1015Xhttps://siglentna.com/wp-content/uploads/dlm_uploads/2020/02/SVA1000X_DataSheet_DS0701X_E04A.pdf

author: tautech
author_rank: Super Contributor
timestamp: December 10, 2020, 08:29:49 pm
content: Quote from: tautech on December 10, 2020, 06:59:21 pmOne email to the US and it's been fixed already !Time now to clean some posts.

author: tv84
author_rank: Super Contributor
timestamp: December 10, 2020, 09:13:21 pm
content: Curiosity:Product IDs:11401 - SVA initial models11402 - SVA1015X11403 - SVA1032X11404 - SVA1075X11405 - SSA3032X+11406 - SSA3075X+11407 - SSA3015X+ <- Wasn't Siglent initially planning on releasing this one?11408 - SSA3000X-R11409 - ? ? ?11410 - SVA1000X (with V3.2.2.4.0 FW and up) all models11411 - SSA3000X+ (with V3.2.2.4.0 FW and up) all models11412 - SSA3000X-R (with V3.2.2.4.0 FW and up) all models

author: tautech
author_rank: Super Contributor
timestamp: December 10, 2020, 09:25:22 pm
content: Quote from: tv84 on December 10, 2020, 09:13:21 pmThey 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 seeminglynewSSA3015X Plus = early SVA1015X without VNA option.

author: tv84
author_rank: Super Contributor
timestamp: December 17, 2020, 07:23:52 pm
content: Here is the demonstration of another "semirandom mistake":A SSA3015X+ that booted up as a SVA1015X.

author: alannz
author_rank: Contributor
timestamp: December 21, 2020, 01:15:22 am
content: 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 USBcp /usr/bin/siglent/startup_app.sh /usr/bin/siglent/usr/mass_storage/U-disk0/startup_app.shTo copy from USB back to SAmv /usr/bin/siglent/startup_app.sh cp /usr/bin/siglent/startup_app.sh.oldcp /usr/bin/siglent/usr/mass_storage/U-disk0/startup_app.sh cp /usr/bin/siglent/startup_app.sh3. 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/siglent3. 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 && rebootThank you to the technical Gurus on this forum, you truly ROCK!

author: luillo
author_rank: Newbie
timestamp: January 06, 2021, 11:07:59 am
content: Quote from: tv84 on December 10, 2020, 02:58:08 pmAlways impressed with your work @tv84.... Has anyone tested this procedure on the SSA3021X Plus model?

author: tv84
author_rank: Super Contributor
timestamp: January 06, 2021, 11:10:12 am
content: Quote from: luillo on January 06, 2021, 11:07:59 amIt all started with that one. Have a look at its thread.

author: tautech
author_rank: Super Contributor
timestamp: September 14, 2021, 11:58:42 am
content: 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.

author: 2N3055
author_rank: Super Contributor
timestamp: September 14, 2021, 12:24:18 pm
content: Quote from: tautech on September 14, 2021, 11:58:42 amSame here!!

author: egonotto
author_rank: Super Contributor
timestamp: September 14, 2021, 03:48:16 pm
content: Hello,Happy birthday tv84 also from me!Best regardsegonotto

author: tv84
author_rank: Super Contributor
timestamp: September 14, 2021, 04:12:55 pm
content: LOL, guys. No need but thank you very much. My birthday is not a random mistake. It happens periodically!

author: minsik
author_rank: Contributor
timestamp: July 17, 2024, 07:34:52 am
content: 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.