Our customer is trying the RTOS Template Application with TMDX654IDKEVM not TMDX654GPEVM. But it does not work and it fails in the GPIO initialization.
http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_examples_demos.html
Could you tell me how to modify the application to work with the TMDX654IDKEVM?
Best regards,
Daisuke
Hi,
There is only GP EVM example on AM654x, not IDK EVM. What is the software release you used for this? PRSDK 5.3? I recall there was GPIO toggling failure in 5.0 or 5.1 releases.
I just tested the rtos_template_app_am65xx_a53 on my AM654x IDK EVM A53 core, there is no issue. (The base board for GP and IDK are the same, the difference is the add-on Serdes and application board). GPIO is the basic module and the AM654x GP template app should expect to work on IDK EVM.
I saw a green LED is blinking (it is labeled as LD18, besides the PRU2 ETH0/1 RJ-45). When I halt the A53, it stopped blinking. So this should work.
Also my out file:
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/rtos_5F00_template_5F00_app_5F00_am65xx_5F00_a53.out
Regards, Eric
Hi Eric-san,
Thank you for your reply.
I tested the rtos_template_app_am65xx_a53.out that was attached by you on TMDX654GPEVM and reproduced the issue. Our CCS is version 8.3.0.00009, and the updates for device support and emulator support have been applied.
A53 Core 0 seems to be running in secure mode. Is it correct?
I am also concerned about hardware issues.
Is it correct to set all switchs (SW2, SW3 and SW4) for boot mode to OFF?
Does the latest RTOS SDK (Processor SDK v05.03.00.07) support the revision of our EVM?
Best regards,
Daisuke
Hi,
No, my case has "SEC OFF", see the screenshot.
The boot pin setup doesn't matter.
My board is also Rev E3, 3P0014.
Most likely, you used the GEL to initialize the board only WITHOUT loading DSMC firmware. You need to do this following: 
,
Topic:
Description
AM65x EVM users testing basic functionality like R5F and A53 bring up and DDR configuration can use the basic setup described in the previous section for setting up the EVM. However, advanced application level debug that uses resource management for UDMAs, interrupt setup, power management to setup clock modules, or wakeup/power of slave cores will require loading of SYSFW (DMSC Firmware) on the M3 core so that the application can make API calls to leverage its services.
Regards, Eric
Hi Eric-san,
Thank you for your reply.
The demo succeeds in the case with loading DSMC firmware, but fails in the case without loading DSMC firmware. My above post is the results in the case without loading DSMC firmware.
Both of my cases have "SEC on". Does it mean that High-Security device is implemented on my EVM?
Best regards,
Daisuke
Hi Eric-san,
Thank you for your reply.
I tested it for so far by using the rtos_template_app_am65xx_a53.out that was attached by you.
Sorry, I had a mistake. Their status remained in the old state because they were checked while running. When checked after suspend, they has been updated.
Best regards,
Daisuke
