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.

Best approach to reporting issues in Driverlib code?

Other Parts Discussed in Thread: MSP430F5638

There are several places throughout the I2C interface code where there are waits without timeouts, which is a major no-no for our application.

So far, I've just copied the code, given the function a new name, and moved on.

But I'm thinking that perhaps I should send what I've discovered off just in case anyone cares.

Is there a mechanism for reporting issues like this?

Ed Averill