• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 325 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.

IWR6843AOPEVM: mcanMultiTransmission [-3502 error]

Tom Bilsborow
Prodigy 20 points
Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: AWR6843AOPEVM

Trying out the 6843AOP here and am seeing Error: CANFD transmit data retry failed [Error code -3502] faults when running the out-of-box example for mcanMultiTransmission present in the CANFD library of the SDK. The kicker here, is that Classic CAN has been enabled, meaning that mcanCfgParams->fdMode = 0x0U. The follow timing parameters are being used, which have been calculated from the TI CAN Timing Calculator.

    mcanBitTimingParams.nomBrp = 0x10U;
    mcanBitTimingParams.nomPropSeg = 0x1U;
    mcanBitTimingParams.nomPseg1 = 0x3U;
    mcanBitTimingParams.nomPseg2 = 0x3U;
    mcanBitTimingParams.nomSjw = 0x3U;

    mcanBitTimingParams.dataBrp = 0x10U;
    mcanBitTimingParams.dataPropSeg = 0x1U;
    mcanBitTimingParams.dataPseg1 = 0x3U;
    mcanBitTimingParams.dataPseg2 = 0x3U;
    mcanBitTimingParams.dataSjw = 0x3U;
   

On the topic of setup, I have a AWR6843AOPEVM connected to a mmWave Boost PROC074B with CAN routed to J1/J2 of the PROC074B via the myriad of DIP switches. I have ~1m twisted pair CAN bus with termination at each end. An Ixxat USB-to-CAN compact (non-FD) adapter is connected into the far end of the setup. I see an output waveform when I send out data from CANTX, but this -3502 error is presented.

Any help here would be appreciated!

Tom

  • 0
    TI__Genius 17265 points

    Hi Tom,

    Looking at the CANFD driver, error -3502 is CANFD_EINUSE which indicates "Operation cannot be implemented because a previous
    * operation is still not complete."  Since you are running a multiTransmission test, I believe this indicates that the TX buffer has not cleared the first message out before you try to put the second in.

    It sounds like you modified the tests a bit, have you successfully ran them without any modifications? This may help indicate whether there is a HW or setup issue.  Additionally, have you looked at the pinmux used in this test? They are intended for the non-AOP devices, so it may be good to double check that the signal is pinmuxed to the expected location. 

    Best Regards,
    Alec