Part Number: AM2432
Other Parts Discussed in Thread: UNIFLASH, AM2434
Hello Champs,
My customer built the firmware that working well on RAM. but they cannot download it to launchpad flash.
My customer is using ind_comms_sdk_am243x_09.00.00.03.
They followed the flashing procedure in this URL
Here’s the detailed issue Working with an ind comms 9.00.00.03 SDK code for the the AM243x LP board, and the following phenomena occurred after attempting a Flash download.
Working with CCS version 12.7.1
After connecting RAPIEnet SDK debug in CCS, it operated normally when checked (OSPI BOOT mode)
>When debugging in CCS, the program is loaded and operated via System Reset -> Load Program
After removing power from the board, changed the switch to UART BOOT MODE
Proceeded with the Flash download by referring to the Flash-related download procedure on the TI AM243x MCU+SDK 09.00.00.03 web page
>Proceeded using uart_uniflash.py in the Windows Command Prompt (cmd.exe)
>No errors occurred during progress in the Cmd window (confirmed the message that it was downloaded normally)
After the Flash download was complete, changed the pins to OSPI BOOT mode
When the AM243x LP board is powered on without a CCS connection, it performs abnormally
When checking with the Uart Terminal in the Debug screen by connecting CCS:
[00:00:00.009,604] main: AM243x BOOT S/W Version 1. 1(Release), after this log is output, there is no further output
When pausing debugging in the Debug screen after connecting CCS, an Abort occurs due to Hwip Data Abort or Hwip Prefetch Abort
>Code execution is impossible thereafter
Prior to the first Flash download attempt, it executed normally via Debug connection in CCS. However, since the first Flash download attempt, both OSPI standalone booting and Debug connection execution have become impossible. Therefore, I suspect that the board-related configurations were corrupted during the Flash download process.
First of all, it seems that the process is entering the APP Image side, but seeing as it stops almost immediately upon entry, I suspect a DDR-related access issue or an SBL-related initialization problem.
The TI SDK used is ind_comms_sdk_am243x_09_00_00_03, so I used the sbl tiimage file located under the directory:
(TI SDK installation path)\mcu_plus_sdk\tools\boot\sbl_prebuilt\am243x-lp.
I am wondering if this is occurring because this file does not match the current TI board settings.
Looking at the .ccxml file currently under the targetConfigs folder, the Board type is set to AM2434_ALX.
Do you have any suggestion for this? Can using uniflash be the solution?
