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

TMS570LS1227: Reconfiguration of message objects

Harshal Pawar
Prodigy 180 points

Part Number: TMS570LS1227
Other Parts Discussed in Thread: HALCOGEN

Hi,

I’m working on the CAN communication of TMS570LS1227.

As per the datasheet, MsgVal bit of the Arbitration register is need to be reset to not valid before making changes in the message objects.

Below is the snap of the same.

The halcogen generated canInit() function sets all the message objects to valid.

Now, I’m using the halcogen generated canUpdateID() API to update the IDs.

But it seems like canUpdateID API doesn’t set the MsgVal bit to not valid, it is keeping the previous state of the 31st bit of Arbitration register i.e. valid (set by halcogen in canInit).

So do I need to set the MsgVal bit to not valid for respective message box every time before using the canUpdateID API?

  • 0
    TI__Guru**** 199296 points

    Hi Harshal,

    Harshal Pawar said:
    So do I need to set the MsgVal bit to not valid for respective message box every time before using the canUpdateID API?

    Yes. If your want to change the ID of a message object for receiving data dynamically, the MSGVAL should be RESET first, then SET after the ID has been changed. After the MSGVAL is reset, the message handler will ignore this message object.