In CAN and CAN FD's 15765 transport ISOTP, you didn't add full-duplex mode, only half-duplex. Can you add full-duplex mode according to the ISO15765 standard?

[chenyurong22]

According to the ISO15765 standard, when handling SF, FF, FC, and CF, there are two CAN/CANFD transmission modes: half-duplex and full-duplex. The diagram is shown below.

on page 38
Table 23 — Handling of unexpected arrival of N_PDU with same N_AI as currently being processed

ISO 15765-2 2016.pdf

You've already implemented the half-duplex mode of ISOT. Can you add full-duplex mode according to the ISO15765 standard?

[tae9898]

again i didn't checked hw test but done with code
thanks for pr!
git : b46ca97

[chenyurong22]

again i didn't checked hw test but done with code thanks for pr! git : b46ca97

@tae9898 hello

thank you very much, I will check it on STM32 board. If I find some bug , I will give you feedback.

by the way, Can you add a distinction between physical addressing and functional addressing here?

in void ISO_TP_ProcessFrame(uint32_t can_id, const uint8_t *data, uint8_t dlc) function, can you according to the recieve can_id, Are you distinguishing between physical addressing and functional addressing?

void ISO_TP_ProcessFrame(uint32_t can_id, const uint8_t *data, uint8_t dlc)
{
if (data == NULL || dlc == 0U) {
return;
}

/* PCI 타입 판별: 첫 바이트의 상위 4비트 */
uint8_t pci_type = data[0] & 0xF0U;

switch (pci_type) {
    case ISO_TP_PCI_SINGLE_FRAME:
        process_single_frame(can_id, data, dlc);
        break;
    case ISO_TP_PCI_FIRST_FRAME:
        process_first_frame(can_id, data, dlc);
        break;
    case ISO_TP_PCI_CONSECUTIVE:
        process_consecutive_frame(data, dlc);
        break;
    case ISO_TP_PCI_FLOW_CONTROL:
        process_flow_control(data, dlc);
        break;
    default:
        Debug_Print("[ISO-TP] Unknown PCI: 0x%02X\r\n", data[0]);
        break;
}

}