5 years, 1 month ago.
USBDevice on FRDM-K64F sometimes crash my laptop
First, it is my second post on this topic but could not locate my old one. Sorry for the repeated post then. However, I am bringing more info this time.
I am currently having issues with the USBDevice library when deployed on the FRDM-K64F. I built a very simple image for target which only instantiate one USBMidi object. (see attached image) When I connect the usb port of the target to my Windows 8.1 development laptop, I get one of the following results: - Unknown device message, and a floating unknown usb device in the "Device Manager", sometimes reporting that descriptors could not be retrieved. - A frozen screen which requires a computer reset - A blue screen which report one of the following messages : PAGE_FAULT_IN_NONPAGE_AREA, IRQL_NOT_LESS_OR_EQUAL, KERNEL_SECURITY_CHECK_FAILURE - Sometimes works (when I am very lucky)
Another thing I observed is that the FRDM-K64F usb port sometimes has to be connected multiple times before the firmware achieves proper start-up. When the firmware does not start, only the Ethernet port led is on. Could there be power sequencing issues?
The host laptop is a DELL XPS 15" and has a Intel(R) series 8/C220 USB 3.0 controller.
I tested the same target/firmware on other computers and USBDevice/FRDM-K64F worked fine. (Intel(R) series 6/C200 and Intel(R) series 7/C216)
I considered the fact that the problem might be the laptop itself. However, what worries me here is that I have been using this laptop with all kind of USB devices for at least a year and never experienced any issue. (Including USB sound cards with midi ports)
Too add to my observations, I tested the same cases with a second FRDM-K64F board and got the same results.
After conducting some researches, I came across this post http://developer.mbed.org/questions/4252/USBKeyboard-on-KL25Z-only-works-intermit/ where the reported problem appeared to be similar to mine. Sadly, I tested the http://developer.mbed.org/users/mjr/code/USBDevice/ library and It did not fixed my issue.
I also tested this with 2 different 2.0 USB Hubs. No luck there either.
Does anybody observed similar issue or has any idea of what could be going on? At this point, I am planning the purchase of an external USB sniffer to try to solve this.
If anybody as an idea for a patch, I would be more then happy to test it!
1 year ago.
The information about the USB device on FRDM-K64F is so helpful and valuable. I hope that we will get this kind of stuff in the future also. https://www.pcsupportnumber.co.uk/blog/fix-windows-error-code-0x80004005/
You need to log in to post a question