Keil Logo

µVISION DEBUGGER: Problems to debug/simulate NXP Kinetis devices


Information in this knowledgebase article applies to:

  • MDK-ARM V5.20

SYMPTOM

You may encounter problems debugging an NXP Kinetis microcontroller with Keil ULINK2, Keil ULINKpro, Segger J-Link or any CMSIS-DAP debugger. This only happens when a project was created with MDK-ARM V5.20. Projects created with previous MDK-ARM versions do not demonstrate this problem.

CAUSE

Many devices need special handling when a debug session is started. With MDK-ARM V5.20, all Freescale devices were renamed to NXP because these companies merged. The debug drivers for Keil ULINK2, Keil ULINKpro, Segger J-Link or any CMSIS-DAP debugger only checked for the chip vendor name 'Freescale' to enable the special handling for these devices.

RESOLUTION

Download the ZIP file attached to this knowledgebase article and extract it to your MDK-ARM installation folder, which is C:\Keil_v5\ by default. This updates the files:

  • CMSIS_AGDI.DLL to version 1.25.21
  • SARMCM3.DLL to version 5.20.0.2
  • JLTAgdi.DLL to version 1.60.0
  • UL2ARM.DLL to version 1.74.9
  • UL2CM3.DLL to version 1.157.19
  • ULP2ARM.DLL to version 2.20.8
  • ULP2CM3.DLL to version 2.203.30

STATUS

The problem is fixed with the attached debug drivers. IMPORTANT: Do not apply these patches to any MDK-ARM release other than V5.20.

SEE ALSO

ATTACHED FILES

Request the files attached to this knowledgebase article.

Last Reviewed: Friday, February 24, 2017


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.