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.

LAUNCHXL-F28P55X: TMS320F28P559SJ9PZRQ1: ADC-DAC Loopback Working on LaunchPad but Not on Custom Board

Part Number: LAUNCHXL-F28P55X


Tool/software:

Hello TI team,

I am using the TMS320F28P559SJ9PZRQ1 MCU and trying to perform an ADC-DAC loopback test as part of self-test diagnostics.

Status:

  • The loopback code works correctly on the XF28P559SJ9PZQ LaunchPad. The DAC is configured to output a known voltage, which is then read back via an ADC channel.

  • However, when running the same code on my custom hardware (also using the F28P559SJ9PZRQ1), the ADC does not return the expected value. The ADC result is incorrect , indicating the loopback is failing.

Observations:

  • DAC and ADC initialization is identical on both platforms.

  • DAC reference and output enable settings have been verified.

  • On the custom board, it appears the DAC output is not reaching the ADC input internally.

Questions:

  1. Are there any device-level configuration requirements or errata that could cause this behavior only on the custom board?

  2. Is there any difference in internal analog signal routing between the LaunchPad and standalone devices that might affect this?

  3. Any guidance to debug or validate the DAC output path and ADC sampling under loopback conditions?

I’d appreciate any tips or documentation pointers. I can share the initialization code if needed.

  • Dikshith,

    You can test both module individually. Could you please confirm the following:

    1. Could you please confirm that you are when you run standalone DAC without connecting it to ADC, you are getting correct value on multimeter/oscilloscope to see if DAC configuration is correct?

    2. For ADC, you can use simple DC source or resistor divider to create any voltage level between 0 to 3.3V. Could you please confirm if you are getting those value correctly.

    Once, we find out which one is not working we can go forward with this debug. Let me know.

    Regards,

    Sumit