We are using Yocto Scarthgap for a new imx93 board. We have a SOM that is very similar to the NXP SOM on the EVK, to the point that if I put the SDIO card for the EVK into our board it will boot.
To avoid the annoyances of dealing with Yocto, I pulled u-boot-imx out and made it a stand-alone build using the SDK from Yocto. I can successfully build u-boot for the EVK and it boots.
So I for our board I:
And now I have and SDIO card I should be able to boot with...but nothing happens, nothing on the console. If I follow this same process but use imx93-evk it will work on our board and boot.
For flash.bin, the EVK is 24,576 bytes larger than for NIMBUS, so I fee like I'm missing something. Bl31.bin, tee.bin and mx93a1-ahab-container.img are all present.
I tried an image that used the EVK u-boot-spl.bin and NIMBUS u-boot.bin; the SPL came up but then got stuck when it tried to run U-BOOT.
Please Help!
Thanks for the quick reply...
My problem turned out to be a missing device tree file. The EVK has a file named "imx93-11x11-evk-u-boot.dtsi"; I have never heard of this file or seen it in any documentation in creating a new target. This file appears to describe the multi-file container. I copied the EVK file and changed the name to my new target, built and it booted.
Hopefully this post will help someone in the future when they come across the same issue.
Hello @davidpatton
I hope you are doing very well.
The general steps to generate the correct flash.bin are in chapter 3.1.1 How to build U-Boot in standalone environment of the i.MX Porting Guide.
And you can see the specific steps on chapter 4.5.13 How to build imx-boot image by using imx-mkimage of i.MX Linux User's Guide.
Specific steps for i.MX93:
You will find all the necessary packages on the table 3. BSP and multimedia standard packages of the i.MX Linux Release Notes.
Best regards,
Salas.