AM2432: Uart Flash SOC Initialization Binary Failed on LP-AM243 EVM

Hi Vaibhav,

Thanks for your reply, sorry there is a misunderstanding for you, when customer took the picture of the EVM they did not change the bootmode yet, and when they start the testing, actually they did set the bootmode according to our guide below.

And to double confirm it, customer could see the "CCCCCCC" output in the UART terminal, which means the bootmode setting should be correct.

Customer mentioned this EVM has been used by their colleague before, so we doubt that the OSPI flash is not empty, and maybe we need erase it. May I know do we have some reference guide about how to erase the OSPI flash?

Thanks,

Kevin

Try to erase the entire flash by writing this in the config file.

Hi Vaibhav,

Thanks for your help.

However, after modifying the config file, customer feedback that it stuck at executing command 2 of 2, and will not execute the following erase command.

--operation=erase --erase-size=67108864  --flash-offset=0x0

This problem only happens on the EVM board, customer feedback that they tried add the same erase command for their own development board, these development board will successfully erase the OSPI flash and flash the new image.

Customer switched the bootmode to OSPI boot on this EVM board, and they could see the log below.

And according to the guide below, we could now the EVM has been flashed before, but the strange point is that it could not be erased.

And the error log shows that it stuck when executing sbl_null.release.hs_fs.tiimage, may I know would that because previously customer flashed an "incorrect" sbl_null.release.hs_fs.tiimage causing this problem and is there any other way to reflash this image?

Thanks,

Kevin

Kevin Peng said:

customer feedback that they tried add the same erase command for their own development board, these development board will successfully erase the OSPI flash and flash the new image.

Good to know about this.

So to summarize, it works on the customer's board, but not on the TI AM243-LP EVM?

If this is the case, I am not sure, how old the EVM is and what is the type of SoC in play.

Please check the device type here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228618/faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp

If device type is GP then proceed to flash the GP images else HS FS images.

Can you confirm this real quick so that we can move forward.

It is for sure, that the customer's board is having the a SoC which is HS FS but what about the TI EVM one?

Regards,

Vaibhav

Hi Vaibhav,

The type of the EVM board is below.

The OPN is LP-AM243

The PCB is PROC109A

The AM24 PN shown in the EVM is AM2434BSFFHIALX

So it is HS-FS, and customer is trying to flash HS image.

Thanks,

Kevin

Hi Vaibhav,

We have followed your guide & got that the device type is HS-FS.

Hence this problem might not be the "incorrect" image using, customer is using the HS image.

Thanks,

Kevin

Hi,

Thanks for your patience.

Kevin Peng said:

customer is using the HS image.

I am assuming you meant HS FS Image.

Here is what we can do as a part of the next step:

1. Open the file SBL Null: C:\ti\mcu_plus_sdk_am243x_10_00_00_20\examples\drivers\boot\sbl_null\am243x-lp\r5fss0-0_nortos\main.c
2. Introduce loop_forever() after int32_t status;
3. Rebuild the application in debug mode and not release mode so that we can debug step by step.
4. Make sure to perform the uart unigflash step via the Python command and then when it gets stuck at Step 2 which is SBL Null.debug.tiimage(hs fs image)
5. Then, open CCS and connect to the R5F0_0 core and you will see that the flow is stuck at loop_forever().
6. Once you are at this point, simply set the value of loop = 0 inside loop_forever() and proceed to debug one line at a time.
7. Please do so, until you see some error happens at lets suppose a certain API. Please let me know the name of this API.

This would be a good way to find out where exactly things are going south.

Looking forward to your response.

Regards,

Vaibhav

Hi Vaibhav,

Thanks for your reply.

Customer is trying the above methods, but feedback that they will stuck at the below position, could you provide customer some clue to debug?

Thanks,

Kevin

Hi Kevin,

I want to clarify few more things:

Kevin Peng said:

• LP-AM243 EVM
• Their own development board made with AM2432

The Flash on the LP-AM243 is a Quad Flash.

Can you tell me if the flash on the custom board is a Octal or a Quad flash?

Regards,

Vaibhav

Hi Vaibhav,

The customer board is also Quad flash.

I sent my LP-AM243 to customer today, and customer could successfully flash on my EVM with the same steps.

So this problem is just specifically with the problem EVM board customer is having.

Do you think using any other flashing like CCS flashing would be helpful?

Thanks,

Kevin 

Hi Kevin,

Thanks for your patience.

Kevin Peng said:

I sent my LP-AM243 to customer today, and customer could successfully flash on my EVM with the same steps.

So this problem is just specifically with the problem EVM board customer is having.

To summarize, you sent the AM243-LP, to the customer, something like this below:

They were able to flash on it, but the AM243-LP the customer has, the flashing of the same files from the same config file, does not work?

I am assuming they are flashing the AM243-LP images if I am not wrong?

Regards,

Vaibhav