Siglent SVA1015X and SVA1032X 1.5, 3.2GHz Spectrum & Vector Network Analyzers

[tubularnut]

File sizes, and (last line of) script, and filesystem sizes look correct.

NB. The filesystem list does not show memory usage, just filesystem sizes. The ecomb app is not a filesystem.

Can you do the following, this will tell you for sure if Aladdin is running.

  ps -ef | grep Aladdin
  689 root       6:00 /usr/bin/siglent/Aladdin    <<----- Important one!
  901 root       0.00 grep Aladdin

If you don't see it, then Aladdin hasn't started.

[tv84]

My wild guess:

When you do an upgrade from the USB stick, the .ADS occupies disk space in the USB disk. Then it decompresses to the filesystem upgrade dir.

When you do and upgrade via web, you must download the .ADS to the filesystem spending precious space. When it decompresses, it consumes further space...

I wonder if it is really possible to do any upgrade via web on the current SSAX+ and/or SVAs... 

Try to see if you any content in the filesystem's upgrade directory and delete all that content. I would assume it should start at the next reboot...

Nonetheless, I don't fully grasp what this problem could be.

[Kibabalu]

Hi tuburlanut,

yes ist runs:

Code: [Select]

ps -ef | grep Aladdin
  956 root       0:00 grep Aladdin


[Kibabalu]

My wild guess:

When you do an upgrade from the USB stick, the .ADS occupies disk space in the USB disk. Then it decompresses to the filesystem upgrade dir.

When you do and upgrade via web, you must download the .ADS to the filesystem spending precious space. When it decompresses, it consumes further space...

I wonder if it is really possible to do any upgrade via web on the current SSAX+ and/or SVAs... 

Try to see if you any content in the filesystem's upgrade directory and delete all that content. I would assume it should start at the next reboot...

Nonetheless, I don't fully grasp what this problem could be.

Hi tv84,

where should the upgrade directory be located?

under /usr/bin/siglent/usr/usr?

it's empty

[tubularnut]

Hi tuburlanut,

yes ist runs:

Code: [Select]

ps -ef | grep Aladdin
  956 root       0:00 grep Aladdin


Actually it’s not running, that is just the grep command itself. There should be another line for /usr/bin/siglent/Aladdin.

So for some reason it is not starting.

As tv84 says, try removing the upgrade contents.

Edit: Apologies. I left out the 'grep' process from the ps output for clarity (or so I thought) but have added it back in to my post.

[Kibabalu]

when I start Aladdin manually, I'm seeing this :

Code: [Select]

/usr/bin/siglent/usr/tmp # init log error[File /usr/bin/siglent/usr/tmp/config/log/log4cpp.properties does not exist]
log init finished
[ 7414.066490] spidev spi1.1: setup: unsupported mode bits f8
mac ioctl error
Udisk = U-disk0  not found notes
the u-disk sum = -1 is error

 remove udisk /usr/bin/siglent/usr/mass_storage/U-disk0
not erase the udisk = U-disk0
[ 7414.154089] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

        挂载U盘 /usr/bin/siglent/usr/mass_storage/U-disk0    device = /dev/sda1
udhcpc: started, v1.26.0.git
Setting IP address 0.0.0.0 on eth0
sh: write error: Device or resource busy
sh: write error: Device or resource busy
udhcpc: sending discover
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
mod_if_exit_handler:signal=6
Clean Up Ready!
Clean Up - dev_thread
Clean Up - dev_interpreter
Clean Up - SCPI
Clean Up - USBTMC
Clean Up - VXI_11
Clean Up - telnet_scpi
Clean Up - socket
Clean Up - GPIB
Clean Up - nsp adapter
Clean Up Over!
udhcpc: sending select for 192.168.42.76
[ 7414.253652] <<-GTP-INFO->> System resume.
[ 7414.253664] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 7414.273275] <<-GTP-INFO->> GTP wakeup sleep.
[ 7414.273285] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
udhcpc: sending select for 192.168.42.76
udhcpc: sending select for 192.168.42.76
udhcpc: lease of 192.168.42.76 obtained, lease time 864000
Setting IP address 192.168.42.76 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.42.1
Recreating /usr/bin/siglent/usr/etc/resolv.conf
 Adding DNS server 192.168.42.1


