• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 398 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/TM4C1294NCPDT: Setting properties to disable the Peripheral Clock on Bebug breakpoints

Dario Patruno1
Prodigy 60 points

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

Tool/software: Code Composer Studio

Hi guys!

I have a problem with the Tiva Series C board. The Can1 peripheral seems to go crazy or not properly configured

using the PB0 and PB1 pins. No OTG neither BoosterPacks are connected on.

The pins shows a square waveform also when the software is stopped on a breakpoint, meaning that, I guess,

the peripheral clock stay indipendent from the microcontroller clock and the debugger.

Is there a way to stop the peripheral clock on breakpoints ?

Thank you so much! Have a beautiful day!

Dario Patruno

  • 0
    TI__Guru 72500 points
    Are you using the EK-TM4C1294XL launch pad? On that board PB1 is tied to 5V (TARGET_VBUS) through an analog switch. That pin is used as USB0VBUS in USB OTG or USB HOST mode. To turn off that switch, PD6 must be low. You can configure PD6 as a digital output driving low, or as an input with a pulldown. Using PB1 as CAN1TX without configuring PD6 can blow the output buffer of PB1.
  • 0 in reply to Bob Crosby
    Prodigy 60 points
    Thanks Bob for the answer. I´ll put the PD6 pin in low state output if I´ll use the CAN1 peripheral. Unfortunately I´m using the CAN0 one... and the issue is still present...
    Thanks a lot.
    Best Regards,
    Dario Patruno
  • 0 in reply to Dario Patruno1
    TI__Guru 72500 points
    I don't see a way to suspend the CAN peripheral clock in debug mode in the documentation, but I want to do some experiments before I conclude it cannot be done. Sorry, but I am kind of backed up so I might not be able to do that today.

    Can you be more specific about the "go crazy"? Can you capture the CAN bus with a logic analyzer and see if the timing looks correct for the transmit and if you are getting an acknowledge, or is someone else on the bus asserting an error frame? What is the value in the CANSTS register after trying to transmit at 500K baud?
  • 0 in reply to Bob Crosby
    TI__Guru 72500 points

    You seem to have two threads going on this CAN at 500K baud issue. If needed, let's continue this on the other thread:

    e2e.ti.com/.../805818