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-Q1: LIN communication issue with the chip

Part Number: TMS320F2800157-Q1


Tool/software:

Hello, I am encountering a serious problem with the LIN communication part of the 157 chip.

Software background: The current software includes a boot part and an APP part, and the program jumps from BOOT to APP when the controller is powered on. BOOT needs communication, so it initializes the LIN communication module. Similarly, the LIN module is initialized in the APP.

Test problem: I use CANOE to keep communicating with the 157 controller constantly, and conduct repeated power-on and power-off tests on the controller. During the test, the problem of "intermittent loss of communication after power-on" occurs.

Problem analysis: I conducted the same test on a 280025 controller, and no such "intermittent loss of communication after power-on" problem occurred.

Compare the LIN communication part of the software program between the 280025 and 157 controllers, and you will find that the operations are consistent and there is no difference. Compare the technical reference manuals of the 280025 and 157 controllers, and you will find that the LIN communication part of the two chips is basically consistent and there is little difference (except that the 280025 has DMA function). In addition, the same LIN transceiver was used in both tests.

Therefore, I would like to ask:

1. What are the specific subtle differences between the 250 chip and the 157 chip in the LIN communication module?
2. Besides the differences explicitly stated in the technical manual, do the 025 chip and the 157 chip have similar subtle differences in other driver modules, such as the LIN communication module?
3. Why does the 157 chip's LIN communication occasionally lose communication after power-on, and how should this problem be solved?

  • Hi Tonyx,

    The design of the LIN module itself did not change at all between the F28002x and the F280015x devices. As you stated, the only difference is that there is a DMA wrapper added in design to interface with the LIN module on the F28002x since that device has a DMA. For other modules on these devices, you may see many differences since they are both completely different device families. For this I would suggest referring to the types/descriptions listed for each module you are using in the Peripheral User Guide (linked here) to see the similarities and differences. While some modules will be exactly the same (like the LIN module), others will have some changes (like the CMPSS for example).

    As for the power-on issue, can you describe a little more about why your application is initializing the LIN module in both the boot sequence and the application code? Also, I am not familiar with CANOE, is "intermittent loss of communication after power-on" a message that gets displayed by this software? In this errored case, if you send messages repeatedly with CANOE, does the data ever eventually get received properly or does it keep displaying this error message?

    Best Regards,

    Delaney

  • Thank you for your reply

    Communication is also required during boot, so the LIN module is initialized in the boot program;
    After one power on, the controller cannot respond to the LIN header

  • Hi Zhang,

    Why is it necessary to re-initialize the LIN module in the application code? Are different settings being used in communication during the application code? Are you able to connect a debugger to your device to see what is being received by the application in the errored case?

    Best Regards,

    Delaney

  • Hi Delaney,

    Yes, the application program and boot program are different, and I cannot obtain some status of the MCU under error conditions because error conditions occur randomly.

    The most confusing thing is that this error situation has never occurred on the 025 chip, and the programs of the two chips are completely identical, including the same testing environment.

    Best Regards,

    Zhang

  • Hi Zhang,

    Are you able to connect a debugger to the F280015 chip to view the LIN status flags in the errored case?

    It's possible that this could be an issue with the boot sequence; that may be the difference between the operation of the 2 devices since the LIN module has no change. I will discuss with the boot expert to see if they have any input on this.

    Best Regards,

    Delaney

  • Hi,Delaney

    thanks very much,

    I need to repeatedly power on and off the controller. Currently, the JTAG emulator cannot maintain contact with the chip when the controller is powered off, and the UART function hardware is temporarily not supported, so I cannot obtain the specific status when the error occurs.

    Best Regards,

    Zhang

  • Hi Zhang,

    Delaney is out of office today, returning tomorrow, please expect a response back by then.

    Thank you,

    Luke

  • Hi Zhang,

    Are you able to share your application and boot code? Or at least the LIN configurations you are using for both?

    Best Regards,

    Delaney