TMDS243EVM: Boot From Flash And DFU

Hi Hao,

Hao Wang said:

I think I have successfully loaded the program using DFU to flash, because the log gave expected output as manual d

I assume you are following the steps describe here: https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/10_01_00_32/exports/docs/api_guide_am243x/GETTING_STARTED_FLASH_DFU.html#autotoc_md65

Using this you should be able to successfully flash and boot the program from OSPI, assuming you have set the bootmode pins correctly. Please recheck and verify the same. Please also attach the flashing logs, so I can check if something was missed there.

Hao Wang said:

I have also tried to load the program directly to RAM by DFU and boot from DFU, get nothing either.

Which commands have you used for this? Was there any error while DFU transfer, or the Download was successful but you there were no logs printed in the UART  terminal?

Best Regards,

Meet.

Meet

I followed the steps in the manual you described.

Both of the appimage and appimage_xip are loaded.

This is the log for flash loading.

I think the loading is successfully.

But when set the boot mode to OSPI mode, the UART terminal gave the output as below.

I can confirm the boot mode is set correctly. It looked the OSPI mode cannot boot.

Regarding to DFU direct loading.

I also followed the commends described in manual, to send bootloader image firstly and then send application image.

But the UART terminal again gave below. The board cannot boot from DFU either.

Thanks for any suggestions.

Thanks & Best regards

Hao (Wang hao)

Hi Hao,

I can see from the logs that you are flashing the .appimage, you have to flash the HS-FS appimage for this (.appimage,hs_fs). Flashing the wrong image is causing this issue, could you please retry with the HS-FS binary.

Best Regards,

Meet.

Meet

I can confirm I loaded the hs_fs image for SBL.

Do you mean hs_fs for appimage?

When I search Workspace Debug folder, there is no hs_fs image file.

Can you please suggest which file is the right one?

Thanks.

Thanks & Best regards

Hao (Wang hao)

Hi,

Hao Wang said:

Do you mean hs_fs for appimage?

That is correct you have to use the HS-FS binary for the application image.

Hao Wang said:

When I search Workspace Debug folder, there is no hs_fs image file.

hs_fs image should have been generated by default, I am not sure why it is not the case for you. Could you share your makefile, let me know if you have done any changes. The GP support is dropped since SDK version 09.00.00, as you are using 09.02.00 the GP binary (.appimage) shouldn't be generated and you should be able to see the HS-FS binary after building the example.

Also let me know which CCS version you are using.

Best Regards,

Meet.

Meet

I just built the project from CCS.

I am using CCS12.8.1.

I have also built in Release mode, it again gave me appimage in Release folder as built in Debug mode.

Do you suggest build with makefile?

Thanks.

Thanks & Best regards

Hao (Wang hao)

Hi,

Hao Wang said:

Do you suggest build with makefile?

Yes, I would suggest that you can try that and see if HS-FS binary is being gernerated using the makefile.

Please also attach the CCS makefile, so I can check if any step is missed in your makefile due to which the .appimage.hs_fs doesn't get generated: It will be named as makefile_ccs_bootimage_gen in your CCS project folder.

Best Regards,

Meet.

Meet

Please see the make file.

makefile_ccs_bootimage_gen

Thanks.

Thanks & Best regards

Hao (Wang hao)

Hao,

This CCS makefile is correct. Could you try to build this example from SDK makefile and see if that generated the HS-FS image?

Meet

I tried to build by makefile.

It gave me below result.

This lists all the files in the ti-arm-clang folder. I have copied the example.syscfg file into it.

Do we need a gmake version for Win10 64bit system?

Will you please help to identify?

Thanks a lot.

Thanks & Best regards

Hao (Wang hao)

Hi Hao,

example.syscfg has to be in the r5fss0-0_nortos folder, not the ti-arm-clang folder.