USBDM programming MKV44F16

[lucianonicolau]

Hi pgo,

How to include MKV44F16?

I identify the sdid value = 0x44601145

Now I need to change the .xml

copying this:

<!-- MKV31F12-->

-<device name="MKV31F256M12" family="CortexM4F" subfamily="MKV31F25612">

<memoryRef ref="kinetis16K_32K_Ram"/>

<memoryRef ref="FTFA_PFlash0_SEC_256K_2KS"/>

<memoryRef ref="kinetisIO_MK"/>

<sdid value="0x31600A80" mask="0xFFF00F80"/>

<tclScriptRef ref="Kinetis-Kxx-Scripts"/>

<flashProgramRef ref="Kinetis-MK-FTFA-flash-program"/>

<registerDescriptionRef ref="CortexM4F-register-description"/>

<note>KV31P100M120SF8RM</note>

<note>Tested</note>

</device>

to this:

<!-- MKV44F16-->

-<device name="MKV44F16" family="CortexM4F" subfamily="MKV44F16">

<memoryRef ref="kinetis16K_32K_Ram"/>

<memoryRef ref="FTFA_PFlash0_SEC_256K_2KS"/>

<memoryRef ref="kinetisIO_MK"/>

<sdid value="0x44601145" mask="0xFFF00F80"/>

<tclScriptRef ref="Kinetis-Kxx-Scripts"/>

<flashProgramRef ref="Kinetis-MK-FTFA-flash-program"/>

<registerDescriptionRef ref="CortexM4F-register-description"/>

<note>KV44F16</note>

<note>Tested</note>

</device>

Do you think I nee to change something more?

Luciano

[raimonddragomir]

Hi Luciano,

The MKE02 support in 160 is broken. If you are in a hurry, you can (re)install the 120 version which works guaranteed :smileyhappy:

I have both versions on my computer (120 and 160). 

Best regards,

Raimond

[pgo]

Hi Luciano,

The main reason for chips not being included is that I don't have one for testing!  I don't feel confident to do this blind.

You can add device basically as you have outlined but you need to do thorough testing to be sure that the device is programmed correctly.

bye

[lucianonicolau]

Thank you, I understood.

These XML files I changed allowed USBDM flash programmer to identify MKV44, so USBDM to Chip KV44 is working now.

But KDS (Kinetis Design Studio) can not show CPU KV44 in order to debug  in "Debug Configuration"

Could you send to me accurate instructions to change more files in order to have MKV44 in USBDM Debug with KDS?

Regards, 

[pgo]

Hi Luciano,

I have uploaded a new version of USBDM to sourceforge  with device descriptions based on those you provided.  Could you check these please?

The devices should now appear correctly but obviously I have not tested them.

bye

[lucianonicolau]

Hi pgo,

The KV44 works perfectly with KDS and ARM Programmer!

Check the MKE02Z64, it is not working with 4.12.1.160  it can detect chip but cannot erase and program, see the error:

I reinstall all with no success for MKE02.

Luciano

[pgo]

Hi Luciano,

As Raimond has indicated, I have broken the ME support in the .160 version.

Yo can see this thread https://community.nxp.com/thread/446167?sr=stream 

for a quick fix (replacement MKE02 script attached near the bottom)

bye

[raimonddragomir]

Hi pgo,

Sorry to dissapoint you, but it's still not working. Something happens just

at the end of flash programming (I can see the progress because it's a ~16K

binary). Then it fails with this message:

(Programming of the target flash failed! Reason: Internal program error -

please report).

The interesting thing is that the programmed binary is almost working! Only

that it's resetting itself after probably one second. I saw this easily on

my board because I have a flashing led pattern in the first 200ms in my

application.

I also installed 140 version (I had 120) and I can confirm it's working.

Now I have the 140 and 160 versions on my computer. 140 is working well,

160 fails in this new way.

The chip is a MKE02Z64VLD2.

2017-04-12 15:08 GMT+03:00 pgo <admin@community.nxp.com>:

NXP Community

<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: USBDM programming MKV44F16

reply from pgo

<https://community.nxp.com/people/pgo?et=watches.email.thread> in *OSBDM

and TBDML* - View the full discussion

<https://community.nxp.com/message/896259?commentID=896259&et=watches.email.thread#comment-896259>

[pgo]

Hi Luciano,

Sorry I forget to answer the other part of your question.

The dialogue sorts the devices by name and speed.  It is meant to leave unrecognized devices unsorted but due to a bug it filters them out - In this case because it doesn't handle the 160MHz speed.

If you change the name of the device to MKV44F64M15 it should appear but there are still a few things broken.

In any case I didn't think KDS supported the MKV40 devices yet?  Do you have to install something else?

I will fix this in the next release probably on the weekend since there are a few other changes to finalise.

bye

[lucianonicolau]

I´d like to add the STM32F030 and STM32F070 on this .xml too. Do you believe it can works? Why don´t you include it yet?
It is because STlinkV2 takes 10sec to program and USBDm takes 3sec (much faster).

[lucianonicolau]

How to include the MKV44 on KDS?

[lucianonicolau]

it works!

<!-- MKV44F-->

-<device name="MKV44F6416" family="CortexM4F" subfamily="MKV44F6416">

<memoryRef ref="kinetis16K_16K_Ram"/>

<memoryRef ref="FTFA_PFlash0_SEC_64K_2KS"/>

<memoryRef ref="kinetisIO_MK"/>

<sdid value="0x44601145" mask="0xFFF00F80"/>

<tclScriptRef ref="Kinetis-Kxx-Scripts"/>

<flashProgramRef ref="Kinetis-MK-FTFA-flash-program"/>

<registerDescriptionRef ref="CortexM4F-register-description"/>

<note>MKV44F6416</note>

</device>

-<device name="MKV44F25616" family="CortexM4F" subfamily="MKV44F25616">

<memoryRef ref="kinetis32K_32K_Ram"/>

<memoryRef ref="FTFA_PFlash0_SEC_256K_2KS"/>

<memoryRef ref="kinetisIO_MK"/>

<sdid value="0x44601145" mask="0xFFF00F80"/>

<tclScriptRef ref="Kinetis-Kxx-Scripts"/>

<flashProgramRef ref="Kinetis-MK-FTFA-flash-program"/>

<registerDescriptionRef ref="CortexM4F-register-description"/>

<note>MKV44F25616</note>

</device>

please include it on the next revision!

Luciano