Dear Raja, it seems to me to understand that on VF61 it is mandatory to use USBC_CABLEDET(pin 137) for USB client functionality.
If you set SODIMM 137 to 1 but the USB Host is not really present the VF61 start triggering USB IRQ that will lead to memory leak on long term.
Unfortunately on our mainboard the USB client is isolated because it is a medical device, so i cannot recognize the cable connection because i don’have the USB Vbus.
The only way to enable USB client functionality is to set “manually” SODIMM 137 to 1 as standard Gpio.
This method works right if I use a PXA 270 with WinCE5 or a T20 with WinCE7 without any memory leak, only with VF61 goes into memory leak after 4 hours.
Is there a way to overcome this issue if i cannot recognize the cable detection on VF61?
Thanks
Roberto
Dear @sciur,
Unfortunately, we don’t have any other options other than using the USBC_CABLEDET(SODIMM_137) signal to make it work USB client functionality and avoiding the memory leak. There is also one more bug related to Microsoft Active sync memory leak when you use it on the USB Client functionality. As of now, there is no plan to solve due to leak is very small 12kbyte per loop on CE7 Vybrid61, it would consume huge time to solve it.
Please let us know if you have any other questions.