This was not the silver bullet we hoped for.
Our problem with 'false' MSG_LOST continued.
Then we realised we were on version 2.1.8 of XMClib.
Stepping to 2.1.18 with the change introduced to void XMC_CAN_MO_Config(const XMC_CAN_MO_t *const can_mo) seemed to do the trick.
Problem was that TX events was enabled on RX MOs and visa versa. That was why this problem was only an issue on our gateway nodes. They have a lot of continuous TX & RX, on both the CAN1 & CAN2 modules.
Our problem with 'false' MSG_LOST continued.
Then we realised we were on version 2.1.8 of XMClib.
Stepping to 2.1.18 with the change introduced to void XMC_CAN_MO_Config(const XMC_CAN_MO_t *const can_mo) seemed to do the trick.
Problem was that TX events was enabled on RX MOs and visa versa. That was why this problem was only an issue on our gateway nodes. They have a lot of continuous TX & RX, on both the CAN1 & CAN2 modules.