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

[jmlegrand]

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?

[jmlegrand]

After reviewing, the schematics and probing some signals on the board, I found some answers:

1. The HVP-KV58F board can't attach to the MCUXpresso because the target MCU is not powered by the USB port like it is the case with the HVP-KV46F150M.

2. To power the MCU in standalone mode, you have to plug it into the HVPMC3P or you have to provide the power from the USB by wiring the power of the USB to power the target MCU via J10 and J11.  See the attached image. 

IMPORTANT - You can't insert HVP-KV58F module into the HVPMC3P platform when this patch is installed.

[Robin_Shen]

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!
-----------------------------------------------------------------------------------------------------------------------

[jmlegrand]

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

[Robin_Shen]

Sorry. I forget to attached it.

Please check it.

[jmlegrand]

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$

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 burning any of the 4 firmware listed above

$ 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 0x100011db9, registered, matc$   +-o AppleUSBXHCI Root Hub Simulation@03000000  <class AppleUSBRootHubDevice, id 0x$     +-o USB3.0 Hub@03100000  <class AppleUSBDevice, id 0x100011da0, registered, matc$

Do you have any idea why it is not working?

Note: I have HVP-KV46XXX module that is working like a charm. 

[Robin_Shen]

I didn't find the DAPLink of HVP-KV58F either.

Please try to use the bootloader and firmware of FRDM-K22F board on OPENSDA: OpenSDA Serial and Debug Adapter

[jmlegrand]

Robin,

I still waiting for an answer that could explain why I am not able to attach de the MCUXpresso IDE with the HVP-KV58F board.  Could you give me an update?

I can't find the HVP-KV58F220M Schematics (in PDF format) on the NXP WEB site.  Could you tell me where I can find it?

Regards,

Jean-Marc

[Robin_Shen]

You can download the HVP-KV58F220M Design Files(REV 1) now.

The HVP-KV58F220M Schematics (in PDF format) can be found in it.

[Robin_Shen]

Sorry for my late reply!
Have you try to test it on Windows 10?

The HVP-KV58F220M Schematics (in PDF format) is not available on the NXP WEB site. I need to contact internal team to ask where can we get it. I will attached the schematic after I receive it.

Best Regards,

Robin

[jmlegrand]

Robin,

I have tried to test on my Windows 10 VM (running on Mac OSX workstation), but the MBED USB device refused to mount in the VM.  I am using Virtualbox 5.2.22 and the device is added to USB device filter for that VM.  My HVP KV46F150M has the PEMicro firmware and this one works fine.   I can test with the PEMicro firmware if  you can provide me the firmware that could be installed on my HVP KV58F.

Regards,

Jean-Marc

[jmlegrand]

Robin,

I ran my tests only on Mac OSX only because we are using Mac OSX for

development and Linux for continuous integration. I will try on a Windows

10 VM tonight.

Regards,

Jean-Marc

[jmlegrand]

Robin,

I am now able to see the board a USB device.  But I had to use the different bootloader binary file obtained from DAPLink bootloader update | Mbed  (I have attached the binary file that I have used with this reply).  Then I have used the file k20dx_frdmk22f_if_crc_legacy_0x8000.bin.zip to reprogram my unit with the latest versions of DAPLink firmware.

However, I am still not able to attach MCUXpresso IDE with the HVP KV58F board.  I am getting the following error message:

Error Message from MCXpresse IDE
Error in final launch sequence Error: Unable to configure core for probe index 1. Wire not connected LinkServer has been terminated and will be restarted. Please restart your debug session. If the problem recurs, please power cycle your debug probe and restart MCUXpresso IDE.