• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 552 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/AM5728: Application causes reboot

Vijay Pratap
Prodigy 120 points

Part Number: AM5728

Tool/software: TI-RTOS

Hi,

  I am configuring McASP as 32 channel TDMA slave and NIMU on AM572X evaluation Kit for DSP1 core (booting from SdCard using TiRTOS provided MLO).

Both the applications was working fine but when i tried merging both (as data is coming over UDP and passing it over McASP to other device), I found my AM572X board are getting rebooted after loading application ( below are the UART print (reboot is happening continuously)).

By any chance my software can over-write any registers which is causing this issue because I am suspecting one array that gone crazy.

I am using CCSv7.2.0.13, processor_sdk_rtos_am57xx_3_03_00_04, pdk_am57xx_1_0_6 and  ndk_2_25_01_11.

**** PDK SBL ****
**** Copying Application Image to DDR ****:
SD Boot - file open completed successfully
Version: CSII_v_1_2_0_0
MMDS Reset Done...
Configuring McBSP...
TDMA Rx SWI Created...
TDMA Tx SWI Created...
TDMA Task Created...
UDP Task Created...
Starting TiRTOS...

**** PDK SBL ****
**** Copying Application Image to DDR ****:
SD Boot - file open completed successfully 
Version: CSII_v_1_2_0_0

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0
    TI__Guru** 116870 points

    Vijay,

    Before you test the booting of the application, does the combined MCASP + NDK application run correctly when the .out (application) is loaded on the DSP over an emulator. I would verify the functionality over emulator before testing this under boot scenario.  Can you also provide the map file for the combined application for us to analyze.

    The other way to test this would be to connect to the DSP and ARM when no SD card is inserted then insert the SD card and run the SBL .out to see if the setup runs correctly. you can set a break point at the start of the SBL main function to catch where the code branched from.

    I also recommend looking at the application notes here and to confirm that when you combined the application that there are no interrupts/EDMA resource or memory overlap between app and the bootloader that could be the root cause of this issue.

    SPRAC93_final.pdf

    Hope this helps. Please share any new findings that you may have from the debug steps provided here so we can further analyze the issue or provide more next steps to root cause the issue.

    Regards,

    Rahul