OSBDM and TBDMLのトピックFailed to resume target process. Downloading binary to target...

Failed to resume target process. Downloading binary to target...

Joel69003 — Sat, 18 Oct 2014 23:42:13 GMT

Hi all, and particularly PGO,

I'm experimenting issues with CodeWarrior and the USBDM with MKE02Z64M4 device. I have created a project and keep all default options. However, it is not possible to load and debug the application. I get the following error when launching the debugging:

In the console:

My USBDM is "USBDM_SWD_JS16CWJ". Software version is 4.10.6.200, drivers 1.3.0.

I am able to program the target with the ARM programmer provided with the USBDM (it works well) but it is not very convenient to debug the application...

Have you experimented this kind of issues ? Thanks for your help!

Regards,

Joel

Re: Failed to resume target process. Downloading binary to target...

pgo — Sun, 19 Oct 2014 22:33:09 GMT

Hi Joel,

It is not setting the device correctly (Hence the _DEFAULT) in the flash programming log.

This probably means that I have not correctly set an alias for the device. Codewarrior uses different names internally for devices and these are mapped to the usual names by an alias entry in the database.

I probably have missed the one for the device you are using.

I will check this.

bye

PS Confirmed missing entries. This will be corrected in the next version or you can try manually adding the following lines to near the end of arm_devices.xml (after similar ones for KE02Z16M2):

<device name="KE02Z16M4"	alias="MKE02Z16M4"	hidden="true"/>
<device name="KE02Z32M4"	alias="MKE02Z32M4"	hidden="true"/>
<device name="KE02Z64M4"	alias="MKE02Z64M4"	hidden="true"/>

bye

Re: Failed to resume target process. Downloading binary to target...

Joel69003 — Mon, 20 Oct 2014 17:38:51 GMT

Hello PGO,

Thanks for writing. I have added the 3 lines in the file "C:\Program Files (x86)\pgo\USBDM 4.10.6.200\DeviceData\arm_devices.xml" just below the three lines for KE02 M2 devices but it is not working :-( I have created a new project in a new workspace, and it is still written "DEVICE = '_DEFAULT'" in the console. Do I need to do something to force CodeWarrior taking care of the new configuration ?

Note: I have created a new project with a KE02 M2 device (well, I don't now the difference between the two except the maximum clock speed) and launched the debug of a very simple application with CodeWarrior and it is working. So issue is only for the M4 devices.

Thanks for your help,

Regards,

Joel

Re: Failed to resume target process. Downloading binary to target...

pgo — Mon, 27 Oct 2014 20:45:41 GMT

Hi Joel,

The current version adds these aliases so I would expect it to work now.

bye

Re: Failed to resume target process. Downloading binary to target...

Joel69003 — Tue, 28 Oct 2014 19:50:37 GMT

Hi PGO,

I have installed 4.10.6.210 and the issue is now corrected.

Thanks for your time.

Best Regards,

Joel

Re: Failed to resume target process. Downloading binary to target...

wangyongsheng — Sat, 18 Apr 2015 16:10:34 GMT

Hello PGO

I meet the same problems using the USBDM 4.10.6.250 to Debug the DSC MC56F8345 and MC56F84789 with Codewarrior 10.6.But the information in Console is different.Here is the details:

Executing Initialization File: E:\Codewarrior\84789_BDM/Project_Settings/Debugger/MC56F84789.tcl

radix x

cmdwin::eclipse::config hexprefix 0x

cmdwin::eclipse::config MemWidth 16

cmdwin::eclipse::config MemAccess 16

cmdwin::eclipse::config MemSwap off

Starting 3rd party flash programming...

DiMemoryDownload() - DI_DNLD_TERMINATE - Programming memory image...

===========================================================

Programming target

Device = 'MC56F84585'

Trim, F=0, NVA@0000, clock@0000

Ram[0000...3FFF]

Erase=EraseMass

Security=intelligent

Total bytes=35556

doRamWrites=T

Erase Time = 3.48 s, Speed = 9.97 kBytes/s, rc = 0

DiMemoryDownload() - DI_DNLD_TERMINATE - Programming complete, rc = 7

Thanks for your attention,

Best Regards,

yongsheng