topic Re: Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP in Kinetis Microcontrollers

Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP

jmlegrand — Mon, 17 Dec 2018 16:39:52 GMT

I am playing with a HVP-KV58F module because we are considering using the KV58 MCU in our solid state breaker and motor drive.

For the past few days, I spent few hours to find which tools to use build sample code that will work with module. The documentation mentions: CodeWarrior, Kinetis Studio and finally MCUXpresso.

Based on that research, the MCUXpresso seems to be the most up to date development environment for NPX KV MCU family that will satisfy our developers who are working on MAC OSX and Linux workstations.

Could you confirm that MCUXpresso IDE and SDK are the tools recommended to start a new projet based on NPX KV58 processors?

Finally, I not able to lunch debugging sessions using MCUXpressor between the HVP-KV58F over the mbed CMSIS-DAP (tested on MAC OSX and Windows 10). According to this post (Link Server Unable to connect wire for probe in... | NXP Community ) I probably need to update the CDMIS-DAP firmware, but I can't download any binary for the HVP-KV58F from the NXP web site. Could you tell me where I can find the latest version of the firmware?

To be honest, the chip looks great on paper, but so far I had to spend a lot of time trying to just run an example on the evaluation module and it is still not working. Is-it really a MCU recommended for new design?

Re: Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP

Robin_Shen — Tue, 18 Dec 2018 07:20:49 GMT

Hi Jean-Marc Legrand,

Please download the MCUXpresso IDE 10.3.0, CodeWarrior and Kinetis Design Studio are outdate.(New SDK will not support them.)
Please also build and download the latest MCUXpresso SDK_2.5.0_HVP-KV58F and Documentation(SDK_2.5.0_HVP-KV58F_doc).

Then you can find the "Table 2. Hardware platforms supported by MCUXpresso SDK" Getting Started with MCUXpresso SDK.pdf.
It showns CMSIS-DAP OpenSDA v2.1 are used on both HVP-KV58F and TWR-KV58F220M.

I have attached TWR-KV58F220M-QSP.zip, you can try to use the bootloader and firmware in it.(Win10 may meet problem.)

Best Regards,

Robin

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP

jmlegrand — Tue, 18 Dec 2018 16:27:17 GMT

The attachment TWR-KV58F220M-QSP.zip is missing. Could you attach the file?

Re: Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP

Robin_Shen — Wed, 19 Dec 2018 00:48:17 GMT

Sorry. I forget to attached it.

Please check it.

Re: Can't attach MCUXpresso debugger to HVP-KV58F via CDMIS-DAP

jmlegrand — Wed, 19 Dec 2018 15:20:38 GMT

Robin,

I have burned and tested the following OpenSDA images.

CMSIS-DAP (Default Image)
OpenSDA bootloader
PE Micro
Segger OpenSDA

The USB device is listed when I boot in bootloader mode. Then I can copy the firmware onto the bootloader drive, but I don't see the USB device when a disconnect and reconned the HVP-KV58F board to my MacBook Pro.

Before booting in bootloader mode
$ ioreg -p IOUSB +-o Root <class IORegistryEntry, id 0x100000100, retain 22> +-o AppleUSBVHCIBCE Root Hub Simulation@80000000 <class AppleUSBRootHubDevice, id$ \| +-o iBridge@80100000 <class AppleUSBDevice, id 0x1000004fe, registered, matched$ \| +-o Headset@80400000 <class AppleUSBDevice, id 0x100000508, registered, matched$ \| +-o iBridge ALS@80300000 <class AppleUSBDevice, id 0x10000050c, registered, mat$ \| +-o iBridge Display@80600000 <class AppleUSBDevice, id 0x10000051b, registered,$ \| +-o iBridge DFR brightness@80700000 <class AppleUSBDevice, id 0x100000545, regi$ \| +-o iBridge FaceTime HD Camera (Built-in)@80200000 <class AppleUSBDevice, id 0x$ \| +-o Apple Internal Keyboard / Trackpad@80500000 <class AppleUSBDevice, id 0x100$ +-o AppleUSBXHCI Root Hub Simulation@02000000 <class AppleUSBRootHubDevice, id 0x$ +-o AppleUSBXHCI Root Hub Simulation@14000000 <class AppleUSBRootHubDevice, id 0x$ \| +-o USB2.0 Hub@14100000 <class AppleUSBDevice, id 0x100011a2d, registered, matc$ +-o AppleUSBXHCI Root Hub Simulation@03000000 <class AppleUSBRootHubDevice, id 0x$ +-o USB3.0 Hub@03100000 <class AppleUSBDevice, id 0x100011a14, registered, matc$

