• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 732 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.

AWR1642: About MCAN test issue

yimin bai34
Genius 4755 points

Part Number: AWR1642
Other Parts Discussed in Thread: MMWAVE-SDK

Hi Sir 

We used AWR1642 EVM for CANFD test in  Rev. B EVM.

We set the parameter as below

                testSelection = 4;

                gDisplayStats = 1;

the log showed 

Debug: Number of iterations              : 1

Debug: Number of messages transmitted    : 0

Debug: Number of messages received       : 0

Debug: Number of messages lost           : 0

Debug: Error Status Interrupt              : 1

Debug: Error Reason                     : 6

Error Reason is 6 and it means "CANFD_Reason_PROTOCOL_ERR_DATA_PHASE".

Could you advise what is this issue or what we miss to do?

thanks

BR

Yimin

  • 0
    TI__Mastermind 22155 points
    Hello Yimin bai34,

    Can you please clarify the following:
    1. What is the demo or example application you are using from the MMWAVE-SDK?
    2. What is BITTIMINGS you have set in the example code for the CANFD?
    3. What is the bittiming you have set in the receiver tool?

    The error seems to be due to dataphase BIT TIMING mismatch between the Tx and Rx.

    -Raghu
  • 0 in reply to Raghunandan Kamath
    Genius 4755 points

    Hi SIr 

    1. EVM is AWR1642 Ver B and we use mmwave_sdk_02_00_00_04 CAN-FD Test code. 

    2. BITTIMINGS used the default setting of test code 

        mcanBitTimingParams.nomBrp      = 0x2U;

        mcanBitTimingParams.nomPropSeg  = 0x8U;

        mcanBitTimingParams.nomPseg1    = 0x6U;

        mcanBitTimingParams.nomPseg2    = 0x5U;

        mcanBitTimingParams.nomSjw      = 0x1U;

     

        mcanBitTimingParams.dataBrp     = 0x2U;

        mcanBitTimingParams.dataPropSeg = 0x8U;

        mcanBitTimingParams.dataPseg1   = 0x6U;

        mcanBitTimingParams.dataPseg2   = 0x5U;

        mcanBitTimingParams.dataSjw     = 0x1U;

    3. the tool is peak system for receiving. And the CANFD setting of peak system is the same with test programming.

    please advise

    BR

    Yimin

  • 0 in reply to yimin bai34
    TI__Mastermind 22155 points

    Hello Yimin,

    Bellow are the setting to be done in the driver for 1Mbps nominal bitrate and 5Mbps Data bitrate

    mcanBitTimingParams.nomBrp      = 0x2U;

       mcanBitTimingParams.nomPropSeg  = 0x8U;

       mcanBitTimingParams.nomPseg1    = 0x6U;

       mcanBitTimingParams.nomPseg2    = 0x5U;

       mcanBitTimingParams.nomSjw      = 0x1U;

    /*5MHz*/

       mcanBitTimingParams.dataBrp     = 0x1U;

       mcanBitTimingParams.dataPropSeg = 0x2U;

       mcanBitTimingParams.dataPseg1   = 0x2U;

       mcanBitTimingParams.dataPseg2   = 0x3U;

       mcanBitTimingParams.dataSjw     = 0x1U;

    If you have a different bitrate requirement, please change these settings accordingly.

    Also if you are planning to use the FD mode of operation you will need to also enable the CAN -FD option on the Peak system tool.

    Please refer to this APP_NOTE for more details on the bittiming and the setup..

    Thanks,

    Raghu