FRDM-K64F no USB detected with recent DAPLink

cancel
Showing results for 
Search instead for 
Did you mean: 

FRDM-K64F no USB detected with recent DAPLink

2,992 Views
pietrushnic
Contributor I

Hi all,

I tried recent firmware from OpenSDA site, but neither DAPLink rev0242 nor DAPLink OpenSDA v2.2 Bootloader works for me. When using CMSIS-DAP 0226 or 0221 I see correctly exposed USB endpoints:

|__ Port 4: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 12M
|__ Port 4: Dev 52, If 0, Class=Mass Storage, Driver=usb-storage, 12M
|__ Port 4: Dev 52, If 3, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 12M

With that I can flash with OpenOCD (despite some errors). Using DAPLink firmware nothing is detected. How this firmware should work with FRDM-K64F ?

According to README.md of DAPLink project I should see at least 3 endpoints.

Labels (1)
Tags (2)
9 Replies

1,152 Views
nxf50233
NXP Employee
NXP Employee

Hello,

I faced the same issue on K64F and K66F freedom boards. The COM port was not found and the OpenSDA firmware update did crash the K20 with Windows 10.

Segger J-Link OpenSDA - Board-Specific Firmwares trick from Michael Cress solved it.

Could we change the driver download link from K64F and K66F get started page?

Thanks for your answer.

Best regards,

Paul

---

Get started link

pastedImage_2.png

Segger firmware solution

solution to the win 10 problem com not found.PNG

0 Kudos

1,152 Views
avantyr
Contributor I

Just in case someone with the same problem as me stumbles upon this, I had a similar issue.

None of the DapLink bootloader binaries were working for me (after installing them and reconnecting the USB none of the LEDs lit up and my PC didn't detect the board), only the Segger J-Link one was working, but after updating the KDS 3.0.0 that debugger was broken for me and the 2 plugins "fix" failed me. 

I managed to find a special Debug version of the P&E/PNE one which upon connecting it installed/fixed the OpenSDA driver on my Windows 10 laptop. That binary works fine with the PnE Debugger I have.

I've attached the zip which contains that Kinetis K64F binary. Hopefully, it can save someone a headache.

Download from my drive

0 Kudos

1,152 Views
michaelcress
Contributor II

I'm also experiencing this issue. I have attempted to download CMSIS-DAP rev 0221 from OpenSDA Serial and Debug Adapter|NXP , however the link just refers back to the .html page that hosts it. So not only do I have a board that won't show me the MBED mount anymore but also no way to revert ( it seems ).

0 Kudos

1,152 Views
mjbcswitzerland
Specialist V

Hi

Unless you are using Rowley Crossworks (which may need it) I would forget CMSIS-DAP - the latest Segger version is very good. It now works very well with Win 10 (debugging, USB-MSD loading and VCOM). However Win 7 should be used to load the boot loader since it can't be loaded with Win 10.


It is useful to have Win 7 available to re-load in case it gets corrupted (which can happen, although I don't know exactly when and why, but I have needed to reload a couple of times).

Regards

Mark

1,152 Views
michaelcress
Contributor II

This works for me with MCUXpresso on both Mac and Win 10.

For anyone who may find themselves here in the future, I grabbed the install files from here: SEGGER - The Embedded Experts - Downloads - J-Link / J-Trace . Search for J-Link OpenSDA - Board-Specific Firmwares and expand it. My board is FRDM-K64F. I copied the .bin file to the bootloader mount, unplugged, and replugged and MCUXpresso found it just fine. This also seems to work with mbed files too (although I'm guessing that shouldn't be a surprise to anyone).

1,152 Views
pietrushnic
Contributor I

I managed to build working setup able to flash and debug using 2 different firmwares and upstream OpenOCD. First is CMSIS-DAP 0226. It looks like CMSIS-DAP 0226, despite generating errors while flashing  give ability to correctly run sample Zephyr networking application that I tested. Second working configuration is Segger Jlink - I tried binaries from recent KDS.

I described my experience in this blog post

0 Kudos

1,152 Views
SiegfriedLoeffl
Contributor I

I also have trouble getting this board to work.

- I put the board into bootloader mode (reset while plugging it in). It appears as BOOTLOADER USB drive on my Mac and the LED blinks in green.

- I downloaded the CMSIS-DAP-BOOTLOADERV2.zip file from OpenSDA Serial and Debug Adapter|NXP 
- I try to copy this file to the board, but it's too big:

$ sudo mount -u -w -o sync /Volumes/BOOTLOADER ; cp -X ~/Downloads/CMSIS-DAP-BOOTLOADERV2.zip /Volumes/BOOTLOADER/

Password:

cp: /Volumes/BOOTLOADER/CMSIS-DAP-BOOTLOADERV2.zip: No space left on device

Same problem obviously also on a Windows PC... (checked just to be sure).

Now the board doesnt' seem to do anything when I boot it up. Where can I find the correct firmware files.

I think I'll throw the board in the trash and get an Arduino instead. It's just a waste of time. 

0 Kudos

1,152 Views
michaelcress
Contributor II

Hey Siegfried,

Just an FYI...you have to unzip the file and then attempt to copy the .bin file ( not the .zip ). Don't bother though; I attempted on both Win 10 and Mac with no success.

0 Kudos

1,152 Views
mjbcswitzerland
Specialist V

Siegfried

Try this:OpenSDA Serial and Debug Adapter|NXP 

There are P&E, mdeb, Segger versions to try. It is true that MAC (not sure, but I know it operates in a similar fashion - see http://www.utasker.com/kinetis/USB-MSD-MAC.html) and Windows 10 have caused some big problems with the on-board debuggers. Presently I use the most up to date Segger one since it works as Virtual COM, USB-MSD for fastest and easiest binary file loading and as reliable debugger (a few weeks ago the previous latest version failed as USB-MSD so it shows that it is being maintained!). Previously I was using P&E (for a couple of years for debugging but it didn't have USB-MSD) but after a certain Win 10 update it stopped operating correctly and that is when I moved to Segger (but it is worth trying various ones if interested). I was also using mbed as VCOM and fast USB-MSD loader on a second FRDM-K64F board for a couple of years, but that would never debug and it too completely failed after a recent Win 10 update. The DAPLink is generally considered to not be much use since it is not of any quality and I think it is only very half-heartedly maintained by mdeb (probably more ARM PR than anything to be taken seriously).

Once you get this working try some projects from http://www.utasker.com/kinetis/FRDM-K64F.html where you can get a complete open source FRDM-K64F solution that will allow you also to simulate the board and cut project development times.

Regards

Mark


Professional support for Kinetis: http://www.utasker.com/index.html
Remote desktop one-on-one coaching: http://www.utasker.com/services.html
Getting started to expert videos: https://www.youtube.com/results?search_query=utasker+shorts

0 Kudos