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.

TMS320F280049C: SCI interrupt not respond

Part Number: TMS320F280049C

Hi Champ,

I am asking for my customer.

They are testing with continuously disconnecting the power to the device and power on again the device. At this moment, actually the MCU is still connecting RX/TX with another side (system) which it is still operating and keeps transmitting message to F280049C.

When the device is re-power on, there is a chance that the device SCI RX/TX ISR won’t request and hold an RX/TX interrupt. And it is confirmed rest of the functions are operating well.

We would like to ask whether the device receives UART signals from another side (system) during the initial stage of the SCI module, then it will cause SCI RX/TX ISR not response it and not having an interrupt request.

Any thought from here or testing in as such condition from the past ?

Regards,

Johnny

  • Hi Johnny,

    A few questions to clarify my understanding:

    • What is the reasoning for disconnecting/reconnecting power for the device? (i.e. what is the context)
    • Is my understanding correct? The customer is transmitting data from another device and receiving this data on F280049C and using TX and RX interrupts successfully. After a power cycle (disconnect and reconnect power), the F280049C interrupts are no longer getting triggered.

    Some more specific follow up questions:

    1. Is the customer using FIFO or non-FIFO mode? Which interrupt flags are enabled?
    2. How is the customer measuring whether or not interrupts are being called (i.e. breakpoint in the ISR, checking interrupt flags in PIE, checking interrupt flags in SCI, etc)?
    3. Are SCI error interrupts configured/enabled? Is the customer seeing a frame error or break detect error?
      1. If the F280049C is constantly being sent data from another device (even during a power cycle), it could be that when the SCI module resets and begins receiving data again, the data is read in incorrectly (e.g. it begins reading received data in the middle of a byte, causing the reading frame to be misaligned). 
      2. Is the customer checking if data is being received at all after a power cycle? (if you are able to share oscilloscope images, that could be helpful as well!)

    Best Regards,

    Allison