• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 99 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0-SDK: LIN communication not working

Desingh Raj Mani
Prodigy 20 points

Part Number: MSPM0-SDK
Other Parts Discussed in Thread: MSPM0G3507, TLIN2029A-Q1

I am trying to execute LIN communication using MSPM03507 launch pad and TLIN eval board. I am using lin_reponder example and it is not woring as expected. Can you please suggest for tools and usage.

  • 0
    TI__Mastermind 23192 points

    Hi Desingh,

    What seems to be the issue?

    Are you able to prove the signals coming from both the MSPM0 LIN output, and the output of the TLIN board? Can you share what the signals coming from the MSPM0 look like?

    Best Regards,

    Diego Abad

  • 0
    Prodigy 20 points

    Hi Diego,

    I have connected the MSPM0G3507 board to TLIN2029A-Q1 Evaluation Module and after that I configured two PID's in responder table one is 20 transmit from Launchpad and E2 received to Launchpad, I am using Canoe 19 and configure LIN network and tried the code running in debug mode full run and expecting the LIN frames for PID 20 in Canoe , i get different errors like  1. Dominant signal waited for long time ,2. data byte 7 is not received and each time when i reset and run i get different errors like this. And in code 

    void LIN_processMessage_Rx(void)
    {
        /* Copy received data to transmit buffer for echo/loopback */
        //memcpy(&gLIN.txBuf[0], &gLIN.rxBuf[0], LIN_DATA_MAX_BUFFER_SIZE);
       
        for (uint8_t i = 0; i < 8; i++)
        {
            gLIN.txBuf[i] = 0;
        }

                /* ---- Update application signals ---- */
            tbc_status      = 2;    /* example status */
            tbc_gain_plus   = 1;
            tbc_gain_minus  = 0;
            tbc_squeeze     = 40;

            TBC_prepareTxFrame(0x20);


        /* Toggle LED1 to indicate a packet has been received */
        DL_GPIO_togglePins(GPIO_LEDS_PORT, GPIO_LEDS_USER_LED_1_PIN);
    }

    /*
     * LIN Transmit Message Handler
     *
     * Called after a LIN message has been transmitted.
     * Toggles LED2 to provide visual indication of transmission.
     */
    void LIN_processMessage_Tx(void)
    {

        /* Toggle LED2 to indicate a packet has been transmitted */
        DL_GPIO_togglePins(GPIO_LEDS_PORT, GPIO_LEDS_USER_LED_2_PIN); 
    LIN_table_record_t responderMessageTable[LIN_RESPONDER_NUM_MSGS] = {
            { 0x20, 8, },
            { 0x49, 8, },
            { 0x0D, 8, },
            { 0xE2, 8, LIN_processMessage_Rx },
            { 0xBA, 8, LIN_processMessage_Rx },
            { 0xFB, 8, LIN_processMessage_Rx }
    }; 
    } these are modified code in Lin_responder 
  • 0 in reply to Desingh Raj Mani
    TI__Mastermind 23192 points

    Hi Desingh,
    Can you share a SALEAE capture of the LIN bus?

    Best Regards,

    Diego Abad