Tool/software: TI-RTOS
HI,
My customer is getting stack at NDK jumbo frame verification on their custom board. Basically they have followed the following step to modify NDK and PDK NIMU:
Considering their reports, I felt OK for
- NDK customization built for jumbo frame
- NIMU layer modification for PBM : PBM_alloc(10236)
... But this wiki is too old for the lates ProcSDK environment (v05.01.00.11). NIMU build system had been changed from CCS to gmake.
It seems Eric has verified to work jumbo frame with the ProcSDK on C6678 EVM. See the following link.
My question here is what was the exact build step for modifying NIMU source code to support jumbo frame ? The post suggested like:
We just knew an issue in the K2H NIMU driver, ping failed on 1500 bytes of packets. In the K2H, nimu_eth.c, we changed
From:
if (Init_Cpsw ((uint32_t) ptr_device->mtu, ptr_pvt_data->pdi.bMacAddr) != 0)
To:
if (Init_Cpsw ((uint32_t) (ptr_device->mtu + ETHHDR_SIZE + 4U), ptr_pvt_data->pdi.bMacAddr) != 0)
With this change we were about to ping with >1500 bytes packets (without jumbo support, the packets are fragmented as expected). Without this change, ping has no response for >1500 bytes packets. Maybe the same fix also apply to the C6678 as well as this is the CPSW setup MTU size code.
But i'm not sure the similar modification was actually needed or not. Could you clarify ?
Best Regards,
NK