TMDS64EVM: Application Not Running After Flashing via UART Boot Mode

Michael V

Intellectual 606 points

Part Number: TMDS64EVM
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

Hello,

It appears that I took to long to respond so the previous thread was locked, but

I am still trying to boot an application using OSPI boot on the TMDS64EVM.

Flash programming completes successfully, however the application does not start after power-on.

Reference:

AM64x MCU+ SDK: Flash a Hello World example

Tools/Files used:

Flash application (for programming):
- Path: ...\tools\boot\sbl_prebuilt\am64x-evm
- File: sbl_uart_uniflash.release.hs_fs.tiimage

OSPI bootloader (executed first at boot):
- Path: ...\tools\boot\sbl_prebuilt\am64x-evm
- File: sbl_ospi.release.hs_fs.tiimage

User application (application to be programmed):
- Path: {CCS project directory}\Debug
- File: uart_echo_callback_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs

Flash configuration file (edited):
- Path: ...\tools\boot\sbl_prebuilt\am64x-evm
- File: default_sbl_ospi.cfg

Observed behavior:

- After flashing, the board is switched to OSPI boot mode and powered ON, but the application does not start.

- It appears that the OSPI SBL is not being executed after reset, or that execution does not proceed to the stage where the R5F core is released.

- When debugging with CCS, the R5F core starts execution, but when booting from flash, the R5F core does not seem to start.

- In CCS debug mode, MAIN_Cortex_R5_0_0 initially enters HALTED, and transitions to RUNNING after clicking “Continue”.

- When powering ON without CCS after flashing, LD22 remains OFF.

Although flashing completes successfully, the boot behavior differs between CCS debug execution and standalone OSPI boot.

The possibility of debug and release versions being mixed is currently being explored, but in parallel

I have a request.

Could you please advise on:

1) Possible root causes for this behavior

2) Required settings or conditions for ROM to execute the OSPI SBL and start the R5F core correctly

I appreciate your assistance, and look forward to your response.

Michael

5 months ago

0 Meet Thakar 5 months ago

TI__Mastermind 24325 points

Hi Michael,

As I mentioned in the previous thread, I flashed the same binaries on my EVM and could boot the SoC without any issues, so this is not expected. Please share your SBL Project that is causing this issue, If you are using the prebuild SBL then the issue is most likely with your UART application, please share the UART application you are flashing as well.

Best Regards,

Meet.

0 Michael V 5 months ago in reply to Meet Thakar

Intellectual 606 points

Hi Meet,

Thank you for your reply.

We were able to confirm that the SoC boots correctly when using the SDK’s default UART echo callback example, and that the issue occurs when transitioning to a custom UART application.

At this point, I would appreciate your guidance on identifying the root cause, so that a custom project can be implemented without reintroducing the same issue.

In particular, are there any SysConfig settings that require special attention when moving away from the default UART example — especially within the Memory Configurator section (e.g., memory regions, non‑cacheable regions, linker‑related settings, etc)?

If reviewing the full SysConfig file would be helpful, I am willing to share it via a private channel. Please let me know if private sharing is possible.

I look forward to your continued support.

Best regards,
Michael

0 Meet Thakar 5 months ago in reply to Michael V

TI__Mastermind 24325 points

Hi,

SBL is not able to boot your custom image, are you using the default makefile provided with SDK or you have a custom build setup? Could share your application image or if possible the entire UART example? You can share these via a private message.

You can also debug the SBL by referring to the guide I shared previously: [FAQ] AM62X/AM64X : [FAQ] Debugging SBL boot in RTOS SDK and figure out where exactly the SBL is stuck.

0 Michael V 5 months ago in reply to Meet Thakar

Intellectual 606 points

Hi Meet,

For some reason, I was unable to accept your request, so I sent one of my own.

Once accepted, I will send you over the application image.

Best regards,

Michael

0 Meet Thakar 5 months ago in reply to Michael V

TI__Mastermind 24325 points

Hi Michael,

I have accepted the request, please share the application image.

Best Regards,

Meet.

0 Michael V 5 months ago in reply to Meet Thakar

Intellectual 606 points

Hi Meet,

I was able to share the application image via private message.

Best regards,

Michael

0 Meet Thakar 5 months ago in reply to Michael V

TI__Mastermind 24325 points

Hi Michael,

I see that you are placing your application at 0x7000000 address in the MSRAM, this is the issue, please refer to this: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/12_00_00_27/exports/docs/api_guide_am64x/MEMORY_MAP.html

As mentioned here, the first 2 banks are reserved for SBL, so if you place your application code here then SBL will overwrite itself when loading the application, leading to the issue you are observing.

Best Regards,

Meet.

0 O.H 4 months ago in reply to Meet Thakar

Mastermind 7270 points

Hi Meet,

I'm Michael's colleague. I'm contacting you because he's temporarily out of the office.

Meet Thakar said:
I see that you are placing your application at 0x7000000 address in the MSRAM, this is the issue, please refer to this: https://software-dl.ti.com/mcu-plus-sdk/esd/AM64X/12_00_00_27/exports/docs/api_guide_am64x/MEMORY_MAP.html

We tried moving to 0x700C0000, but the problem persists. Please let me know if I've overlooked anything or if any information is missing.

Best regards,
O.H

0 Meet Thakar 4 months ago in reply to O.H

TI__Mastermind 24325 points

Hi,

Are you facing the same issue here as well, could you share the boot logs?

Please share your new appimage as well, if possible please share the entire project or the linker.cmd file at least.

Best Regards,

Meet.

Processors

Processors forum

TMDS64EVM: Application Not Running After Flashing via UART Boot Mode