Ben,
My apologies, yesterday while looking at this issue my access to boards was restricted and I tested with a similar board but subtly different - where OpenSDA and target MCU USB connections were alternately arranged.
That being said, I have now located a Kinetis KL28 and added a debug header for the target MCU for external debug operations. Again, I can see no issue debugging with JLink via USB or IP.
An MCUXpresso IDE installer includes a particular version of JLink and will install this at the IDE installation time. However, no JLink version assumption is made until the first workspace is created. At this time a search is performed to locate the most recent JLink installation and the path used can be seen within the IDE preferences.
From here, the user has the potential to override the IDE's selection or force the IDE to perform a new search (and path update) via the 'Restore Defaults' button.
But note - the target is the J-Link GDB server not JLlink.exe
For a typical IDE installation - all of this is automatically performed, the only time user action is expected is if a later version of SEGGER is manually installed (for some reason) and an existing workspace remains in use.
Also note: Just to add to the complication... After the release of MCUXpresso IDE version 11.0.0. SEGGER made a change to their long standing installation scheme. Therefore if a version of SEGGER JLink is installed that is more recent than the version installed with MCUXpresso IDE Version 11.0.0 the Restore Default mechanism will not automatically detect this update - instead the user must browse for the newer JLinkGDBServer... Furthermore, if a user uninstalls the version of SEGGER J-Link installed by the IDE and replaces this with a later version, then no JLink support will be found - for each workspace, the new server must be manually selected. This issue will be addressed on the next release of MCUXpresso IDE.
I hope this helps,
Yours,
MCUXpresso IDE Support
The Jlink is being powered by the target processors USB connector
To get the Jlink Segger target probe to work I have tried:
Un-installing, then re-installing MCUXpressoIDE_11.0.0_2516.exe
tried
1. JLink_Windows_V647d.exe
2. JLink_Windows_V612.exe
3. JLink_Windows_V646h.exe
When I reinstalled MCUXpressoIDE_11.0.0_2516.exe, it uses version:
JLink_Windows_V6.44i
When it installs, it creates the Jlink folder here:
C:\Program Files (x86)\SEGGER\JLink_V644i
But the IDE looks for it here:
C:\Program Files (x86)\SEGGER\JLink
So I moved all the files from the C:\Program Files (x86)\SEGGER\JLink_V644i folder to the C:\Program Files (x86)\SEGGER\JLink folder.
The Console Tab:
[03-7-2019 01:07:28] Executing Server: "C:\Program Files (x86)\SEGGER\JLink\JLink.exe" -nosilent -swoport 2332 -select USB -telnetport 2333 -singlerun -endian little -noir -speed auto -port 2331 -vd -device MKL28Z512xxx7 -if SWD -halt -reportuseraction
SEGGER J-Link Commander V6.44i (Compiled May 17 2019 17:35:18)
DLL version V6.44i, compiled May 17 2019 17:34:22
Unknown command line option -nosilent.
Server has been shut down.
The windows message box:
As I mentioned, powering the FRDM-KNL28Z from the target USB and using the PEMico's Multilink Probe,
the project can be debugged.
Noticed the SDA USB uses LinkServerDebug
The SWD Segger 10pin Debugger uses Jlink GDB SEGGER Interface Debugging
When I added the Segger Jlink debug, I get:
When I added the PEMicro:
The project does erase, download,verify and allows stepping with the MKL28Z512 10 pin debug. I have FINALLY found a probe that can function.
No blue button, when I press Debug in the Quickstart panel I get:
Now at version 2.44
Found "0244_k20dx_bootloader_update_0x8000.bin" binary at:
DAPLink bootloader update | Mbed
After copying the binary into the folder, Had to loadbin with 0x8000 offset:
J-Link>loadbin C:\Users\bmccormick\Downloads\OpenSDAv2.2_DAPLink_frdmkl26z_rev0242\0244_k20dx_bootloader_update_0x8000.bin,0x8000
Now after a reset, reboot:
Now to try the blue button.
Noticed that your Jlink.exe was at V647a, I used V6.12. Couldn't find V647a, but did find V647d, no legacy selection in the Beta.
When first connecting with V647d, couldn't connect, tried powering up on the target USB port, couldn't halt CPU, then powered back up on SDA USB, looks like it did download the bin file:
Yet another brain fade. I noticed that the link to the bootloader actually was to the FRDM-KL26 NOT FRDM-KL28Z,
so needless to say, it doesn't bootup when the reset button is held and released. I guess its time to go home now.
After noticing the USB was on the SDA port and mine wasn't, after switching to the SDA port, here was the loadbin results:
Looks like the download did fail, still at version 2.41
Thanks Alexis for the detailed example.
The link to https://www.nxp.com/downloads/en/snippets-boot-code-headers-monitors/OpenSDAv2.2_DAPLink_frdmkl28z_r...
took me to:
Page Not Found
The page you requested cannot be found.
After Googling "OpenSDAv2.2_DAPLink_frdmkl26z_rev0242.zip" I found where to download it at:
DAPLink downloads missing from site
Running Jlink:
Augggh.
Hi Ben,
Can you try using this file to load this file using the external debugger?
Using the J-Link debugger connected to the SWD 10-pin connector near the OpenSDA connector, this will give you access to the MK20 in the board.
Using the J-Link commander console execute the next commands:
- connect
-? (Search for the MK20Dx128XXX5)
-s (select SWD)
-(Enter) (Default)
The log should be like the next one:
Then to download the OpenSDA use the command loadbin:
-loadbin (path), 0
And the MCUXpresso should recognize the device after clicking the blue bug, as the next image:
In case you want to debug the target MCU (KL28Z), you should connect the debugger to the other SWD 10 pin connector.
Let me know if this helps you.
Best Regards,
Alexis Andalon
