• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 537 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.

TMS320F28374S: DCAN peripheral can't receive/transmit while running in user Boot code

Benjamin Zhou
Expert 4000 points
Part Number: TMS320F28374S


Hi Team,

  My customer encountered an issue while using DCAN for firmware upgrade,   in Application, the DCAN worked well, which Tx/Rx & interrupt worked as expected, but jump from user application code to user bootloader,  the DCAN peripheral can't receive/transmit any data even can't trigger the interrupt,  while only run with bootloader code, this issue still existed.

  Customer used TMS320F28374SPTPT， and used GPIO4&5 for DCAN feature,

  Attached is the CAN peripheral register in bootloader & application code. compared with the configuration, which are very similar and not found why this happened. but while doing the CAN Message RAM initialization,  the RAM contents are different from Bootloader to Application.

  Could you kindly support this case?  Expect for your reply, thanks.

Best Regards

Benjamin

  • 0
    TI__Guru* 95315 points
    Benjamin,
    You mention DCAN works fine in the application, which implies no hardware issues here. Can you please explain how "jump from user application code to user bootloader" is done? When you say " while only run with bootloader code, this issue still existed", are you saying the CAN bootloader does not work even when invoked at power-up?
  • 0 in reply to Hareesh Janakiraman
    TI__Expert 4000 points
    Hi Hareesh,
    Yes, the hardware worked well, the difference between the APP&Bootloader is the APP run with customized OS but the Bootloader doesn't have the OS.
    While powered up, the bootloader CAN peripheral can't work well, and there are some differences that for the CAN RAM message contents after initialization.
    Doubt about the CAN peripheral in initialization would have some unexpected operation, but double checked with the customer's code and CAN demo code, there is no obvious difference.
    Could you kindly give some comments for the case? Expect for your reply, thanks.

    Best Regards
    Benjamin
  • 0 in reply to Benjamin Zhou
    TI__Guru* 95315 points

    Benjamin,

                There are no known issues in the bootloader, which has been tested to be working. And you mention the hardware is working well. Clearly, this is a s/w issue. It is extremely difficult to debug software issues without access to the software and the hardware that the s/w is running on. If you could provide more clarity/precision on what exactly is not working, I may be able to help. Specifically, I need clarity on the following statements:

     

    "...CAN peripheral can't work well...."

     

    ".....there are some differences that for the CAN RAM message contents after initialization...."