Flasher Secure is a mass production programming system, capable of protecting the vendor’s IP regardless of the production site. It provides full control over the programming process at contract manufacturers (CM) and similar environments.
1:打开J-Flash ARM后,首先点击File-OpenProject.,从中选择STM32F103RB.jflash。(例子芯片,直接在提示的目录下找) 2.点击File-Open data file.选择要烧录的可执行文件(.hex 或者.bin)3:options-project settings 在里面配置cpu型号,下载方式4: 选择.
To configure the J-Link/J-Trace adapter for Flash download: Choose Flash — Configure Flash Tools. From the menu, to open the Project — Options for Target — Utilities dialog. Warning: Your IP address 207.46.13.235 is public! Your Internet Provider, Government or hackers can very easily track all your activity! Enable protection.
- Authenticated production with full visibility
- Production volume control
- CM administration and setup portal
- Ultra fast programming
- Supports Cortex-M, RX, PPC
- Prevents production of counterfeit units
- No overhead in programming time
- Secure your production at contract manufacturers
- 1.Flasher Secure—How it works
- 2.End-to-End Security
- 3.Secured Firmware
- 4.Package content
J-flash Keygen
When you need to go for mass production, it is common to employ a contract manufacturer (CM) to mass-produce products. CMs have access to the customer's IP and large quantities of the components they are contracted to produce. Because of this, it is essential that customers control both their IP and limit CM production to prevent theft and secure revenue. To combat these threats, Flasher Secure uses mutual authentication, authorization, and confidentiality to secure your IP and production run. As an IP owner, you have full end-to-end control of your production chain.
End-to-End Security
Flasher Secure supports vendor-specific trusted firmware features to ensure end-to-end encryption, authentication, and confidentiality covering the whole process including the 'last mile'.
Modern products carry a huge amount of intellectual property (IP). From the IP owners point of view most of the IP is located inside the firmware. IP owners want to protect their IP. The Flasher Secure system uses authentication algorithms to make sure, that only authorized boot loaders and firmware are used in the system. If one component is not genuine, the device will stop working. Simply copying the firmware and/or bootloader from one device to another is not possible any more.
A secure production programming system capable of deploying device signatures and other security tokens is a central part of a device management system, that provides security updates during the lifetime of a product without sacrificing IP protection. SEGGER's Secure Product Lifecycle Management system provides a concept of such device management system.
Package content
More Information
Purchase
Technology
Accessories
Tools
Models
J-Flash SPI is a PC software running on Microsoft Windows (backward compatible down to Windows 2000) systems, Linux or macOS, which allows direct programming of SPI flashes via J-Link or Flasher. The flash is programmed directly via J-Link using the SPI protocol, no CPU / MCU in between.
- Direct programming of SPI flash via J-Link (no CPU / MCU in between)
- Since J-Link communicates directly with the flash, even flashes connected to CPUs not supported by J-Link can be programmed
- Cross-platform (GUI and command line version available for Windows, Linux and macOS)
- 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
- Part of the J-Link software and documentation package
- 1.J-Flash SPI - programming tool for SPI flash memories that simply works!
- 2.Licensing
- 3.20-pin connection
- 4.20-pin QSPI connection
- 5.J-Link 10-Pin Needle Adapter Connection
- 6.Which SPI flash devices are supported?
- 6.1.Atmel / Adesto DataFlash
- 7.Evaluation hardware
- 8.Command line version
- 9.Flash Programming Speed
- 10.FAQ
J-Flash SPI - programming tool for SPI flash memories that simply works!
J-Flash SPI is a PC software running on Microsoft Windows (backward compatible down to Windows 2000) systems, Linux or macOS, which allows direct programming of SPI flashes via J-Link or Flasher. The flash is programmed directly via J-Link using the SPI protocol, no CPU / MCU in between.
Most common SPI flashes are automatically recognized by their respective ID and can easily be programmed with no further setup / configuration of J-Flash SPI needed to be done by the user.
In order to use J-Flash SPI, either a higher-end J-Link model (J-Link PLUS or higher, click here for the debug probe model overview) or a Flasher Production Programmer (click here for the flash programmer model overview) is needed.
20-pin connection
The following table lists the pinout for the SPI interface on J-Link / Flasher.
| 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 J-Link, 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 J-Link, 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 J-Links may not be able to supply power on this pin. |
Pins 4, 6, 8, 10, 12 are GND pins connected to GND in J-Link. They should also be connected to GND in the target system.
*On later J-Link products like the J-Link ULTRA, these pins are reserved for firmware extension purposes. They can be left open or connected to GND.
Pinout SPI 20-pin
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:>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:>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 J-Links may not be able to supply power on this pin. |
Pins 4, 6, 8, 10, 12 are GND pins connected to GND in J-Link. They should also be connected to GND in the target system.
*On later J-Link products like the J-Link ULTRA, these pins are reserved for firmware extension purposes. They can be left open or connected to GND.
Pinout QSPI 20-pin
J-Link 10-Pin Needle Adapter Connection
The following table lists the pinout for the SPI interface on J-Link / Flasher when using the J-Link 10-pin Needle Adapter (model 8.06.04).
| 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 J-Links may not be able to supply power on this pin. |
| 6 | DO | Input | Data-out of target SPI. Input of J-Link, 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 J-Link, 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 J-Link. It should also be connected to GND in the target system.
Notes 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 J-Link should be connected to the reset of the target system or the reset pin of the CPU to make sure that J-Link can keep the CPU in reset while programming the SPI flash.
J-Flash SPI connection
J-Flash SPI is able to auto-detect common SPI flashes automatically, via their respective ID. Anyhow, 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:
Atmel / Adesto DataFlash
Atmel DataFlash is not supported by J-Flash SPI as its instruction set and handling in general is significantly different from any other SPI flash. Moreover, its page/sector size is not a power of 2, making it incompatible to existing concepts.
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.
Command line version
A command line version of J-Flash SPI is available for Windows, Linux and macOS, too. The command line version is also part of the J-Link software and documentation package. Please note that the GUI version of J-Flash SPI can also be controlled from the command line.
Due to the high performance and the efficient protocol of J-Link/Flasher, programming speeds up to the max. flash programming specified by the flash vendor, can be achieved.
| Flash device | Programming speed1 |
|---|---|
| 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
A: Please check the SEGGER wiki for more information which J-Link hardware versions support the 'SPI interface': wiki.segger.com/Software_and_Hardware_Features_Overview
More Information
Purchase
