J-Flash SPI
Direct programming of (Q)SPI flashes
Overview
J-Flash SPI is a software for Flashers and J-Links to directly program (Q)SPI flashes. It is also used to setup the Flasher for stand-alone programming of those devices. The flash is programmed directly via J-Link or Flasher using the SPI protocol, with no CPU / MCU in between. Since J-Link or Flasher communicates directly with the flash, even flashes connected to CPUs not supported by J-Link or Flasher can be programmed.
Key features
- Multi-platform GUI
- Auto-detection of popular SPI flashes
- Any SPI flash can be supported. All flash parameters can be manually configured / overridden, if required.
- Can be controlled via command-line.
- Multi-platform: Includes setup and control software for Linux, macOS, and Windows.
- No license required. No hidden costs. No future costs.
- Future Proof: Software, firmware updates, and new flash loaders are free of charge
Software
J-Flash SPI is available as part of the Flasher Software and Documentation Package:
Updates
Future software and firmware updates as well as any new flash loaders for target devices that will be added are also free of charge.
- No licensing costs, even for newly supported devices.
- No hidden costs.
- No future costs.
Command Line version
A command line version of J-Flash SPI is also part of the Flasher Software and Documentation Package. The J-Flash SPI software supports all common programming languages. By entering commands into the command line, batch programming for automated execution of routine tasks such as starting or stopping processes, configurations, etc. becomes fast and easy.
Please note that the GUI version of J-Flash SPI can also be controlled from the command line.
Supported devices
J-Flash SPI is able to auto-detect common SPI flashes automatically via their respective ID. Since all flash parameters (size, commands etc.) can also be manually configured by the user, any SPI flash device can be supported.
The list of flash devices that are supported by the flash auto-detection of J-Flash SPI can be found here:
20-pin SPI connection
The following table lists the pinout for the SPI interface:
| Pin | Signal | Type | Description |
|---|---|---|---|
| 1 | VTref | Input | This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. |
| 2 | Not connected | NC | Leave open on target side. |
| 3 | Not connected | NC | Leave open on target side. |
| 5 | DI | Output | Data-input of target SPI. Output of Flasher, used to transmit data to the target SPI. |
| 7 | nCS | Output | Chip-select of target SPI (active LOW). |
| 9 | CLK | Output | SPI clock signal. |
| 11 | Not connected | NC | Leave open on target side. |
| 13 | DO | Input | Data-out of target SPI. Input of Flasher, used to receive data from the target SPI. |
| 15 | nRESET | Output | Target CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". |
| 17 | Not connected | NC | Leave open on target side. |
| 19 | 5V-Supply | Output | This pin can be used to supply power to the target hardware. Older Flashers may not be able to supply power on this pin. |
Pins 4, 6, 8, 10, 12 are GND pins connected to GND in Flashers. They should also be connected to GND in the target system.
Please note:
On later Flasher products these pins are reserved for firmware extension purposes. They can be left open or connected to GND.
20-pin QSPI connection
The following table lists the pinout for the Quad SPI (QSPI) interface:
| Pin | Signal | Type | Description |
|---|---|---|---|
| 1 | VTref | Input | This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. |
| 2 | Not connected | NC | Leave open on target side. |
| 3 | IO1 | I/O | Bi-directional data I/O pin 1 |
| 5 | IO0/DI | I/O | Single: Data-input of target SPI. Output of programmer, used to transmit data to the target SPI. Quad: Bi-directional data I/O pin 0 |
| 7 | nCS | Output | Chip-select of target SPI (active LOW). |
| 9 | CLK | Output | SPI clock signal. |
| 11 | IO2 | I/O | Bi-directional data I/O pin 2 |
| 13 | DO | Input | Single: Data-out of target SPI. Input of programmer, used to receive data from the target SPI. Quad: Must be connected to same signal as pin 3 IO1/DO to guarantee correct operation for temporary single mode transfers during QSPI mode. |
| 15 | nRESET | Output | Target CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". |
| 17 | IO3 | I/O | Bi-directional data I/O pin 3 |
| 19 | 5V-Supply | Output | This pin can be used to supply power to the target hardware. Older Flashers may not be able to supply power on this pin. |
Pins 4, 6, 8, 10, 12 are GND pins connected to GND in Flashers. They should also be connected to GND in the target system.
Please note:
On later Flasher products these pins are reserved for firmware extension purposes. They can be left open or connected to GND.
10-pin needle adapter connection
The following table lists the pinout for the SPI interface when using the 10-Pin Needle Adapter:
| Pin | Signal | Type | Description |
|---|---|---|---|
| 1 | VTref | Input | This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. |
| 2 | nCS | Output | Chip-select of target SPI (active LOW). |
| 4 | CLK | Output | SPI clock signal. |
| 5 | 5V-Supply | Output | This pin can be used to supply power to the target hardware. Older Flashers may not be able to supply power on this pin. |
| 6 | DO | Input | Data-out of target SPI. Input of Flasher, used to receive data from the target SPI. |
| 7 | Not connected | NC | Leave open on target side. |
| 8 | DI | Output | Data-input of target SPI. Output of Flasher, used to transmit data to the target SPI. |
| 9 | Not connected | NC | Leave open on target side. |
| 10 | nRESET | Output | Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". |
Pin 3 is GND pin connected to GND in Flashers. It should also be connected to GND in the target system.
Please note regarding nRESET:
If there is another device / peripheral that also controls the SPI flash (e.g. a CPU the flash is connected to), nRESET of the Flasher should be connected to the reset of the target system or the reset pin of the CPU to make sure that the Flasher can keep the CPU in reset while programming the SPI flash.
Evaluation hardware
Selecting the right (Q)SPI flash that fits the needs can be a difficult task. There are plenty of different flashes as well as vendors available and creating a hardware for each candidate is time-consuming and costly.
To make evaluation of different (Q)SPI flashes a lot easier, we have created a (QSPI) evaluation board.
Flash programming speed
Due to the high performance and the efficient protocol of Flasher, programming speeds up to the max. flash programming specified by the flash vendor, can be achieved.
| Flash device | Programming speed[1] |
|---|---|
| ISSI IS25LP128 | 500 KB/s |
| ISSI IS25LD040 | 100 KB/s |
| ISSI IS25LQ080 | 340 KB/s |
| ISSI IS25CD010 | 100 KB/s |
| ISSI IS25CQ032 | 190 KB/s |
| Macronix MX25L3235E | 285 KB/s |
| Macronix MX66L1G45G | 430 KB/s |
| Macronix MX66L51235F | 315 KB/s |
| Micron N25Q128A | 270 KB/s |
| Micron M25P10 | 160 KB/s |
| Micron M25PX16 | 230 KB/s |
| Micron M45PE10 | 230 KB/s |
| Micron M25PE4 | 215 KB/s |
| Spansion S25FL128 | 410 KB/s |
| Spansion S25FL116K | 265 KB/s |
| Winbond W25Q128FV | 340 KB/s |
[1] Max. flash programming speed that can be achieved depends on flash device. Flash programming is done in pages and page size as well as page programming time varies from device to device. For more information about the page programming time for a specific flash device, please refer to the appropriate datasheet.
FAQ — Frequently asked questions
Q: I have an older Flasher version. Does it support SPI programming?
A: Please check the SEGGER wiki for more information on which Flasher hardware versions the "SPI interface" is supported: kb.segger.com/Software_and_Hardware_Features_Overview.