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.

TMS320F2800157: UART Vs BQ79616

Part Number: TMS320F2800157
Other Parts Discussed in Thread: TMS320F280039C, BQ79616, USB2ANY, SYSCONFIG

Tool/software:

hello experts,

I’m experiencing an issue with UART communication between the TMS320F2800157 Launchpad and the BQ79616 EVM. I’m generating the signal as shown in the picture below, but the BQ79616 does not respond. However, when generating the same signal using another Launchpad (TMS320F280039C), the BQ79616 responds correctly and communicates as expected, providing the appropriate readings.

Please note that both setups use the same clock and the same baud rate (1 Mbps), as specified in the BMS documentation.

  • Hello,

    I will need some more detail on the issue you are seeing as it is difficult to discern what type of issue may be occurring with the only symptom being the BQ device does not respond (i.e. this could be a hardware connection issue, peripheral/device configuration issue, software implementation issue, etc).

    Are you connected to the device debugger while running the program? Can you confirm that you are able to see the registers being programmed in memory correctly? Are you seeing the expected signal when scoping the TX? 

    I would also run one of our SDK examples to confirm you are able to transmit/receive ok. Please let me know if you are able to provide more context on the issue and any results from what you have already done to debug. 

    Best Regards,

    Allison

  • i think i didn't explain the issue correctly.

    so i'll explain from the beginning, so first of all, i have TMS320F280039C launchpad and BQ79616 EVM, so i can reading cell voltage and module voltage and temperature and all communication is good, and communication between microcontroller and BMS is UART, the hardware connection between microcontroller and BMS as shown below 

    connect BMS_USB2ANY_TX with controller_TX (GPIO_35)

    connect BMS_USB2ANY_RX with controller_RX (GPIO_37)

    Connect BMS_USB2ANY_3.3 with controller_3.3 

    and BMS_GND_ISO with controller_GND

    and all is good with communication and reading from BMS and writing to BMS

    so i decide to migrate from the controller TMS320F280039C to TMS320F2800157

    and made the previous connection to the new controller TMS320F2800157

    connect BMS_USB2ANY_TX with controller_TX (GPIO_29)

    connect BMS_USB2ANY_RX with controller_RX (GPIO_28)

    Connect BMS_USB2ANY_3.3 with controller_3.3 

    and BMS_GND_ISO with controller_GND

    so first of all i test the UART in TMS320F2800157 and it works well, and i can send frames and receive frames 

    so i sent the following signal

      

    and followed the wakeup sequence for the BMS to wake up to move forward to communicate with the BMS.

    but the BMS didn't respond

    i'm using the same software that i'm using in TMS320F280039C launchpad with different MCAL that compatible with TMS320F2800157 launchpad

     but BMS didn't respond, so i can say the issue not from the UART

    so can you help me ?

    if you need further more information, please let me know

    Are you connected to the device debugger while running the program? Can you confirm that you are able to see the registers being programmed in memory correctly? Are you seeing the expected signal when scoping the TX? 

    yes i am connected to the device debugger while running the program and 

    able to see the register being programmed in memory correctly 

    I would also run one of our SDK examples to confirm you are able to transmit/receive ok.

    yes i did that and transmit/receive is ok. 

  • Hello,

    Thank you for the more thorough explanation. Can you confirm what your SCI GPIO configurations are or perhaps send a snippet? Are you using sysconfig for this?

    Best Regards,

    Allison

  • hello,

    this the SCI GPIO configurations

    i'm using the same code that generated from sysconfig

  • Hello,

    Apologies for the delay. So from what you are describing, the SCI on F280015x is functioning properly and sending the command as expected, but the BQ device is not responding. Is that correct? If there is no issue with the SCI communication on C2000 side and the output signal is seen correctly, then I may forward this to the BQ team to gather their input as well.

    Best Regards,

    Allison