Difference between revisions of "J-Link-OB-K22-CortexM"
(→SN 900031732 to 900032331) |
(→Drag and drop programming support) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
__TOC__ |
__TOC__ |
||
| + | |||
| + | == Drag and drop programming support == |
||
| + | This J-Link OB model optionally supports the drag & drop programming feature. For more information about host OS specifics, potential limitations, ... please refer to the [[J-Link_drag_and_drop_programming | drag and drop programming wiki article]]. |
||
| + | |||
| + | === Drag and drop fails under macOS Ventura === |
||
| + | Starting with macOS Ventura, file download via drag & drop could fail with macOS error code 100093. This was caused by a change in behavior of macOS, introduced with that version.<br> |
||
| + | Fixed in J-Link OB firmware that comes with J-Link software V7.82b and later. |
||
== SN 900031732 to 900032331 == |
== SN 900031732 to 900032331 == |
||
Revision as of 17:50, 7 November 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
Drag and drop programming support
This J-Link OB model optionally supports the drag & drop programming feature. For more information about host OS specifics, potential limitations, ... please refer to the drag and drop programming wiki article.
Drag and drop fails under macOS Ventura
Starting with macOS Ventura, file download via drag & drop could fail with macOS error code 100093. This was caused by a change in behavior of macOS, introduced with that version.
Fixed in J-Link OB firmware that comes with J-Link software V7.82b and later.
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):