[tv84]

Do like this:

Code: [Select]

chmod -R 777 /usr/bin/siglent/usr/usr/upgrade/*
sync
mount -o sync,rw,remount /usr/bin/siglent/
sync

rm  /usr/bin/siglent/usr/usr/upgrade/*.zip
rm  /usr/bin/siglent/usr/usr/upgrade/*.ADS
rm  /usr/bin/siglent/usr/*.zip
rm  /usr/bin/siglent/usr/*.ADS
sync
I extracted this from the start of the upgrade.sh (initial script run in an .ADS update).

[Kibabalu]

the folder /usr/bin/siglent/usr/usr/upgrade/ isn't existing. Maybe, that's the problem?

I can create it, but than it is still empty. Should the .ADS file be located there?

[tubularnut]

I wonder if something wasn't copied across during the upgrade because of space filling up. Which you won't see now as any temporary files may have been removed when rebooted.

I would suggest running the upgrade (again) from a USB drive, but I have no idea how to do that from the internal serial port. @tv84 ??

[tv84]

the folder /usr/bin/siglent/usr/usr/upgrade/ isn't existing. Maybe, that's the problem?

I can create it, but than it is still empty. Should the .ADS file be located there?

Don't worry with the things that don't exist.

Ensure that you have those *.ADS and *.zip deleted.

I wonder if something wasn't copied across during the upgrade because of space filling up. Which you won't see now as any temporary files may have been removed when rebooted.

I would suggest running the upgrade (again) from a USB drive, but I have no idea how to do that from the internal serial port. @tv84 ??

The best is to do it via the app. Let him do the deletes and see where that goes.

[Kibabalu]

There is no upgrade folder, thus there's nothing to delete.

A search for ADS-files gave just files on the USB stick:

Code: [Select]

/usr/bin/siglent # find / -name "*.ADS"
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V3.2.2.3.2.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_backup.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V2.2.1.2.8.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_V2.2.1.2.8.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SSA3000X_Plus_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SSA3000X_Plus_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_backup.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V3.2.2.3.3R1.ADS

No zip-files at all.

[Kibabalu]

what's about an upgrade from USB disk initiated from the terminal, like tuburlanut said? Is that possible?

What's usually inside the upgrade folder?

[Kibabalu]

I manually startet Aladdin. Now it's inside the process list:

Code: [Select]

ps -ef | grep Aladdin
 1022 root       0:15 /usr/bin/siglent/Aladdin
 1095 root       0:00 grep Aladdin

But there the device still stucks inside the siglent boot screen.

[tubularnut]

I manually startet Aladdin. Now it's inside the process list:

Code: [Select]

ps -ef | grep Aladdin
 1022 root       0:15 /usr/bin/siglent/Aladdin
 1095 root       0:00 grep Aladdin

But there the device still stucks inside the siglent boot screen.

I believe you have access to the internal serial port?

If you capture the output from that, as a normal boot, without the USB drive plugged in, then someone may be able to spot why Aladdin is not starting on normal boot. (Attach as a text file will be best)

[Bicurico]

Hi,

The upgrade should be in folder /usr/bin/siglent/usr/usr/upgrade/.

Here you should see:

Folder: add
Folder: app
Folder: drivers
Folder: plat
Folder: sys
Folder: vnc
upgrade.sh
upgrade_add.sh
upgrade_app.sh
upgrade_drivers.sh
upgrade_plat.sh
upgrade_sys.sh
upgrade_vnc.sh

I suspect that what happend to your device was:

1) You tried to do the web upgrade
2) This downloaded the upgrade to attached USB disk
3) After extraction of files and first reboot you removed USB disk (?)
4) Upgrade was not correctly finished, because USB drive was not present

There is no official way to upgrade manually from USB, as all shell scripts would be pointing to wrong folders.

If you want to try, I can send you the contents of the upgrade folder.
I am not so sure about disk space, which is why it is always best to run the update from within Aladdin.

Anyway, you would have to:

1) mount the /usr/bin/siglent folder as rw:
mount -o sync,rw,remount /usr/bin/siglent/

2) copy the files and folders (of the archive) to /usr/bin/siglent/usr/usr/upgrade/

3) sync

4) cd /usr/bin/siglent/usr/usr/upgrade/

5) ./upgrade.sh

Send me your email per PM.

Regards,
Vitor

[tv84]

Here is the zip with the .ADS contents.

I suggest you do the following:

chmod -R 777 /usr/bin/siglent/usr/usr/upgrade/*
mount -o sync,rw,remount /usr/bin/siglent/
mount -o sync,rw,remount /usr/bin/siglent/firmdata0
sync

Unzip the .ZIP into:

/usr/bin/siglent/usr/usr/upgrade/

Sync.

Then manually launch:

/usr/bin/siglent/usr/usr/upgrade/upgrade.sh

[Kibabalu]

I manually startet Aladdin. Now it's inside the process list:

Code: [Select]

ps -ef | grep Aladdin
 1022 root       0:15 /usr/bin/siglent/Aladdin
 1095 root       0:00 grep Aladdin

But there the device still stucks inside the siglent boot screen.

I believe you have access to the internal serial port?

If you capture the output from that, as a normal boot, without the USB drive plugged in, then someone may be able to spot why Aladdin is not starting on normal boot. (Attach as a text file will be best)

Hi tuburlanut,

see the attached file.

[tubularnut]

A number of errors are reported for Aladdin, which is either itself corrupted, or the underlying filesystem is corrupted.

Code: [Select]

% grep corrupted iTerm2\ Session\ 30.\ Dec\ 2020\ at\ 6_04_21\ PM.txt
[    1.748128] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.888495] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.034812] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.520557] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x*** glibc detected *** 00ed0a80/usr/bin/siglent/Aladdin ***
: free(): corrupted unsorted chunks: 0x00ed08d8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00fa7ce8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0730 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0588 ***
/usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0338 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed01d0 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0028 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecfe80 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecfcd8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf920 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf6f8 ***
359b2000-359b6000 r-xp 000030/12/2020 15:49:14 /lib/libc.so.6(+0x*** glibc detected *** 636e8/usr/bin/siglent/Aladdin): [0xfree(): corrupted unsorted chunks35a226e8: 0x]
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf458 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x/lib/libc.so.600ecf360/lib/libc.so.6((exitgsignal+0x+0x143c))[0x[0x359f1270359ebfc8]
[    1.748054] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.888402] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.034702] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.520337] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
*** glibc detected *** /usr/bin/siglent/Aladdin: corrupted double-linked list: 0x00ef2188 ***
[    1.748233] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[    1.888603] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.028302] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[    2.514028] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0


[Kibabalu]

Here is the zip with the .ADS contents.

I suggest you do the following:

chmod -R 777 /usr/bin/siglent/usr/usr/upgrade/*
mount -o sync,rw,remount /usr/bin/siglent/
mount -o sync,rw,remount /usr/bin/siglent/firmdata0
sync

Unzip the .ZIP into:

/usr/bin/siglent/usr/usr/upgrade/

Sync.

Then manually launch:

/usr/bin/siglent/usr/usr/upgrade/upgrade.sh

It's a little bit embarrassing, but I'm struggling with copying files from my machine to the device using a terminal emulation. What is the best way to do it? Is there something like scp for UART?

[tubularnut]

Put the files on your USB disk, plug it in, and you should see the USB path as you found earlier:

/usr/bin/siglent/usr/mass_storage/U-disk0

[Kibabalu]

 you are right

[Bicurico]

Copy the files to USB, insert USB and reboot SSA.

1) Copy files from ZIP to an "upgrade" folder in the root of USB
2) Connect via telnet/serial and you should find the files on /usr/bin/siglent/usr/mass-storage/U-disk0
3) Do the mount and sync commands
4) Use cp -r upgrade /usr/bin/siglent/usr/usr to copy the upgrade folder on USB
5) sync
6) run upgrade.sh as explained before

[Kibabalu]

tuburlanut, tv84 and Bicurio,

Thanks a lot to you.

It's booting now.

If you are ever in Stuttgart, don't hesitate to contact me. I'll try to give you a little bit back from the joy I'm feeling in this moment!

[tubularnut]

Excellent 

[tautech]

Nice work chaps.