Request for Assistance with Verdin AM62 Board and Dahila Carrier Board

[aliou]

I am reaching out for assistance with two issues I am encountering with my Verdin AM62 board and Dahila carrier board. I am currently working on a thesis project, and I am facing challenges that are blocking my progress.

1. Issue with UART/JTAG Port and CCS : I am trying to work directly with the Cortex-M4 core of the board through the UART/JTAG port, but unfortunately, CCS does not recognize my connection. Additionally, I am unable to flash the initial configuration file. Could you please guide me on the correct procedure to resolve this issue?
2. Issue with Splash Screen Display in U-Boot : I have followed all the necessary commands to configure and display a BMP image via U-Boot, but the image is not activated during the boot process. I can execute the BMP display. Could you explain how to correctly enable the splash screen display at U-Boot startup?

These two issues are major roadblocks in my project, and your support would be highly appreciated to help me move forward.

Thank you in advance for your assistance.
Verdin AM62 Board
Dahila Carrier Board

[ToradexAI]

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

Did you like my answer?

---

Hello,

Thank you for reaching out with your questions regarding the Verdin AM62 board and Dahlia carrier board. Let’s address each of your issues step by step:

1. UART/JTAG Port and CCS Connection Issue:

   • Configuration Check: Ensure that Code Composer Studio (CCS) is correctly configured for the AM62. Verify that you have installed the necessary drivers and support packages specific to the AM62 from Texas Instruments. The target configuration in CCS should match your hardware setup.
   • Processor SDK: Consider setting up the Processor SDK from Texas Instruments, which includes tools and examples for working with the Cortex-M4 core. Follow the setup instructions carefully to ensure all components are correctly installed.
   • RemoteProc and RPMsg: If you are using RemoteProc to manage the Cortex-M4, ensure it is properly configured. Texas Instruments provides documentation on setting up and using RemoteProc and RPMsg for inter-core communication.

2. Splash Screen Display in U-Boot:

   • BMP File Verification: Make sure the BMP image file is correctly formatted and accessible by U-Boot. It should be in a supported format and located in a directory that U-Boot can access during boot.
   • U-Boot Environment Variables: Check the U-Boot environment variables related to splash screen configuration. You may need to set variables such as splashimage and splashpos to specify the image location and position on the screen.
   • U-Boot Commands: Ensure that the commands to load and display the BMP image are correctly included in the U-Boot boot script. You might need to modify the boot script to include these commands if they are not already present.

I hope these suggestions help you resolve the issues with your Verdin AM62 board and Dahlia carrier board. If you have further questions, feel free to ask.

Best regards,
Toradex AI Assistant

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

TI AM62 Computer on Module - Verdin AM62

Connection Issue to Core M4F1 on AM62 Micro via XDS110

I’m currently facing an issue while trying to connect to the Core M4F1 of the AM62 micro through XDS110, following the procedure outlined in the provided [AM62x MCU+ SDK: CCS Launch, Load and Run]. When attempting to connect to the core, I receive the following error message: Error connecting to the target: (Error -1274 @ 0x0) Error encountered during connect sequence. The specific reason is unknown but may be the result of trying to access a Core or logic that is inaccessible due to a lack o…

Fast splash screen on Verdin AM62.

[srzm]

I have a Dahlia board and I faced the splash screen display issue before.

The device tree is set to Verdin Development Board and not to Dahlia board. Since you’re already in the u-boot, do this:

• set fdt_board to dahlia using setenv ,
• use saveenv to store from RAM into flash,
• delete the fdtfile because preboot will not change the fdtfile unless empty.

Not sure if that’ll solve your other issue, but try it.

Below is what it looked like in my u-boot (# is the shell, not a comment):

Verdin iMX8MP # printenv fdt_board
fdt_board=dev

Verdin iMX8MP # setenv fdt_board dahlia

Verdin iMX8MP # printenv fdt_board
fdt_board=dahlia

Verdin iMX8MP # printenv fdtfile
fdtfile=imx8mp-verdin-wifi-dev.dtb

Verdin iMX8MP # setenv fdtfile

Verdin iMX8MP # saveenv
Saving Environment to MMC... Writing to MMC(2)... OK

Verdin iMX8MP # reset