Hi,
I am working on S32G GoldVIP and trying to test OTA update. I am trying use case given in user manual, when I am executing this command xl console v2xdomu it asks for login, there I have entered root then it throws error as below (also screen shot is attached).
Login incorrect
v2xdomu login:
Login timed out after 60 seconds.
[ 148.619255] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm init: checksumming directory block 0
[ 148.623298] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm init: checksumming directory block 0
[ 148.624720] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm init: checksumming directory block 0
[ 148.625832] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm init: checksumming directory block 0
[ 148.631557] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
[ 148.632798] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
[ 148.633782] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
[ 148.634756] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
[ 148.635715] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
[ 148.636593] EXT4-fs error (device xvda): __ext4_find_entry:1590: inode #25825: comm getty: checksumming directory block 0
Auto Linux BSP 39.0 v2xdomu hvc0
Please suggest the solution.
Thanks
Hi,
Which version of GoldVIP do you use ?
Which kind of image do you use ? The prebuilt image from GoldVIP package or the built image from yocto ?
Please, let us know.
Hi,
Thanks for your feedback. We don't see any GoldVIP BSP version 39.0. Commonly, GoldVIP versions are v1.x0, i.e. the newest one is v1.12.0, as shown under the Automotive Software Packages Manager:
Please, let us know.
Hi,
Thanks for your feedback. We have received the following update on regards the error you are seeing:
"...the command xl console v2xdomu is a known issue specified in the release notes. It causes the the console to hang, the alternative is to use ssh root@10.0.100.20 instead."
Still, we understand that moving to a different version is also another solution.
Please, let us know.
Hi,
Let us investigate further this situation. Once we have an update, we will let you know.
We apologize for any delay from our side.
Please, let us know.