AX88772B: ProcessTxBulkOutComplete FAIL!

Hello we have had some problems with the AX88772B on our T30 running WEC7 built from the v2.3 BSP.
We are building a new image using the Toradex v2.3 workspace and noticed that after running for about 18 hours that one of our units showed no status lights at all. No green or amber lights, just messages from the serial output showing the following repeating

AX88772B: ProcessTxBulkOutComplete() Wait complete time out
AX88772B: ProcessTxBulkOutComplete() FAIL! hTransfer:[0xb31c8e50] TxBulkSize:[138] dwUsbErr:[0x0] LastIndex:[7]

Sorry that is all we have to go on, but I had to repower the unit and could not trigger a system dump to get more information, given that our diagnostic tools require a connection to our lan.

Anyone have any insight on this issue?


Dear @bertin,

I quickly searched in our database found one related issue :, Could you try the workaround and let us know the feedback.

If it is not solving the issue, could you provide below details

  • Are you able to reproduce this issue on our carrier board as well?

  • Is there any activity that makes the Ethernet issue happen faster? Is there a way to reproduce the issue reliable?

  • Do you have any additional driver / libraries / activity going on when the issue happens? (USB connection, devices connected, SPI communication, GPIO pin settings, …)

We are building our image based on the 2.3 BSP, would the issue you linked, and the corresponding workaround, effect us?

We don’t seem to have the HKLM\Drivers\BuiltIn\USBEHCI key in our registry. We only have two keys called HKLM\Drivers\BuiltIn\USBEHCI2 and HKLM\Drivers\BuiltIn\USBEHCI3, should I create the HKLM\Drivers\BuiltIn\USBEHCI and enter the value that you suggest?



Dear @bertin,

USB EHCI2 is connected to the Asix AX88772B Ethernet chip, hence you need to create that key under HKLM\Drivers\BuiltIn\USBEHCI2

Thanks for response and sorry for the weird delays in my responses. We have some serious problems with making a working image (see my other posts…) and a tight production timeline.

A quick update. We verified that this registry setting did fix problems on our old (based on the toradex 2.0 BSP/OSDesign) but this doesn’t seem to have any effect our 2.3 based os that I originally reported.

But the good news is that I have no seen the behaviour, as I originally described, reproduce.

So I guess consider this case closed.