• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 335 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.

TMS570LC4357: muxInit fails after POR while using Bootloader+RTOS

tanmoy deb
Prodigy 20 points
Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN

Dear Team, 

I am facing a strange issue. 

I have made a bootloader over CAN using the reference code. Due to using the Exception vector, I have update updated the same in the Bootloader also. 

The application is running with FreeRTOS and it has some pin muxing from the HALCoGen tookl. Like some peripheral pins I have converted into GPIO etc. 

While using the application at 0x00000000 address it works fine. And while using the 0x10020 address for the application, I observe the muxInit fails while POR (without debugger). With the debugger it works fine. 

Please help to solve it.

  • 0
    TI__Guru**** 196776 points

    Hi Tanmoy,

    Does the code execution jumps the Application from Bootloader successfully? 

    tanmoy deb said:
    I observe the muxInit fails while POR (without debugger)

    Is the pinmux not configured properly? or the code gets stuck in this init function? Did you print some debug information from Application muxInit()? 

  • 0 in reply to QJ Wang
    Prodigy 20 points

    Yes, the jumping from Bootloader to Application happens now successfully. Thanks for your input. 

    While debugging this problem, i found that the system_init->muxInit gets called in the _c_int00 function; and it gets called while debugger attached, or the application is on the 0x0000_0000 address. 

    I also observe the SW Reset does not enable the MuxInit properly. 

    Also I have plan to use Watchdog reset, SW reset, i see the system_init never gets called in those. Please suggest some holistic solution so that the generated BSP can work with every scenarios - POR with bootloader, SW Reset, Watchdog reset. 

    Please help to resolve the issue.