Getting stuck at Booting BL31 while booting goldvip image

[Priyanka_30]

we built the Goldvip image as suggested in Goldvip-user-manual , but when we try to boot it , it gets stuck in Booting BL31

when we flash the Goldvip image from NXP website to SD card , it creates 4 partitions . But When we flash our custom built Goldvip (followed steps as per the Goldvip manual Section 19 ) to sd-card it creates only 3 partitions 

NOTICE:  Reset status: Power-On Reset  

NOTICE:  BL2: v2.5(release):bsp33.0.hf1-2.5-dirty

NOTICE:  BL2: Built : 13:14:01, Aug 11 2022

NOTICE:  BL2: Booting BL31

The logs are attached for reference. Please suggest any possible way to fix it.

[MayanksPatel]

Hi @Priyanka_30,

I did the same in my local setup and it works fine. 

Please share the changes you did in conf/local.conf file.

Also, share the memory card partition image here for a better understanding of partitions.

Thanks,

Mayank s Patel

[Priyanka_30]

Hi @MayanksPatel 

Please find below changes from attached file.

For memory card partition, 1 partition is happening for boot and 2 other extra partitions, ideally it should be 4 partition, but its only 3.

[MayanksPatel]

Hi @Priyanka_30,

Please add the following line in the local.conf file.

IMAGE_INSTALL_append +=" apt"

Try after adding this and testing it.

Also, share the partition screenshot of the prebuilt image and custom image after flashing it into the memory card.

There is a utility "disks" in Linux which will help to show partition type and its details.

Thanks,

Mayank s Patel

[Priyanka_30]

Hi @MayanksPatel,

Yesterday also after doing changes Booting BL31 loaded but for  apt update we are getting some errors.

Reference Logs : 
apt-get update
Reading package lists... Error!
W: No sandbox user '_apt' on the system, can not drop privileges
E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory)
E: Could not open file - open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened.

And we are not able to see Domu created logs are attached in attachment.

[gmocanu]

Hello,

According to the boot logs you attached, you use an incorrect PFE FW image:

[    3.478588] pfeng 46000000.pfe: ERR: (DRIVER) event 1 - Driver runtime error: [pfe_pe.c:1894] Unsupported firmware detected: Found revision 1.3.0 (fwAPI:e1cb376b67fa4d1de800b132b328b42c), required fwAPI 9

Please download the correct PFE FW version, as referenced in the GoldVIP User Manual under the Software and Hardware Prerequisites chapter.

The creation of the xenbr0 and v2xbr (the bridges referenced in the V2Xdomu configuration file) have the pre-up target dependent on the existence of some PFE interfaces. From the other logs, one can notice the lack of those network bridges, therefore the spawn of the V2Xdomu VM will fail.

Best regards,
George

[MayanksPatel]

Hi @Priyanka_30,

You would need to add the package classes for ipk. You may add this to the already existing PACKAGE_CLASSES variable in the local.conf file. debian package management went wrong while packing the lib32 into rootfs file.

PACKAGE_CLASSES ?= "package_rpm package_ipk"

EXTRA_IMAGE_FEATURES += " package-management"

IMAGE_INSTALL_append = " opkg "

Hope this helps.

Thanks,

Mayank s Patel

[MayanksPatel]

Hi @Priyanka_30,

I am looking into this and trying to reproduce the issue.

I will get back to you with updates.

Thanks,

Mayank s Patel

[MayanksPatel]

Hi @Priyanka_30,

Thank you for reaching out to us.

Can you please share which GOLDVIP Release you are using?

Also, Please share the steps which you used for flashing and share the details of the custom image and for that what changes you incorporated on top of the GOLDVIP repo.

Thanks,

Mayank s Patel

[Priyanka_30]

Hi @MayanksPatel , 

Thanks for replying.

we used goldvip V 1.5 release to custom build and we added package-manager in the local.conf file to include apt-get package manager.