Another short report of a cross flash
Starting with 2.2.1.2.3r1 I first performed a nand dump(mtd0 - mtd11) and made myself acquainted with the file system(s). At this moment telnet access with the default password was available.
/usr/bin/siglent # df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 61.7M 61.7M 0 100% /
devtmpfs 68.2M 0 68.2M 0% /dev
none 76.3M 4.0K 76.3M 0% /tmp
ubi1_0 29.7M 18.8M 10.9M 63% /usr/bin/siglent
ubi2_0 5.7M 364.0K 5.4M 6% /usr/bin/siglent/firmdata0
ubi3_0 5.7M 24.0K 5.7M 0% /usr/bin/siglent/log
ubi0_0 82.8M 300.0K 82.5M 0% /usr/bin/siglent/usr
/dev/sda1 7.5G 171.2M 7.3G 2% /usr/bin/siglent/usr/mass_storage/U-disk0
One of the remarkable findings was that there was no ecomb file and an empty firmdata1 directory
/usr/bin/siglent # ls
Aladdin firmdata0 log startup_vnc.sh vnc_test
config firmdata1 startup_app.sh usr vncserver
drivers lib startup_ftp.sh vdma_vnc.sh vsftpd
I updated to 2.2.1.2.5 and using the telnet.ads I gained accesss again. Again performed then and dump.
The filesystem changed somewhat
/ # df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 61.7M 61.7M 0 100% /
devtmpfs 68.2M 0 68.2M 0% /dev
none 76.3M 4.0K 76.3M 0% /tmp
ubi1_0 29.7M 22.7M 7.0M 76% /usr/bin/siglent
ubi2_0 5.7M 600.0K 5.1M 10% /usr/bin/siglent/firmdata0
ubi3_0 5.7M 24.0K 5.7M 0% /usr/bin/siglent/log
ubi0_0 82.8M 756.0K 82.0M 1% /usr/bin/siglent/usr
/dev/sda1 7.5G 712.5M 6.8G 9% /usr/bin/siglent/usr/mass_storage/U-disk0
And the ecomb_p file showed-up
/usr/bin/siglent # ls
config ecomb_p lib php.ini startup_vnc.sh vnc_test
config_eth0.sh firmdata0 lighttpd.conf startup_app.sh usr vncserver
drivers firmdata1 log startup_ftp.sh vdma_vnc.sh vsftpd
from this situation I followed the #963 post, renamed ecomb edited NSP_config_upgrade_info.xml and rebooted followed by upgrade with SVA1032X_2.2.1.2.7.ADS
The result was a SVA with 2.1 G bandwidth and grayed out VNA keys and 5 permanent licences including serial. Only after changing
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1305</pid>
<vid>0xf4ec</vid>
<product_type_1>SSA3032X Plus</product_type_1>
<product_type_2>SSA3021X Plus</product_type_2>
<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>
And
/ # mv /usr/bin/siglent/firmdata0/NSP_sn_bandwidth.xml /usr/bin/siglent/firmdata0/NSP_sn_bandwidthx.xml
/usr/bin/siglent/firmdata0 # mv nsp_data_b1 nsp_data_b1x
The system was fully enabled after a reboot(however in pro-mode)
Next step is the factory calibration of the VNA part
It appeared to me that a “cali” directory is placed under firmdata0 and it seems to represent correction data for several parts of the instrument. There is also a configuration directory, however this seems to contain mathematical lookup tables etc.
In the cali directory it looks like attenuator corrections, IF stats, TG output power, RF attenuation etc
Question; could someone with a genuine SVA check if more files are included in this section please.
If so a wrong file might be better than no file or even we might have a possibility to calibrate the instrument ourselves.(I know, wishful thinking)
All in all it was a useful exercise.