the USB endpoint buffer maybe exausted in KHCI driver

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

the USB endpoint buffer maybe exausted in KHCI driver

1,352件の閲覧回数
robinliao
Contributor I

hello NXP

We encountered a problem when using the KHCI driver (KSDK 1.3) in our application

When Kinetis K81 is connected to an Android device via USB, the endpoint buffer (usb_dev_ptr->xd_entries) will be exhausted when the Android SDK calls the following functions to close and open the HCI connection:

  1. android.hardware.usb.UsbDeviceConnection.releaseInterface(UsbInterface intf)
  2. android.hardware.usb.UsbDeviceConnection.close()
  3. Context.getSystemService(Context.USB_SERVICE)

becuase usb_dci_khci_init_xd() is called only when a USBRST interrupt (K81 reset, USB plug on/plug off) occurs, if the USB host continues to obtain device descriptors, xd_entries may be exhausted

how can I release the xd_entries buffer correctly if USB device didn't be plug off and on on during the life cycle?

 

Thank you

Robin

ラベル(1)
0 件の賞賛
返信
1 返信

1,299件の閲覧回数
vicentegomez
NXP TechSupport
NXP TechSupport

I recommend that you changed to MCUExpresso and test the SDK for that

 

0 件の賞賛
返信