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.

MSP430FR6879: Changing PxDIR register unintentionally

Genius 5840 points
Part Number: MSP430FR6879

Hello,

Has there ever been any case where the PxDIR register has changed unintentionally?

Only P85 was changed input port unintentionally after that I set P87-P84 port is output port and P83-P80 is seg signal of LCD.

For now, I don't know the reason why only P8DIR.5 is changed and how to reproduce this phenomenon.

This phenomenon occurred in one of the 130 units produced so far.

Could you give me any opinions about this issue?

Regards,

U-SK

  • Hi U-SK,

    Could you please provide some more detailed information about your application scenario? What's the external circuit looks like? What's the configuration of the pins you mentioned? What's the "issue" program routine looks like? How you figure out the Px.DIR is changed? Also, if you can provide the detailed part number, including the package type, and the revision, it'll be helpful.

    Regards,

    Harry

  • Hi U-SK,

    Have you got any update?

  • Hi Harry, 

    Sorry for rate reply.

    MSP430 is used for solenoid valve and part number is MSP430FR6879IPZ.

    >What's the external circuit looks like?

    I can't disclose above information.

     >What's the configuration of the pins you mentioned? 

    I configured PxDIR only once like this after reset.

    P8DIR |= BIT4 + BIT5 + BIT6 + BIT7.

    >What's the "issue" program routine looks like?

    I can't disclose about above question.

    But I think this issue is not software error because other P8 pins didn't changed.

    >How you figure out the Px.DIR is changed?

    I read P8DIR address using UART.

    Regards,

    U-SK

  • Hi U-SK,

    Sorry for the long delay, I just came back from the holiday.

    According to your description, I actually don't have much thought. However, one thing may be interesting is that you use UART to readout the register value. Do you use parity check in your UART? As you may know, error occurs in all kinds of communication (wired or wireless, protocol, etc.) with different odds. In your case, since it's just one bit error, a simple parity check could easily identify it.

    Let me know your update.

    Regards,

    Harry

  • Hi U-SK,

    May I know if you got any update for this?

    Regards,

    Harry

**Attention** This is a public forum