J-Link OB is an on-board debug probe as part of YOUR eval board.
- Fully compatible with and same features as regular J-Link [More..]
- Inexpensive solution for complete evaluation kits with debug functionality
- JTAG, SWD + SWO supported
- Virtual COM Port (K22-Cortex-M, K22-Cortex-A, STM32F072, SAM3U)
- Optional disable allows use of other external debug probes
- Compatible with most IDEs [More..]
- Very small form factor
- "Drag-And-Drop" interface for intuitive programming of the target device [More..]
J-Link OB is an on-board debug probe as part of YOUR eval board. The microcontroller has a USB-interface on one side and a JTAG/SWD + SWO etc. interface on the device side. It allows debugging the target device on the board it comes with, without the need for an additional debug probe. J-Link OB is used on various eval boards by several eval board manufacturers for various target CPUs.
Having a J-Link right on the eval board allows customers to fully use and test the target CPU, providing full debug capabilities. At the same time, the eval board can remain small and inexpensive. All features of the regular J-Link can be used, including download into Flash memory.
Licensing - Eval board manufacturers
J-Link OB is provided as part of an evaluation board. It is not sold separately. It may only be used to debug the device on the evaluation board it came with. Support is given via the eval board manufacturer and via SEGGER Forum. J-Link OB may not be used for production purposes.
Licensing - Commercial use
J-Link OB is designed in a product or a software development board (for setting up a automated test environment etc.). Pricing is available upon request. For more information please get in touch with us.
Who Can License J-Link OB?
J-Link OB is intended to be licensed for evaluation board manufacturers and silicon vendors. We offer very reasonable pricing.
Do not hesitate to contact us at firstname.lastname@example.org for more information.
Model overview / Supported cores
J-Link OB is not much more than a microcontroller with USB device interface running J-Link firmware. Below is a list of currently available options for J-Link-OB, along with the supported cores and interfaces.
Please note that not every J-Link-OB supports every core and every interface/feature. Other microcontrollers can be supported upon request. If you are looking for a combination that is not yet supported, please get in touch with us.
|J-Link OB model||OB Device||Supported target cores||JTAG||SWD||VCOM|
|Drag & Drop|
|SWO speed||Interface speed||Download performance|
|J-Link-OB-K22-Cortex-M||NXP MK22FN128VLH10 LQFP64 package No external crystal required Cortex-M4 @ 96MHz, 128 KB flash||Cortex-M|
|4 MHz||4 MHz||200 KB/s|
|J-Link-OB-STM32F072-Cortex-M-128KB||ST STM32F072CB UFQFPN48 package No external crystal required Cortex-M0+ @48 MHz, 128 KB flash||Cortex-M|
|250 kHz||2 MHz||100 KB/s|
No external crystal required
Cortex-M0+ @48 MHz, 64 KB flash
|250 kHz||2 MHz||100 KB/s|
Cortex-M3 @72 MHz, 128 KB flash
|4500 kHz||2.25 MHz||150 KB/s|
Cortex-M3 @96 MHz, 128 KB flash
|12000 kHz||3.2 MHz||225 KB/s|
|Available, but not recommended for new designs|
ARM7 @48 MHz, 64 KB flash
|6000 kHz||12 MHz||700 KB/s|
1 Optional. Needs to be specified when ordering
Intuitive Programming of the Target Device
Drag-And-Drop is an optional J-Link OB intuitive programming feature. It allows programming your target MCU in a very simple way.
J-Link OB with Drag-And-Drop capability appears both as a debug probe and as a flash drive on the user's computer - similar to a USB stick. The J-Link's high performance and functionality for programming and debugging remain unchanged! The additional flash drive capability simplifies programming the target to dragging a Motorola S-record, Intel Hex, or plain binary file onto the J-Link Drive.
This J-Link Drive enables manufacturers, and third-party software developers, to deploy ready-to-go demonstration applications to customers who can then quickly evaluate the capability of the board, software, and device - all without installing software or drivers. All major operating systems (Windows, macOS, Linux) are supported.
Developed by SEGGER's Embedded Experts Team, J-Link OB offers a compelling opportunity for board manufacturers to provide a highly polished way to deliver integrated solutions to customers, and enhance the experience over time by adding new applications and features that just "drop into place".
Once customers are ready to do more than download fixed demonstration applications, they can unleash the full potential of the target board using the J-Link OB as a debug probe backed by unparalleled, industry-wide support.
This feature uses SEGGER's Virtual MSD technology.
Drag-And-Drop Flash Programming in Action
The image below demonstrates how easily the microcontroller on the SEGGER emPower (V2 Rev. D or later) can be programmed via "Drag-And-Drop" option.
- Connect the J-Link OB to a Windows, Mac or Linux machine via USB and open the file explorer of your choice.
J-Link will be shown as a flash drive.
- Drag and drop one of the demo .hex files (download here) to the J-Link drive. Programming will start as soon as you drop the file.
- Relax and watch the demo which starts automatically after a few seconds, once programming is complete!
Please note, that Drag-And-Drop is available upon request only.
If you are interested or need more information, please do not hesitate to contact us at email@example.com.
Example implementations that support Drag-And-Drop flash programming
The following boards are already using J-Link OB implementations that support Drag-And-Drop flash programming:
J-Link OB Starter Kits are available which allow eval board manufacturers to test the suitability of J-Link OBs on their specific eval board. The following J-Link OB StarterKits are available:
The StarterKit J-Link-OB-K22 contains the following components:
The StarterKit J-Link-OB-STM32F072 contains the following components:
The StarterKit J-Link-OB-SAM3U contains the following components:
The StarterKit J-Link-OB-STM32F103 contains the following components:
After evaluation of the J-Link OB, a production license needs to be purchased with information on the selected J-Link OB device. The following conditions apply for the usage of the J-Link OB technology:
- SEGGER Logo needs to be printed on the PCB of each eval board containing the J-Link technology
- Eval board does not provide debug out option
- 2 eval board samples containing J-Link OB technology will be provided to SEGGER FOC
How big can the virtual drive be?
A: Pretty much any size. Typically, the size of the virtual J-Link drive should be at least 2.5 times as large as the size of the flash memory, typically rounded to a power of 2. So for a 256KB device, 1MB or more is a good choice. For a 4MByte flash device, the capacity should be 16MB.
Who does the configuration for the target device?
A: All of this is done by SEGGER. The customer receives a production utility that programs the J-Link OB correctly, with the capability to program the specified target device.
The device we target has large flash sectors of up to 128KB per sector. Is this a problem?
A: No. J-Link OB can cope with this.
How fast is the flash programming?
A: Quite fast. Basically as fast as the target device allows it. Total programming time is just slightly more than the time it takes to erase and program the device with very little overhead. On a Nordic Semiconductor NSxxx it takes about 3 seconds to erase and program the entire 256KB flash.
How can this be so fast?
A: Simple: J-Link OB uses SEGGER's real time OS embOS. Multiple tasks run in parallel, performing multiple operations simultaneously: Downloading the program via USB to the J-Link OB, as well as downloading from the J-Link OB into the RAM of the target device as well as "copying" the RAM content of the target device into flash (the actual flash programming). All run largely in parallel, so that the speed is determined by the slowest of the 3 operations, typically the actual flash programming inside of the target device.
What are the minimum hardware requirements for the J-Link OB?
A: Pretty much the same as for J-Link: 64KB Flash memory, 16KB RAM. The only additional requirement is that the MCU used as J-Link OB needs to have a sufficient number of USB Endpoints to accommodate the MSD: 1 for control, 2 bulk for J-Link, 2 bulk for MSD.
Can J-Link work with any kind of Hex or Mot file? Even if only a part of the flash is programmed or the address range is non-consecutive?