Problems using lwIP and USB host together

cremonese wrote on Friday, August 01, 2014:

Hi all,
I’m trying to use lwIP and USB host together (LPC1768). The IP is from FreeRTOS sample CORTEX_LPC168_GCC_RedSuite, and the USB is from the lpcopen 2.10.
Each task works fine if alone, but when they work together, I have problems on the enumerating devices when the USB is detached and reattached: sometimes I get an HardFault and sometimes the enumeration hangs in the function:

static HCD_STATUS WaitForTransferComplete(uint8_t EdIdx)
while ( HcdED(EdIdx)->status == HCD_STATUS_TRANSFER_QUEUED ) {}
return (HCD_STATUS) HcdED(EdIdx)->status;

where the <HcdED(EdIdx)->status> should be updated by the USB’s ISR.
It seems an interrupt problem, but I don’t understand more.

Any help is greatly appreciated.
Best regards,

rtel wrote on Friday, August 01, 2014:

Parts of the USB protocol have tight timing requirements, and it might be that the USB interrupt is being pre-empted by the lwIP interrupt. Try ensuring the USB interrupt has a much higher priority than the Ethernet interrupt. If the USB interrupt is not using the FreeRTOS API then you can even set it to the highest possible priority (which is zero on an LPC1768) to ensure its timing is not effected at all by anything else that is happening in the system - not even any critical sections that might be in the lwIP code.

Remember that if the USB interrupt is using the [interrupt safe] FreeRTOS API [only API functions that end in ‘FromISR’ are intended for use in interrupt] then its priority must be at or below that set by configMAX_SYSCALL_INTERRUPT_PRIORITY: - if you are using a recent version of FreeRTOS then ensuring configASSERT is defined will check this automatically for you at run time

Also make sure, if using the API in the interrupt, that you make use of the pxHigherPriorityTaskWoken parameter to ensure the interrupt returns directly to any unblocked tasks.