K64F USBDevice Issues

[matthewelse]

(Using the Freescale FRDM-K64F)
I'm using the USBHID samples from the handbook on mbed.org, and when I connect it to a mac, nothing is detected (I looked in System Information or whatever it's called - the equivalent of device manager), and when I connect it to Windows, it just says the USB Device has malfunctioned.

This error doesn't appear when code not using USB is run, so clearly it's an issue with the USB Device code somewhere. I might try and do some debugging myself at some point, however I thought I'd try and see if anyone else has had similar issues.

[matthewelse]

@0xc0170 I've got a lot of free time tomorrow (I think), so I'll have a look at debugging this. Perhaps the K64F deals with USB slightly differently to the KL25Z (since they share code, this seems like a good starting point).

[matthewelse]

I had a quick read through this https://community.freescale.com/message/445413#445413, and it seems to imply that this should need fixing: https://github.com/mbedmicro/mbed/blob/master/libraries/mbed/targets/cmsis/TARGET_Freescale/TARGET_MCU_K64F/TOOLCHAIN_ARM_STD/startup_MK64F12.s

I'll edit it on my fork and let you know how it goes

[matthewelse]

The change suggested in that article in fact don't seem to have an effect on this bug. I'm using USBMouse_HelloWorld compiled with the online compiler, using mbed-src and USBDevice. as a simple demo to test the board and it doesn't work with or without the fix he implemented.

[0xc0170]

the community post you reference, there was a bug filled for it and was merged, so it should be in the startup file

[matthewelse]

Yeah I noticed that 😞

I'm still confused by this bug I'm having though...

[Sissors]

@matthewelse, which mbed library are you using? I also ran into something similar, which is only present in the latest mbed release. At release 89 it works fine for me, release 91 not. That has new CMSIS files, so I already looked at things like system settings and clock setups, but while some stuff changed, I haven't found the one responsible for it yet.

[matthewelse]

I was using mbed-src at the time, with the latest version when I first
posted the issue - I'm guessing that's 91 however I'm not entirely sure.
On Thu, 27 Nov 2014 at 15:13 Sissors notifications@github.com wrote:

@matthewelse https://github.com/matthewelse, which mbed library are you
using? I also ran into something similar, which is only present in the
latest mbed release. At release 89 it works fine for me, release 91 not.
That has new CMSIS files, so I already looked at things like system
settings and clock setups, but while some stuff changed, I haven't found
the one responsible for it yet.

—
Reply to this email directly or view it on GitHub
#690 (comment).

[Sissors]

That indeed will be 91, or a least the files included in it. Revision 89 of the mbed lib (312 or so of the mbed-src lib) should work.

And the main reason I was replying here, did some investigatons, and weirdly the register definition file (MK64F12.h) seems to be the cause of the problems. I quickly scanned through it, but didn't really see something which could be it.

[Sissors]

And there is the fix :)

[matthewelse]

Thanks! I was about to go and investigate it myself 😄

[0xc0170]

The fix #690 was merged today, this should be resolved.