U-boot customization for verdin am62

[naveenkumar.muthusam]

Hi all,

We are trying to customize the u-boot of verdin am62 for our custom board in which we want to remove the usb boot, ethernet boot as well as booting MMC1.

In usb boot we want to change the usb instance for usb-boot for updating the image in mmcblk0.

currently we have a workspace under build as u-boot-toradex-ti, but we are not finding any device tree files to do so.

and also kindly provide the information on how to test the new u-boot image after building.

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

To customize the U-Boot for your Verdin AM62 module and remove USB, Ethernet, and MMC1 boot options, you will need to modify the U-Boot configuration files rather than the device tree files. U-Boot boot options are typically controlled through configuration settings in the U-Boot source code.

Here are the steps you can follow:

1. Access U-Boot Configuration: Navigate to your U-Boot source directory, which you mentioned as u-boot-toradex-ti.

2. Modify Configuration Files: Look for the configuration header files, typically named include/configs/<board_name>.h. This file contains macros that define the boot options.

3. Disable Boot Options:

   • USB Boot: Locate and comment out or remove any macros related to USB boot, such as CONFIG_CMD_USB or CONFIG_USB_STORAGE.
   • Ethernet Boot: Similarly, find and disable macros like CONFIG_CMD_NET or CONFIG_NET.
   • MMC1 Boot: Look for CONFIG_MMC or CONFIG_CMD_MMC and adjust accordingly.

4. Rebuild U-Boot: After making these changes, rebuild U-Boot to apply the new configuration. Use the appropriate make commands for your setup, ensuring you target both the A53 and R5 processors if required.

5. Deploy the New U-Boot: Once built, deploy the new U-Boot binary to your module.

Device trees are primarily used for hardware configuration and peripheral setup, not for boot option management in U-Boot. Therefore, your focus should be on the U-Boot configuration files for this task.

By following these steps, you should be able to customize the U-Boot to meet your specific boot requirements for the Verdin AM62 module.

If you have any more questions, feel free to ask!

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Enable UART instead of 'Verdin CAN_1' on Verdin AM62

Hello Toradex Community I’m trying to disable the ‘Verdin CAN_1’ (aka main_mcan0) peripheral which uses the SODIMMs 20 and 22. My goal is to use the SODIMM 20 as UART5_RXD and SODIMM 22 as UART5_TDX instead. im working with the following setup: Verdin AM62 1GB WB IT (V1.1A) Verdin Development Board (V1.1F) TorizonCore Version: 6.5.0+build.8 Host-System Win 10 (WSL2) I’m relatively new to the Device-Tree game and used the the following tutorials/threads as a start: Device Tree Overlays on …

Flashing u-boot manually on verdin am62

I need to update u-boot on my verdin am62 module to improve boot time. I have patched u-boot and completed a Yocto build that produces new u-boot binaries. I have a few questions about how to proceed. In your documentation, you use these commands to update from within u-boot > tftpboot ${loadaddr} tiboot3-am62x-gp-verdin.bin > run update_tiboot3 > tftpboot ${loadaddr} tispl.bin > run update_tispl > tftpboot ${loadaddr} u-boot.img > run update_uboot However, in an image.json file I downlo…

Custom device tree.

[rudhi.tx]

Hi @naveenkumar.muthusam,

If I understand your question correctly, you want to modify the boot targets (either change the order in which the bootloader will look into targets or remove some of them) in the uboot environment. Is that the case? Do you have a specific reason why you want to remove USB, ethernet and MMC1 from the targets list?

Here we have instructions for how to build a custom Uboot from sources and deploy it: https://developer.toradex.com/linux-bsp/os-development/build-u-boot-and-linux-kernel-from-source-code/build-u-boot/#downstream
This is what I would recommend to try first: Build your uboot, deploy and test it before you add the patches into your Yocto build for the image.

Now regarding the file you need to modify to change the order of boot targets:
Currently, we have an include file per device. In there you can specify the U-Boot environment and also the boot devices. Here for example the verdin-imx8mp:
https://git.toradex.com/cgit/u-boot-toradex.git/tree/include/configs/verdin-imx8mp.h?h=toradex_imx_lf_v2024.04
The macro BOOT_TARGET_DEVICES will then create the boot target list. If you want to add for example USB as first boot source, you could do something like this:

diff --git a/include/configs/verdin-imx8mp.h b/include/configs/verdin-imx8mp.h
index bff417fdafb..80b4055cd97 100644
--- a/include/configs/verdin-imx8mp.h
+++ b/include/configs/verdin-imx8mp.h
@@ -30,6 +30,7 @@

 /* Enable Distro Boot */
 #define BOOT_TARGET_DEVICES(func) \
+       func(USB, usb, 0) \
        func(MMC, mmc, 1) \
        func(MMC, mmc, 2) \
        func(DHCP, dhcp, na)

This patch can then be added in your custom meta layer (meta-custom/recipes-bsp/u-boot) with a SRC_URI;append.