Before booting in bootloader mode

$ ioreg -p IOUSB

+-o Root <class IORegistryEntry, id 0x100000100, retain 22>

+-o AppleUSBVHCIBCE Root Hub Simulation@80000000 <class AppleUSBRootHubDevice, id$

| +-o iBridge@80100000 <class AppleUSBDevice, id 0x1000004fe, registered, matched$

| +-o Headset@80400000 <class AppleUSBDevice, id 0x100000508, registered, matched$

| +-o iBridge ALS@80300000 <class AppleUSBDevice, id 0x10000050c, registered, mat$

| +-o iBridge Display@80600000 <class AppleUSBDevice, id 0x10000051b, registered,$

| +-o iBridge DFR brightness@80700000 <class AppleUSBDevice, id 0x100000545, regi$

| +-o iBridge FaceTime HD Camera (Built-in)@80200000 <class AppleUSBDevice, id 0x$

| +-o Apple Internal Keyboard / Trackpad@80500000 <class AppleUSBDevice, id 0x100$

+-o AppleUSBXHCI Root Hub Simulation@02000000 <class AppleUSBRootHubDevice, id 0x$

+-o AppleUSBXHCI Root Hub Simulation@14000000 <class AppleUSBRootHubDevice, id 0x$

| +-o USB2.0 Hub@14100000 <class AppleUSBDevice, id 0x100011a2d, registered, matc$

+-o AppleUSBXHCI Root Hub Simulation@03000000 <class AppleUSBRootHubDevice, id 0x$

+-o USB3.0 Hub@03100000 <class AppleUSBDevice, id 0x100011a14, registered, matc$

After booting in bootloader mode
$ ioreg -p IOUSB +-o Root <class IORegistryEntry, id 0x100000100, retain 22> +-o AppleUSBVHCIBCE Root Hub Simulation@80000000 <class AppleUSBRootHubDevice, id$ \| +-o iBridge@80100000 <class AppleUSBDevice, id 0x1000004fe, registered, matched$ \| +-o Headset@80400000 <class AppleUSBDevice, id 0x100000508, registered, matched$ \| +-o iBridge ALS@80300000 <class AppleUSBDevice, id 0x10000050c, registered, mat$ \| +-o iBridge Display@80600000 <class AppleUSBDevice, id 0x10000051b, registered,$ \| +-o iBridge DFR brightness@80700000 <class AppleUSBDevice, id 0x100000545, regi$ \| +-o iBridge FaceTime HD Camera (Built-in)@80200000 <class AppleUSBDevice, id 0x$ \| +-o Apple Internal Keyboard / Trackpad@80500000 <class AppleUSBDevice, id 0x100$ +-o AppleUSBXHCI Root Hub Simulation@02000000 <class AppleUSBRootHubDevice, id 0x$ +-o AppleUSBXHCI Root Hub Simulation@14000000 <class AppleUSBRootHubDevice, id 0x$ \| +-o USB2.0 Hub@14100000 <class AppleUSBDevice, id 0x100011cb0, registered, matc$ \| +-o MBED CMSIS-DAP@14140000 <class AppleUSBDevice, id 0x100011cc8, registered$ +-o AppleUSBXHCI Root Hub Simulation@03000000 <class AppleUSBRootHubDevice, id 0x$ +-o USB3.0 Hub@03100000 <class AppleUSBDevice, id 0x100011c97, registered, matc$

After booting in bootloader mode