• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 84 subscribers
  • Views 539 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.

LAUNCHXL-F28379D: Cores don't automatically start after loading the Flash Image using uniflash

Jay Amlani
Prodigy 115 points

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE, UNIFLASH

Hi,

When I am manually debugging the LAUNCHXL-F28379D using CCS, I need to start each core manually. But I want this to be automated, so now I am using Uni-flash where I have enabled "Run Target After Program Load/Flash Operation".


But the cores don't start automatically, I get successful message but the core is not running. 

10/4/2023, 2:20:59 PM] [INFO] Executing Reset: CPU Reset
[10/4/2023, 2:21:00 PM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
[10/4/2023, 2:21:00 PM] [INFO] C28xx_CPU2: GEL Output: Memory Map Initialization Complete
[10/4/2023, 2:21:18 PM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
[10/4/2023, 2:21:18 PM] [INFO] C28xx_CPU2: GEL Output: Memory Map Initialization Complete
[10/4/2023, 2:21:55 PM] [SUCCESS] Program Load completed successfully.
  • 0
    TI__Guru* 87155 points

    Hi Jay,

    Are you using a hex file Or a .out file?

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Prodigy 115 points

    I am using .out file

  • 0 in reply to Jay Amlani
    TI__Guru* 87155 points

    Hi Jay,

    I remember seeing a similar debug discussion in the recent times from our CCS team.

    In the Reset Actions, can you enable CPU reset after program Load option and disable the option "Remain Connected after the flash operations" (this is available when you select the C28xx_CPU1" core at the top right corner of the GUI.

    Let me know if it helps.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Prodigy 115 points

    Hi Vamsi,

    I tried your suggestion, but even this does not help me. I even tried power cycle reset by manually removing the cable and attaching it again. Still does not work.

    I am using __standalone parameter in the CPU 1's  predefined symbol. Do you think that could have something to do with this issue?

    Thank you,

    Jay

  • 0 in reply to Jay Amlani
    Prodigy 115 points

    Hi,

    Is there something else I can try, I am still stuck with this issue?

  • 0 in reply to Jay Amlani
    TI__Genius 13365 points

    Jay,

    I started looking at this issue to see if I can reproduce it. I will get back to you soon with suggestions or further questions.

    Thanks,

    Ricky

  • 0 in reply to Jay Amlani
    TI__Genius 13365 points

    Jay,

    I just tried the following on my LAUNCHXL-F28379D.

    1. Compiled the blinkyled_driverlib example from C2000Ware for flash memory in CCS

    2. Start UniFlash, configure for LAUNCHXL-F28379D, and make sure the "Run Target After Program Load/Flash Operation" option is checked

    3. Load the compiled .out file

    4. Observe that the LED on the LaunchPad is blinking

    5. Turn off "Run Target After Program Load/Flash Operation"

    6. Reload the .out file

    7. Observe the LED is not blinking

    All these steps are working for me. 

    I attached the .out file I tried. Can you see if you get the same behaviour on your board as well?https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/blinkled_5F00_driverlib_5F00_lp_5F00_f2837xd.out

    Thanks,

    Ricky