(Not actually a new user, but my account form 2012 doesn't exist anymore. It's been a while since I logged in, perhaps accounts got cleared out?)
I was hoping I could post here with a nice success story, but I'm not quite there yet.
Recently acquired an SSA3021X+, FW 2.2.2.3.2. Attempted to perform some "semirandom but careful mistakes" as others have put it
Here's what I did:
1. Ran the SSA3032X+_backup_NAND+mem+firmdata0.ADS and copied the backups to a safe place
2. Ran SVA1032X_telnet.ADS to get telnet
3. Connected to telnet, started with the instructions in #1223
4. Ran into the issue with step 3 about not having enough disk space, copied the ecomb_p file to the USB mount, then tried to copy it back as ecomb but didn't have enough space?!
5. Also couldn't see the last line in startup_app.sh which I fixed with echo "" >> startup_app.sh
6. Tried to symlink /usr/bin/siglent/ecomb to the one on the USB, sync + reboot after editing startup_app.sh but the app still didn't run on boot
7. Now there was more space in /usr/bin/siglent (not sure why?) so I copied ecomb back there and just ran it manually to get the app to run
8. Went through the other steps in #1223 and started an upgrade with SVA1032X_V3.2.2.3.2.ADS
9. Unit rebooted twice but never launched the app. No more telnet either. (sigh)
10. Took off the back cover, got UART access, and ran ecomb from the USB manually and the app started up
11. (This is where I made things worse) I thought that SVA1032X_V3.2.2.3.2.ADS may be too new so I tried again with SVA1032X_V2.2.1.2.8.ADS, downgrading was a bad idea?
12. Following the progress of the upgrade using UART I can see that /usr/bin/siglent ran out of space and now I'm missing ecomb, startup_app.sh and all of /usr/bin/siglent/drivers, plus most other things in /usr/bin/siglent
13. I can still run original ecomb from the USB to get the app up, but it fails to load some drivers so I don't have a touchscreen and it doesn't seem to list any of the files on the USB drive in firmware upgrade anymore, so I can't run another update with an ADS file.
From what I can see, the upgrade_app step failed because there was no space left on /usr/bin/siglent aka MTD7, here's the relevant snippet of UART output:
update.sh starting ...
current version:
upgrade_app: starting
rm: can't remove '/usr/bin/siglent/libscpi*': No such file or directory
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/startup_app.sh': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/startup_app.sh': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/startup_app.sh': No space left on device
-rpf /usr/bin/siglent/usr/usr/upgrade/app/startup_app.sh /usr/bin/siglent/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/app/ /usr/bin/siglent/usr/backup/
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/drivers/insmod_before_app.sh': No space left on device
cp: write error: No space left on device
cp: can't preserve times of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp: can't preserve ownership of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp: can't preserve permissions of '/usr/bin/siglent/drivers/uinput.ko': No space left on device
cp -rpf /usr/bin/siglent/usr/usr/upgrade/drivers/* /usr/bin/siglent/drivers/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/fpga/* /usr/bin/siglent/config/fpga/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/www/* /usr/bin/siglent/config/www/
upgrade_app: there is no *.dtb to upgrade
upgrade_app: ending
rm: can't remove '/usr/bin/siglent/config/log/log4qt.conf': No such file or directory
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/log4cpp.properties
(I have full telnet and UART logs from the entire time I was attempting the cross-flash, so I can post much more detail if that helps.)
Now I have two options that I see:
1. Copy most/all(?) of the original MTD partitions back (nandwrite?) to reset it back to factory state, then try again?
2. Get an MTD7 dump from SVA1032X_V2.2.1.2.8.ADS and namdwrite it to complete the failed upgrade, then go for the SVA1032X_V3.2.2.3.2.ADS upgrade (or the latest version?).
Since I still have UART console access and things don't seem too badly broken, I'm wondering what those more experienced think is the best next step? It seems like I'm close to the goal of an SVA1032X_V2.2.1.2.8 crossflash, I just need a proper MTD7 partition.