BRT Community

Please login or register.

Login with username, password and session length
Advanced search  


Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - tomas.kopriva

Pages: [1]

thank you for your response and suggestions! The application note from your reply provide clear explanation, how to use and modify the toolchain sources.

best regards
Tomas Kopriva


i am working on the project, which will use the USB Flash drive connected to the USB HOST port of the FT900 (which is really fantastic and powerful IC). With the current version of the FT9xx Toolchain V.2.5.0 everything works as expected but there is a flaw in the USB HOST / BOMS API.

1) when the connected USB Flash drive goes bad - is somehow corrupted, the BOMS API calls wait indefinitely for the drive to respond. This eventually blocks the firmware from normal operation until such corrupted USB Flash drive is unplugged. Judging from the Toolchain source codes, the USB HOST / BOMS API somehow consider timeouts on most places, but some calls still use an infinite wait times. It would be nice to have full control over USB HOST / BOMS API timeout - to be user configurable.

2) there is defined function USBH_finalise (to: Release any resources associated with the USB driver and disable the hardware) but the function have no body. So there is no way to safely shutdown and release resources of the USB Host layer.

So my question is, do you planning to implement above mentioned behavior in the future release of the FT9xx Toolchain?

best regards
Tomas Kopriva

Pages: [1]