This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VH-Q1: RTOS binary loading is confusing, how can I change it

Part Number: TDA4VH-Q1

Hello all,

I am using this board: https://www.ti.com/tool/J784S4XEVM

I always have issues understanding which "fw" is which.

How can I disable the loading of all this garbage "signed, fw-sec"?

I can live with the naming convention "j784s4-main-r5f0_0-fw" and "j784s4-main-r5f0_0-fw".

But this "j784s4-main-r5f0_0-fw-sec" is garbage, there is no mention of "sec" in the documentation: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-j784s4/09_00_01_03/exports/docs/linux/Foundational_Components_IPC_J784S4.html?highlight=j784s4%20main%20r5f0_0%20fw

I need to be able for playing around purpose to just compile a binary and I have it loaded to the corresponding core.

Also, the build process generates: .xer5f, appimage, appimage.signed. I do not need them, How can I make the bootloader recognize the .xer5f only, and have it load it.

I understand that there is some logic behind it, but because it is not clearly visible what is the logic, then it needs to be removed.

Please, my request, I have a .xerf5, and I want to copy it, make a link, ensure it is loaded. No -sec, appimage.signed. 

How can I do it? What must I do to the default LInux/bootloader to have it work this way. 

Br, Mircea