USBDM always busy in FRDM-K64F

[arturlazarini]

Hello everyone,

I'm having some troubles with USBDM. I recently got two FRDM K64F, had some problem with KDS and Codewarrior to run these babies but I finally made it using Segger openSda, PEmicro openSDA and cmsis-dap.
So the problem starts after I build my own PCB with a Kinetis uC and tried to debbug it. Segger and PEmicro openSDA are blocked for other devices.

I was not able to debbug another board besides the freedom, so someone told me to try USBDM.

I followed the steps, installed the drivers, the software and uploaded the USBDM firmware to both of the frdm k64f.
My windows was able to find and install the devices, but I can't run it in any software. The USBDM firmware upgrade software say that my device can't be found because it always busy.

I tried the same procedure with a FRDM KL25 that I own, but it is my windows that can't recognize the device. It always find the device as unknown.

Ps.: I'm using the latest USBDM that I found in sourceforge.

Anyone have an ideia to solve this? Or have any ideia how to debbug another board using the Freedom boards?

Regards,
Artur

[arturlazarini]

Hello everyone,

Sorry I haven't updated this for quite some time.

My USBDM is working fine now.
I updated the drivers and software to version 4.11.1.30 (version that I'm running).

That was more than enough to make it work, but still don't know why it was not working before.  :smileyconfused:

By the way thank you guys for the help !

Best regards,

Artur

[pgo]

Hi Artur,

The USBDM firmware upgrade utility doesn't apply to OpenSDA devices.  It is only for the HCS08 based devices.

You install the software in the usual "openSDA" fashion using the bootloader as detailed here:

http://usbdm.sourceforge.net/USBDM_V4.10/Freedom/html/freedom_setup.html

Does the ARM programmer detect the BDM?

If so can you detect and program the on-board chip?

The FRDM-KL25 is probably the best option for a general purpose programmer and the above instruction are for this board.

What version of Windows are you using?

bye

[arturlazarini]

Hi pgo

thank you for your response.

I installed the software and drivers again just to be sure.

For the frdm-KL25 the windows says that the device is a unknown device (by the way I'm using windows 7 ultimate).

For the frdm-KL64 the drivers are okay and "working". Windows can find it but USBDM software can't.

If I click in "detect" the BDM firmware Ver 10.45.214 changes to BDM firmware Ver 69.66.40 and thats all.
The device is always as busy or not responding.

Any ideias about this issues?

Thank you again for your support.

Regards,
Artur

[smashsmashin]

Same behavior with latest version of USBDM on Win XP and Linux.

Using USB hub (with or without power) didn't help.

I got it running with version 4.10.6.190 and firmware from OpenSDA firmware from version 4.10.6.250

[pgo]

Hi Artur,

I don't have much idea what is causing this.   It appears that the drivers are installed but something is wrong with the communication.

Could you do the following please:

• Could you open the device properties in device manager by right-clicking on the item.

• Select the Driver Details in the Driver Tab

• Could you post the details available.  They should be similar to:

In addition could you try running the debug version of the ARM programmer:

• C:\Program Files (x86)\pgo\USBDM 4.10.6.190\ARM_FlashProgrammer-debug.exe
• I would expect the same results but it will create a log file that might give some clue what  is going wrong.
• Could you post the log file: %APPDATA%/usbdm/usbdm.log

bye

[arturlazarini]

Hi pgo,

The drivers look the same for me.

I run "ARM_FlashProgrammer-debug.exe" and as you said it didn't work. So I run "ARM_GDBServer-debug.exe" and created the logs.
They are in the attachments (by the way there was no usbdm.log).

Thank you for all your help and fast responses !

Artur

[pgo]

Hi Artur,

I'm sorry I should have been more specific.  Could you post the usbdm.log file which contains the low-level usb communication log.

bye

[arturlazarini]

Hi pgo,

The only problem is that I can't find this file you are asking for.

I searched in %APPDATA%/usbdm/usbdm.log but this is everything that I found:

By the way, I downloaded the newer version (USBDM_4_10_6_190_Win) of the software but nothing has changed.

Thanks for the all your Help . :smileyhappy:

[pgo]

Hi Artur,

Could you do the following:

• Start the debug version of the ARM programmer (ARM_FlashProgrammer-debug.exe)
• Ignore the failure to detect a device on the first tab and open the second tab
• Click on Detect Chip button and ignore any errors.
• Close the programmer.

The above should produce a usbdm.log file.

bye

[arturlazarini]

Hi pgo,

I produced the file that you asked for.
Please take a look.

Thank you for all the help.

Regards,
Artur

[guitardenver]

Does anybody know what the solution to this problem was?

[guitardenver]

Found the solution.

Using an external USB hub did the trick. I used an externally powered USB hub too.

[DiegoFSL]

I can confirm a similar solution for me.

It didn't work with a mouse and the FRDM-KL25Z attached. When I disconnected the mouse and connected only the FRDM-KL25Z it worked at first try.