Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade boot firmware for ST mp1 platform in demo. #5

Open
wmamills opened this issue Jul 23, 2024 · 3 comments
Open

Upgrade boot firmware for ST mp1 platform in demo. #5

wmamills opened this issue Jul 23, 2024 · 3 comments
Assignees

Comments

@wmamills
Copy link
Collaborator

The ST demo is still using the boot firmware from OpenAMP v2023.10
There is no know issue with upgrading it, it just did not get done.

Consideration should be made to improving the method of creating the ST sdcard or template.
ST has scripts that can be used or the newer capabilities of make-image-target could be used.

@arnopo
Copy link
Collaborator

arnopo commented Jul 25, 2024

The ST demo is still using the boot firmware from OpenAMP v2023.10 There is no know issue with upgrading it, it just did not get done.

Update of software component are associated to the update to Yocto scarthgap
See OpenAMP/openamp-docs#35 for details
No plan yet to update software components version for nanbield.

Consideration should be made to improving the method of creating the ST sdcard or template. ST has scripts that can be used or the newer capabilities of make-image-target could be used.

could you detail what you have in mind? Yocto generates the wic image , at least in the ST distribution

@wmamills wmamills self-assigned this Jul 31, 2024
@wmamills
Copy link
Collaborator Author

I am talking about the generic-armv7a images here, not the ST reference image.

For generic images the OS image is built independent of the boot firmware.
For kv260 this is simple as boot firmware is on SPI-NOR and OS image is on SD Card.
For ZCU102 this means using MSDOS partition table and adding boot.bin to the ESP(EFI) dir

For ST platforms it is a bit more complex. Last time I just created a "template" that had the needed partitions and a blank VFAT partition that I populated. This is similar to how we tested generic OS images on LAVA.

I ran out of time to update this template this time so I just used the one from last time.

I also wanted to look at improving this process to see if we could create the needed partitions on the fly from firmware components already deployed. There are several methods to do this (wic, ST scripts, my make-image-targets). I just need to figure out which one fits into the flow best.

@wmamills
Copy link
Collaborator Author

(and YES we have the updated firmware components built from scarthgap. The ST reference build is used to get the boot firmware. The Xilinx reference build is also used to get the boot firmware for Zynqmp platforms.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants