The problem of extended message ID of MSCAN transmit.

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

The problem of extended message ID of MSCAN transmit.

1,080 次查看
terrybogard
Contributor II

Dear NXP expert, when CAN_LDD code generated by processor expert, I found the strategy of send frame function identified the standard ID and extended ID was wrong.

if the MessageID <0x10000, then it will be considered as standard ID. Pls give some advice about this, and I need use the MSCAN transmit extended ID.

MC56F82748

CAN1_SendFrame()

{

...

if ((Frame->MessageID & LDD_CAN_MESSAGE_ID_EXT) != 0U) { /* Is the frame configured as Extended ID? */
CAN_PDD_EnableTxMessageBufferRTRExtId(CAN_BASE_PTR, PDD_ENABLE); /* If yes then set message type as "remote frame" */
} else {
CAN_PDD_EnableTxMessageBufferRTRStdId(CAN_BASE_PTR, PDD_ENABLE); /* If no then set message type as "remote frame" */}

...

}

#define LDD_CAN_MESSAGE_ID_EXT 0x80000000UL /* Value specifying extended Mask, ID */

 

0 项奖励
回复
1 回复

1,065 次查看
xiangjun_rong
NXP TechSupport
NXP TechSupport

Hi,

I attach the msCAN example for MC56F84xxx, pls refer to it.

BR

XiangJun Rong

0 项奖励
回复