• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 411 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.

TM4C123GE6PM: Can bus errors at 40 Deg C testing

Ariel Pickholz26
Intellectual 1295 points
Part Number: TM4C123GE6PM
Other Parts Discussed in Thread: TM4C1230H6PM

Hi ,

My customet is using an oven to test our device as part of a product.

They are using TM4C1230H6PM and we are facing CANBUS errors.

While heating the component the CANBUS freezes and communication stops.

They would need URGENT assistance from TI team in order to fully understand the issue and debug it.

The heat is being done on an oven, and they are warming it up to 35-40OC.

Best regards ,

Arik.p

  • 0
    TI__Guru 72500 points
    I will need more information before I can help. You may contact me directly by e-mail.
  • 0
    Guru 117855 points

    Ariel Pickholz26 said:
    ...board is being oven heated - to 35-40°C - causing CANBUS to freeze...

    Might you detail the extent of "CANBUS Freeze?"

    • only CAN_TX halts
    • only CAN_RX halts
    • both CAN_TX/RX halt
    • CAN signals continue - but are mis-shapen or "off frequency"

    Have you monitored the CANBUS signal's "bit widths" - both during "normal" temperature & at elevated ones?    Does that "bit width" change as temperature rises?

    We've encountered this on client boards - usually (but not always) improper crystal bypass caps were employed - and these shift cap values w/temperature changes.

    You may also wish to, "Output a divided replica of the MCU's system clock" (via a Timer pin config'ed as output) and monitor that frequency for stability.

    Employing a simple, "Blink LED" will confirm that (other) aspects of the MCU maintain functionality (at elevated temp.) - no such data has been provided...

    And - as always - we're not told if this issue occurs across multiple boards - or just one.   Single board anomalies are "no fun" - multiple boards should be exercised & the results reported...