• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 304 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.

CCS/TMS320F28069: eCAN-A (Tx/Rx) will not work under CCS debugger but works fine if target is running without debugger.

Goetz Borkowski7
Intellectual 410 points
Part Number: TMS320F28069

Tool/software: Code Composer Studio

Hello from Ubstadt / GER,

currently, I'm developing a communication between 2 targets of same type (TMS320F28069),
using Tiny-CAN IV xl as  a HW adaptor together with CANcool as a monitor as well as for rest-bus simulation.

Messages can be sent / received  between the monitor and a target as long as the target runs "freely".

If I try the same with the target under the debugger, messages do not reach the monitor and cannot be received
from it -- no matter if I run the target in stepping mode or let it run without breaks.

What I could observe is that the concerning bit in CANTRS will not change to 0 after setting 1, so that the program
hangs in the CANTRS polling loop if no timeout is used.

CCS version is: 8.2.0; debugger version is: Cannot retrieve it from Help/about. Came along with CCS 8.2.0.

Has anybody an idea what's wrong??

Note: I'll be back monday...

Best regards and thanks in advance

Goetz

  • 0
    TI__Guru* 95315 points
    Goetz,
    I have heard of the other way round (i.e. code will work only when debugger is connected, but not when running standalone from flash), but not what you are seeing.

    Have you taken a look at the Debug tips in SPRA876? Specifically the one pertaining to 32-bit R/W?
  • 0 in reply to Hareesh Janakiraman
    Intellectual 410 points
    Hello Hareesh,
    the reason of the malfuction was a failure of my CAN monitor (CANcool, with Tiny-CAN IV):
    When the monitor is launched the first time after Tiny-CAN was energized, it often fails to send or receive.
    Tn this case, we must start it a second time. Since the monitor does not display what it's sending, one must have a look on the Tx LED
    in order to control whether it is functional or not.
    In our case it did not send nor receive... So, things first stuck, then worked after a second startup.

    Thanks and have a good time
    best regards, Goetz