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.

TMS320F28377D-EP: Accopling signal noise between CAN A and ECAP with GPIO101

Part Number: TMS320F28377D-EP
Hello.
We have detected some issues related with the pin GPIO101 of a TMS320F28377D-EP.
We have found that if we connect this pin to an ECAP and we send CAN-A messages, the ECAP generates wrong values (more than 25% of deviation from the expected value).

With CAN-A in silence, errors does not happen. CAN-A TX and RX are connected to a CAN driver, but it is not connected to any other device.

Same setup using another pin (tested with pins GPIO100, GPIO102 and GPIO103) are working flawlessly.
It happens no matter which ECAP we use (tested on ECAPs 1 to 4), with pin configured as sync and async qualifications.
These test discards software problems for us as the only thing we change is the ECAP MUX for the GPIO.
The test was implemented as:
- PWM 1 configured to 50Hz, 50% duty cycle, connected to GPIO to be tested.
- CAN-A sending 200 messages/second (the data is not relevant).
- ECAP configured to read pulse width.

We have checked that the PWM signal is arriving clean to the input pin, so we discarded external hardware problems.

We suspect there is a silicon error on this chip.

Do you have any reports about that problems?

Thank you,

Samuel Ors.