FlexCAN TX pins was flooded with `can_error` messages and never stop after calling `FLEXCAN_TransferSendNonBlocking`
Steps to reproduces
1. Based on example flexcan_interrupt_transfer
2. change the FlexCAN pin config like this:
IOMUXC_SetPinMux(IOMUXC_GPIO_AD_B0_02_FLEXCAN2_TX, 1U);
IOMUXC_SetPinMux(IOMUXC_GPIO_AD_B0_03_FLEXCAN2_RX, 1U);
IOMUXC_SetPinConfig(IOMUXC_GPIO_AD_B0_02_FLEXCAN2_TX, 0x10B0U);
IOMUXC_SetPinConfig(IOMUXC_GPIO_AD_B0_03_FLEXCAN2_RX, 0x10B0U);
3. trim down other codes except CAN sending - FLEXCAN_TransferSendNonBlocking
4. add a status code print in CAN callback, like this:
static FLEXCAN_CALLBACK(flexcan_callback)
{
LOG_INFO("status code: %d\n", status);
...
problem:
1. after FLEXCAN_TransferSendNonBlocking gets called, the FLEXCAN_CALLBACK always gets called with error code 5311 and never stops
2. can_error signal was capture on CAN_TX_PIN(IOMUXC_GPIO_AD_B0_02_FLEXCAN2_TX), never stops, like this:
PS, CAN peripheral part schematic is straightforward. and the CAN2_P and CAP2_N are not attached to a CAN twisted cable by now.
PPS, seem there is no problem with the default pins of flexcan_interrupt_transfer example:
IOMUXC_SetPinMux(IOMUXC_GPIO_AD_B0_14_FLEXCAN2_TX, 1U);
IOMUXC_SetPinMux(IOMUXC_GPIO_AD_B0_15_FLEXCAN2_RX, 1U);
IOMUXC_SetPinConfig(IOMUXC_GPIO_AD_B0_14_FLEXCAN2_TX, 0x10B0U);
IOMUXC_SetPinConfig(IOMUXC_GPIO_AD_B0_15_FLEXCAN2_RX, 0x10B0U);
