Difference between revisions of "J-Link-OB-K22-CortexM"
| Line 11: | Line 11: | ||
* Start J-Link Commander |
* Start J-Link Commander |
||
* If this message is shown, one of the "buggy" OBs has been detected and corrected: |
* If this message is shown, one of the "buggy" OBs has been detected and corrected: |
||
| + | *;[[File: JLink-OB-K22-CortexM_900031732_to_900032331_AutoCorrect.png | none]] |
||
* Power-cycle the J-Link OB (unplug and re-plug USB connector of eval board) |
* Power-cycle the J-Link OB (unplug and re-plug USB connector of eval board) |
||
* Now the J-Link OB will also expose a virtual COM port (COM port number from screenshot below may differ): |
* Now the J-Link OB will also expose a virtual COM port (COM port number from screenshot below may differ): |
||
| + | *;[[File: JLink-OB-K22-CortexM_900031732_to_900032331_VCOMPort.png | none]] |
||
Revision as of 10:07, 7 July 2022
This article describes specifics of the J-Link OB CortexM (See https://www.segger.com/products/debug-probes/j-link/models/j-link-ob/#model-overview-supported-cores).
Contents
SN 900031732 to 900032331
These J-Link OB have been mounted on eval boards from Ambiq Micro and some of these report no virtual COM port (VCOM) by accident.
An in-field fix has been implemented V7.66g and later.
How to apply the fix:
- Start J-Link Commander
- If this message is shown, one of the "buggy" OBs has been detected and corrected:
- Power-cycle the J-Link OB (unplug and re-plug USB connector of eval board)
- Now the J-Link OB will also expose a virtual COM port (COM port number from screenshot below may differ):
