• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 140 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.

AM263P4-Q1: The behavior of SDK APIs when the MCAN module is not initialized

Imaoka Daisaku
Intellectual 430 points

Part Number: AM263P4-Q1

If an error occurs during MCAN_init() or if the MCAN module remains in an uninitialized state or stays in initialization mode, what will be the behavior when calling the following APIs?

  • MCAN_getProtocolStatus()
  • MCAN_getTxFIFOQueStatus()
  • MCAN_initTxBufElement()
  • MCAN_writeMsgRam()
  • MCAN_txBufAddReq()
  • MCAN_getNewDataStatus()
  • MCAN_readMsgRam()
  • MCAN_clearNewDataStatus()
  • 0
    TI__Mastermind 40193 points

    Hi Imaoka,

    If the MCAN module is uninitialized or improperly initialized, then the state machine of the peripheral may be inaccurate, which will result in various undeterminable functionality.

    We won't be able to determine or guarantee any specific operational behavior of these API without proper initialization applied.

    I will share the excerpt below from the BOSCH MCAN User Guide document which specifies which registers are reset with CCCR.CCE/INIT toggling.

    This should give some guidance as to the operations of the API knowing that these registers will be zeroed out and invalid.

    Best Regards,

    Zackary Fleenor