Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

RTOS/TMDX654IDKEVM: SBL MCU R5F application loading issue from NOR OSPI flash

$
0
0

Part Number:TMDX654IDKEVM

Tool/software: TI-RTOS

Hello All,

I have problem with running application on R5 core, from the OSPI NOR flash on TI TMDX654IDKEVM board, via SBL from PDK.

My configuration is:

CCS ver 8.3.0
Windows version - Windows 10 Pro version 1803
PDK - pdk_am65xx_1_0_3
OSPI NOR Flash on TMDX654IDKEVM
Uniflash Tool 4.5.0 f (i tried to use 4.6.0 version but it didn't work. But with version 4.5.0 and it works ok)

I use Uniflash Tool 4.5.0 to download SBL, sysfw.bin and app to OSPI flash. The all procedure is described at the folowing links:
e2e.ti.com/.../2852484
origin-e2e.ti.com/.../2803770

For testing i used "GPIO_LedBlink_TestApp" TI SDK Example. I built this example for boath cores, A53 and R5, as instucted in Processor SDK RTOS 05_02_00_10 wiki [6.5.3. Building GPIO examples](software-dl.ti.com/.../index_device_drv.html
On the folowing path "C:\ti\pdk_am65xx_1_0_3\packages\ti\binary\GPIO_LedBlink_TestApp\bin\am65xx_idk" are generated .out files for R5 ("GPIO_LedBlink_am65xx_idk_mcu1_0TestApp_release.xer5f") and A53 ("GPIO_LedBlink_am65xx_idk_mpu1_0TestApp_release.xa53fg") core

Then i used "pdkAppImageCreate.bat" script to generate a separate app files for A53 and R5 core. By calling

Boot switches are set for primary OSPI NOR flash boot.

Then, as I mentioned, i used Uniflash Tool 4.5.0 to download SBL to address 0x0, sysfw.bin to address 0x40000 and app file to address 0xA0000 at OSPI NOR Flash.
I used original sysfw.bin and SBL for OSPI NOR boot, from PDK:
SBL: (C:/ti/pdk_am65xx_1_0_3/packages/ti/boot/sbl/binary/am65xx_idk/ospi/bin/sbl_ospi_img_mcu1_0_release.tiimage)
Sysfw.bin: (C:/ti/pdk_am65xx_1_0_3/packages/ti/drv/sciclient/soc/V0/sysfw.bin)

First i download app for core A53. And I got the next result:

  • Led LD18 on IDK board is blinking
  • Message on UART console output(MPU UART) is:

"IntConfig: portNum[0],pinNum[0],bankNum[0], intNum[712]
GPIO Led Blink Application

All tests have passed"

Then i download app for core R5. But I didn't get any result:

  • Led LD18 on IDK board is NOT blinking
  • Message on UART console output (MCU UART):

SYSFW ver 18.10.0-v2018.10 (Curious Crow) running
SBL Revision: 01.00.09.02 (Dec 20 2018 - 05:13:40)

I don't get any messages from the app.

Then i try to test app for both cores, A53 and R5, by using SD card.

  • I prepared SD card by copying tiboot3.bin and sysfw.bin from pdk
  • Boot switches are set for primary SD card boot.
  • First i put app for A53 core and everything works. (Led is blinking and on MPU UART i have Message)
  • Then i put app for R5 core and everything works. (Led is blinking and on second COM port i have Message)

With little debugging of SBL I found out that the entry point for core A53(MPU1_CPU0) is 0x7001b428, and for R5(MCU1_CPU0) is 0x00000000.
As R5(MCU1_CPU0) core is the one responsible for executing SBL, maybe this is some problem with entry point for this core.
Also, the problem may be copying the app file(for R5 core) to the wrong address in TCM memory?

Has anyone experienced similar problem?

Best regards,
Novica


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>