J721EXSOMXEVM: Error loading C66x example via remoteproc

Text above is mising the "_freertos" suffix on the make target for GPIO, it was there for the build.

Hi Thomas,

There are a few things that you need to take care when it comes to booting RTOS application alongside Linux. Please take a look at the FAQ https://e2e.ti.com/support/processors-group/processors/f/processors-forum/931992/faq-tda4vm-application-in-the-psdkra-runs-standalone-from-sbl-but-doesn-t-run-alongside-linux and make sure all these things are taken care of.

Regards,
Parth

I am from the same team as Tom. More information about the issue which emerged in the last hours:

We are hypothesising -EINVAL (-22) is returned by rproc_parse_fw() here https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/remoteproc_core.c?h=ti-linux-5.10.y#n1670 after find_table() cannot find a '.resource_table' section in the ELF file https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/remoteproc/remoteproc_elf_loader.c?h=ti-linux-5.10.y#n262

Using objdump we have verified that a '.resource_table' section is present in ipc_echo_test_freertos_c66xdsp_1_release_strip.xe66 which runs fine, but it is not present in GPIO_LedBlink_TestApp_freertos_c66xdsp_1_release_strip.xe66 which does not start.

Is this the cause if this issue?

Why is the resource table missing from GPIO_LedBlink_TestApp_freertos_c66xdsp_1_release_strip.xe66 ?

How can the example's makefile(s) be modified to add it?

Thank you

Regards

--

Delio

Hello Parth,

Thank you for your reply. I reviewed the FAQ and the documents linked by it but I cannot find documentation that shows how to take care of those details in practice. We are building the PDK examples on the command line following the ti-processor-sdk-rtos-j721e-evm-08_02_00_05 docs.

I would like to compare the build configuration for the `ipc_echo_test_freertos` example that work with the build configuration for  `GPIO_LedBlink_TestApp_freertos` that doesn't work and I expect that would reveal why the latter doesn't work and what changes to make in order for it to work. But I cannot find relevant documentation nor I can find the relevant files by looking at the directories under `ti-processor-sdk-rtos-j721e-evm-08_02_00_05/pdk_jacinto_08_02_00_21`. I am sure it's all there but it is like finding a needle in a haystack ;-)

Can anyone point us to the build configuration for `GPIO_LedBlink_TestApp_freertos` and `ipc_echo_test_freertos`  relative to the root of the PDK or point us to documentation that describes the directory layout so we can find it ourselves?

Thank you!

--

Delio

Hi Delio,

As of now we do not have the exact steps needed to run GPIO example. You can refer to the discussion https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1128500/tda4vm-uart-app-not-running-alongside-linux-for-mcu1_0. I have shared some patches showing what all things you need to pick from ipc test and how to use it. The patches are specific for UART App on mcu1_0, but similar approach applies to all the examples on any core. 

The general guidelines are:
1) Modify the linker files to make sure the code is loaded into the memory reserved by Linux
2) The GPIO instance being used in the example is disabled in the dts.
3) The resource table is linked
4) You do not need to include sci server as the app is not running on mcu1_0.

I'll also try to make it work on my end, but I'll need some time, meanwhile you can get started with the above steps. Please let me know if you need any clarifications.

Also, please mention which SDK version are you using.

Regards,
Parth

Parth,

Could you please expand on how we make sure "The resource table is linked"?

I've included the following in the linker command SECTIONS:

.resource_table:
{
__RESOURCE_TABLE = .;
} > 0xA6100000

But this doesn't cause the resource table to appear in the output file as it does in the echo example.

Thanks,

Tom

P.S.  We are using ti-processor-sdk-rtos-j721e-evm-08_02_00_05 which includes pdk_jacinto_08_02_00_05

Hi Thomas,

Can you please share a patch of changes that you have done?
Also, please mention which SDK version you are using?

Regards,
Parth