Jflash Keygen
2021年7月25日Download here: http://gg.gg/vi33x
*J-flash Keygen
*J-flash Keygen
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
Description: j-link/jlink ARM debugger software, its operator (keygen) Downloaders recently: 柳树 豫 xuhew wangfeng song 冀军良 kinjal gelei vk HS. Bon YSS 王斌 Roberto talang mr.jeon zhao 邱石 lee sideng More information of uploader dire999. With EDU it is possible to read Flash chips using their software called ’J-Flash’ but because License reasons it is not possible to write to flashes. To do so, one had to buy the bigger and much more expensive J-Link Plus. Anyone know a way to get around this limitation and continue using the EDU? Or one of those far east clones? In order to re-program the protected FLASH sectors with Segger J-Link, I need first to unlock and mass erase the device. For this, there is the J-Link Commander utility which has a command line interface to unprotect and erase the device. For erasing only, the J-Flash (and Lite) is a very useful tool, especially to get a ‘clean’ device memory. As far as I remember the serial number is not a string but just raw hex data nearby the address where the ’GDBFull’ string is located. With this utility I have a GUI to erase and program my device. I’m not sure if ’RolfSegger’ segger j link arm keygen really from Segger or martik mah mp3 a user. Segger j link arm keygen Segger J-flash Arm.
*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.FAQJ-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. PinSignalTypeDescription1VTrefInputThis 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.2Not connectedNCLeave open on target side.3Not connectedNCLeave open on target side.5DIOutputData-input of target SPI. Output of J-Link, used to transmit data to the target SPI.7nCSOutputChip-select of target SPI (active LOW).9CLKOutputSPI clock signal.11Not connectedNCLeave open on target side.13DOInputData-out of target SPI. Input of J-Link, used to receive data from the target SPI.15nRESETOutputTarget CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called ’nRST’, ’nRESET’ or ’RESET’.17Not connectedNCLeave open on target side.195V-SupplyOutputThis 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.PinSignalTypeDescription1VTrefInputThis 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.2Not connectedNCLeave open on target side.3IO1I/OBi-directional data I/O pin 15IO0/DII/OSingle:>7nCSOutputChip-select of target SPI (active LOW).9CLKOutputSPI clock signal.11IO2I/OBi-directional data I/O pin 213DOInputSingle:>15nRESETOutputTarget CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called ’nRST’, ’nRESET’ or ’RESET’.17IO3I/OBi-directional data I/O pin 3195V-SupplyOutputThis 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-pinJ-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).PinSignalTypeDescription1VTrefInputThis 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.2nCSOutput Chip-select of target SPI (active LOW).4CLKOutput SPI clock signal.55V-SupplyOutput 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 DOInputData-out of target SPI. Input of J-Link, used to receive data from the target SPI.7Not connectedNCLeave open on target side.8DIOutput Data-input of target SPI. Output of J-Link, used to transmit data to the target SPI.9Not connectedNCLeave open on target side.10nRESETOutput 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 deviceProgramming speed1ISSI IS25LP128500 KB/sISSI IS25LD040100 KB/sISSI IS25LQ080340 KB/sISSI IS25CD010100 KB/sISSI IS25CQ032 190 KB/sMacronix MX25L3235E285 KB/sMacronix MX66L1G45G430 KB/sMacronix MX66L51235F315 KB/sMicron N25Q128A270 KB/sMicron M25P10160 KB/sMicron M25PX16230 KB/sMicron M45PE10230 KB/sMicron M25PE4 215 KB/sSpansion S25FL128410 KB/sSpansion S25FL116K265 KB/sWinbond 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_OverviewMore InformationPurchaseTechnologyAccessoriesToolsModels
J-Link Commander (JLink.exe / JLinkExe) is a free, command line based utility that can be used for verifying proper functionality of J-Link as well as for simple analysis of the target system with J-Link. It supports some simple commands, such as memory dump, halt, step, go etc. to verify the target connection. The J-Link Commander is part of the J-Link Software and Documentation Pack, which is available for download on the SEGGER webpage.
The sources of the J-Link Commander are available as part of the J-Link SDK.
*1Commands
*1.1Detailed description
*2Command line options
*2.1Detailed description
*10Command specificsCommands
The table below lists the available commands of J-Link Commander. All commands are listed in alphabetical order within their respective categories.Detailed descriptions of the commands can be found in the sections that follow.Command (short form)ExplanationBasic clrBPClear breakpoint. clrWPClear watchpoint. connect (con)Connect to target. deviceSelects a device. eraseErase internal flash of selected device. execExecute J-Link Command String. exit (qc, q)Closes J-Link Commander. exitonerror (eoe)Commander exits after error. fPrints firmware info. go (g)Starts the CPU core. halt (h)Halts the CPU core. hwinfoShow hardware info. isScan chain select register length. jtagconfConfigures a JTAG scan chain with multiple devices on it. loadfileLoad data file into target memory. logEnables log to file. memRead memory. mem8Read 8-bit items. mem16Read 16-bit items. mem32Read 32-bit items. mem64Read 64-bit items. mrMeasures reaction time of RTCK pin. msMeasures length of scan chain. powerSwitch power supply for target. rResets and halts the target. readAPReads from a CoreSight AP register. readcsrReads CSR register on a RISC-V based target. readDPReads from a CoreSight DP register. regsShows all current register values. rnhResets without halting the target. rregShows a specific register value. rxReset target with delay. savebinSaves target memory into binary file. setBPSet breakpoint. setPCSet the PC to specified value. SetTimeoutCmdSet timeout for the stepover command. setWPSet watchpoint. siSelect a target interface. speedSet target interface speed. stShows the current hardware status. step (s)Single step the target chip. stepover (so)Execute a stepover. unlockUnlocks a device. verifybinCompares memory with data file. w1Write 8-bit items. w2Write 16-bit items. w4Write 32-bit items. writeAPWrites to a CoreSight AP register. writecsrWrites CSR register on a RISC-V based target. writeDPWrites to a CoreSight DP register. wregWrite register.Flasher I/O fdelete (fdel)Delete file on emulator. flistList directory on emulator. fread (frd)Read file from emulator. fshowRead and display file from emulator. fsize (fsz)Display size of file on emulator. fwrite (fwr)Write file to emulator.Connection to J-Link ipConnect to J-Link Pro via TCP/IP. usbConnect to J-Link via USB.Configuration VCOMEnable/Disable VCOM VTREFSets a fixed value for VTref on J-Link. WebUSBDisableDisables WebUSB on J-Link. WebUSBEnableEnables WebUSB on J-Link.Detailed description
Following is a detailed description with syntax explaination and examples of the commands listed above.clrBP
This command removes a breakpoint set by J-Link.
Syntax
ParameterMeaningBP_HandleHandle of breakpoint to be removed.
Example
clrWP
This command removes a watchpoint set by J-Link.
Syntax
ParameterMeaningWP_HandleHandle of watchpoint to be removed.
Example
connect
This command establishes a connection between J-Link and target.
Note
If not set already, this command will prompt the user for settings which are needed in order to connect to the target.
Syntax
device
Selects a specific device J-Link shall connect to and performs a reconnect.In most cases explicit selection of the device is not necessary.Selecting a device enables the user to make use of the J-Link flash programming functionality as well as using unlimited breakpoints in flash memory.For some devices explicit device selection is mandatory in order to allow the DLL to perform special handling needed by the device.Some commands require that a device is set prior to use them.
Syntax
ParameterMeaningDeviceNameValid device name: Device is selected.
?: Shows a device selection dialog.
Example
erase
Erases all flash sectors or a certain flash range of the current device. A device has to be specified previously.When specified, all flash between the <StartAddr> and <EndAddr> will be erased.
Syntax
exec
Execute J-Link Command String. For more information about the usage of J-Link Command Strings please refer to J-Link Command Strings.
Syntax
ParameterMeaningCommandJ-Link Command String to be executed.
Example
exit
This command closes the target connection, the connection to the J-Link and exits J-Link Commander.
Syntax
exitonerror
This command toggles whether J-Link Commander exits on error or not.
Syntax
ParameterMeaning1/01: J-Link Commander will now exit on Error.
0: J-Link Commander will no longer exit on Error.
Example
f
Prints firmware and hardware version info. Please notice that minor hardware revisions may not be displayed, as they do not have any effect on the feature set.
Syntax
fdelete
On emulators which support file I/O this command deletes a specific file.
Syntax
ParameterMeaningFileNameFile to delete from the Flasher.
Example
flist
On emulators which support file I/O this command shows the directory tree of the Flasher.
Syntax
fread
On emulators which support file I/O this command reads a specific file.Offset applies to both destination and source file.
Syntax
ParameterMeaningEmuFileFile name to read from.HostFileDestination file on the host.OffsetSpecifies the offset in the file, at which data reading is started.NumBytesMaximum number of bytes to read.
Example
fshow
On emulators which support file I/O this command reads and prints a specific file.Currently, only Flasher models support file I/O.
Syntax
ParameterMeaningFileNameSource file name to read from the Flasher.aIf set, Input will be parsed as text instead of being shown as hex.OffsetSpecifies the offset in the file, at which data reading is started.NumBytesMaximum number of bytes to read.
Example
fsize
On emulators which support file I/O this command gets the size of a specific file.Currently, only Flasher models support file I/O.
Syntax
ParameterMeaningFileNameSource file name to read from the Flasher.
Example
fwrite
On emulators which support file I/O this command writes a specific file.Currently, only Flasher models support file I/O. NumBytes is limited to 512 bytes at once.This means, if you want to write e.g. 1024 bytes, you have to send the command twice,using an appropriate offset when sending it the second time. Offset applies to both destination and source file.
Syntax
ParameterMeaningEmuFileFile name to write to.HostFileSource file on the hostOffsetSpecifies the offset in the file, at which data writing is started.NumBytesMaximum number of bytes to write.
Example
go
Starts the CPU. In order to avoid setting breakpoints it allows to define a maximum number of instructions which can be simulated/emulated.This is particularly useful when the program is located in flash and flash breakpoints are used. Simulating instructions avoids to reprogram the flash and speeds up (single) stepping.
Syntax
ParameterMeaningNumStepsMaximum number of instructions allowed to be simulated.
Instruction simulation stops whenever a breakpointed instruction is hit, an instruction which cannot be simulated/emulated is hit or when NumSteps is reached.Flags0: Do not start the CPU if a BP is in range of NumSteps
1: Overstep BPs
Example
halt
Halts the CPU Core. If successful, shows the current CPU registers.
Syntax
hwinfo
This command can be used to get information about the power consumption of the target (if the target is powered via J-Link). It also gives the information if an overcurrent happened.
Syntax
ip
Closes any existing connection to J-Link and opens a new one via TCP/IP. If no IP Address is specified, the Emulator selection dialog shows up.
Syntax
ParameterMeaningAddrValid values:
IP Address: Connects the J-Link with the specified IP-Address
Host Name: Resolves the host name and connects to it.
*: Invokes the Emulator selection dialog.
Example
is
This command returns information about the length of the scan chain select register.
Syntax
jtagconf
Configures a JTAG scan chain with multiple devices on it.
For more detailed information on how to configure a scan chain with multiple devices please refer to Determining values for scan chain configuration.
Syntax
ParameterMeaningIRPreSum of IRLens of all devices closer to TDI, where IRLen is the number of bits in the IR (Instruction Register) of one device.DRPreNumber of devices closer to TDI.
Example
loadfile
This command programs a given data file to a specified destination address. Currently supported data files are:
**.mot
**.srec
**.s19
**.s
**.hex
**.bin
Syntax
ParameterMeaningFilenameSource filenameAddrDestination address. If not passed, 0x0 is assumed. Only used for .bin files. Ignored
https://diarynote-jp.indered.space
*J-flash Keygen
*J-flash Keygen
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
Description: j-link/jlink ARM debugger software, its operator (keygen) Downloaders recently: 柳树 豫 xuhew wangfeng song 冀军良 kinjal gelei vk HS. Bon YSS 王斌 Roberto talang mr.jeon zhao 邱石 lee sideng More information of uploader dire999. With EDU it is possible to read Flash chips using their software called ’J-Flash’ but because License reasons it is not possible to write to flashes. To do so, one had to buy the bigger and much more expensive J-Link Plus. Anyone know a way to get around this limitation and continue using the EDU? Or one of those far east clones? In order to re-program the protected FLASH sectors with Segger J-Link, I need first to unlock and mass erase the device. For this, there is the J-Link Commander utility which has a command line interface to unprotect and erase the device. For erasing only, the J-Flash (and Lite) is a very useful tool, especially to get a ‘clean’ device memory. As far as I remember the serial number is not a string but just raw hex data nearby the address where the ’GDBFull’ string is located. With this utility I have a GUI to erase and program my device. I’m not sure if ’RolfSegger’ segger j link arm keygen really from Segger or martik mah mp3 a user. Segger j link arm keygen Segger J-flash Arm.
*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.FAQJ-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. PinSignalTypeDescription1VTrefInputThis 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.2Not connectedNCLeave open on target side.3Not connectedNCLeave open on target side.5DIOutputData-input of target SPI. Output of J-Link, used to transmit data to the target SPI.7nCSOutputChip-select of target SPI (active LOW).9CLKOutputSPI clock signal.11Not connectedNCLeave open on target side.13DOInputData-out of target SPI. Input of J-Link, used to receive data from the target SPI.15nRESETOutputTarget CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called ’nRST’, ’nRESET’ or ’RESET’.17Not connectedNCLeave open on target side.195V-SupplyOutputThis 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.PinSignalTypeDescription1VTrefInputThis 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.2Not connectedNCLeave open on target side.3IO1I/OBi-directional data I/O pin 15IO0/DII/OSingle:>7nCSOutputChip-select of target SPI (active LOW).9CLKOutputSPI clock signal.11IO2I/OBi-directional data I/O pin 213DOInputSingle:>15nRESETOutputTarget CPU reset signal (active LOW). Typically connected to the reset pin of the target CPU, which is typically called ’nRST’, ’nRESET’ or ’RESET’.17IO3I/OBi-directional data I/O pin 3195V-SupplyOutputThis 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-pinJ-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).PinSignalTypeDescription1VTrefInputThis 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.2nCSOutput Chip-select of target SPI (active LOW).4CLKOutput SPI clock signal.55V-SupplyOutput 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 DOInputData-out of target SPI. Input of J-Link, used to receive data from the target SPI.7Not connectedNCLeave open on target side.8DIOutput Data-input of target SPI. Output of J-Link, used to transmit data to the target SPI.9Not connectedNCLeave open on target side.10nRESETOutput 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 deviceProgramming speed1ISSI IS25LP128500 KB/sISSI IS25LD040100 KB/sISSI IS25LQ080340 KB/sISSI IS25CD010100 KB/sISSI IS25CQ032 190 KB/sMacronix MX25L3235E285 KB/sMacronix MX66L1G45G430 KB/sMacronix MX66L51235F315 KB/sMicron N25Q128A270 KB/sMicron M25P10160 KB/sMicron M25PX16230 KB/sMicron M45PE10230 KB/sMicron M25PE4 215 KB/sSpansion S25FL128410 KB/sSpansion S25FL116K265 KB/sWinbond 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_OverviewMore InformationPurchaseTechnologyAccessoriesToolsModels
J-Link Commander (JLink.exe / JLinkExe) is a free, command line based utility that can be used for verifying proper functionality of J-Link as well as for simple analysis of the target system with J-Link. It supports some simple commands, such as memory dump, halt, step, go etc. to verify the target connection. The J-Link Commander is part of the J-Link Software and Documentation Pack, which is available for download on the SEGGER webpage.
The sources of the J-Link Commander are available as part of the J-Link SDK.
*1Commands
*1.1Detailed description
*2Command line options
*2.1Detailed description
*10Command specificsCommands
The table below lists the available commands of J-Link Commander. All commands are listed in alphabetical order within their respective categories.Detailed descriptions of the commands can be found in the sections that follow.Command (short form)ExplanationBasic clrBPClear breakpoint. clrWPClear watchpoint. connect (con)Connect to target. deviceSelects a device. eraseErase internal flash of selected device. execExecute J-Link Command String. exit (qc, q)Closes J-Link Commander. exitonerror (eoe)Commander exits after error. fPrints firmware info. go (g)Starts the CPU core. halt (h)Halts the CPU core. hwinfoShow hardware info. isScan chain select register length. jtagconfConfigures a JTAG scan chain with multiple devices on it. loadfileLoad data file into target memory. logEnables log to file. memRead memory. mem8Read 8-bit items. mem16Read 16-bit items. mem32Read 32-bit items. mem64Read 64-bit items. mrMeasures reaction time of RTCK pin. msMeasures length of scan chain. powerSwitch power supply for target. rResets and halts the target. readAPReads from a CoreSight AP register. readcsrReads CSR register on a RISC-V based target. readDPReads from a CoreSight DP register. regsShows all current register values. rnhResets without halting the target. rregShows a specific register value. rxReset target with delay. savebinSaves target memory into binary file. setBPSet breakpoint. setPCSet the PC to specified value. SetTimeoutCmdSet timeout for the stepover command. setWPSet watchpoint. siSelect a target interface. speedSet target interface speed. stShows the current hardware status. step (s)Single step the target chip. stepover (so)Execute a stepover. unlockUnlocks a device. verifybinCompares memory with data file. w1Write 8-bit items. w2Write 16-bit items. w4Write 32-bit items. writeAPWrites to a CoreSight AP register. writecsrWrites CSR register on a RISC-V based target. writeDPWrites to a CoreSight DP register. wregWrite register.Flasher I/O fdelete (fdel)Delete file on emulator. flistList directory on emulator. fread (frd)Read file from emulator. fshowRead and display file from emulator. fsize (fsz)Display size of file on emulator. fwrite (fwr)Write file to emulator.Connection to J-Link ipConnect to J-Link Pro via TCP/IP. usbConnect to J-Link via USB.Configuration VCOMEnable/Disable VCOM VTREFSets a fixed value for VTref on J-Link. WebUSBDisableDisables WebUSB on J-Link. WebUSBEnableEnables WebUSB on J-Link.Detailed description
Following is a detailed description with syntax explaination and examples of the commands listed above.clrBP
This command removes a breakpoint set by J-Link.
Syntax
ParameterMeaningBP_HandleHandle of breakpoint to be removed.
Example
clrWP
This command removes a watchpoint set by J-Link.
Syntax
ParameterMeaningWP_HandleHandle of watchpoint to be removed.
Example
connect
This command establishes a connection between J-Link and target.
Note
If not set already, this command will prompt the user for settings which are needed in order to connect to the target.
Syntax
device
Selects a specific device J-Link shall connect to and performs a reconnect.In most cases explicit selection of the device is not necessary.Selecting a device enables the user to make use of the J-Link flash programming functionality as well as using unlimited breakpoints in flash memory.For some devices explicit device selection is mandatory in order to allow the DLL to perform special handling needed by the device.Some commands require that a device is set prior to use them.
Syntax
ParameterMeaningDeviceNameValid device name: Device is selected.
?: Shows a device selection dialog.
Example
erase
Erases all flash sectors or a certain flash range of the current device. A device has to be specified previously.When specified, all flash between the <StartAddr> and <EndAddr> will be erased.
Syntax
exec
Execute J-Link Command String. For more information about the usage of J-Link Command Strings please refer to J-Link Command Strings.
Syntax
ParameterMeaningCommandJ-Link Command String to be executed.
Example
exit
This command closes the target connection, the connection to the J-Link and exits J-Link Commander.
Syntax
exitonerror
This command toggles whether J-Link Commander exits on error or not.
Syntax
ParameterMeaning1/01: J-Link Commander will now exit on Error.
0: J-Link Commander will no longer exit on Error.
Example
f
Prints firmware and hardware version info. Please notice that minor hardware revisions may not be displayed, as they do not have any effect on the feature set.
Syntax
fdelete
On emulators which support file I/O this command deletes a specific file.
Syntax
ParameterMeaningFileNameFile to delete from the Flasher.
Example
flist
On emulators which support file I/O this command shows the directory tree of the Flasher.
Syntax
fread
On emulators which support file I/O this command reads a specific file.Offset applies to both destination and source file.
Syntax
ParameterMeaningEmuFileFile name to read from.HostFileDestination file on the host.OffsetSpecifies the offset in the file, at which data reading is started.NumBytesMaximum number of bytes to read.
Example
fshow
On emulators which support file I/O this command reads and prints a specific file.Currently, only Flasher models support file I/O.
Syntax
ParameterMeaningFileNameSource file name to read from the Flasher.aIf set, Input will be parsed as text instead of being shown as hex.OffsetSpecifies the offset in the file, at which data reading is started.NumBytesMaximum number of bytes to read.
Example
fsize
On emulators which support file I/O this command gets the size of a specific file.Currently, only Flasher models support file I/O.
Syntax
ParameterMeaningFileNameSource file name to read from the Flasher.
Example
fwrite
On emulators which support file I/O this command writes a specific file.Currently, only Flasher models support file I/O. NumBytes is limited to 512 bytes at once.This means, if you want to write e.g. 1024 bytes, you have to send the command twice,using an appropriate offset when sending it the second time. Offset applies to both destination and source file.
Syntax
ParameterMeaningEmuFileFile name to write to.HostFileSource file on the hostOffsetSpecifies the offset in the file, at which data writing is started.NumBytesMaximum number of bytes to write.
Example
go
Starts the CPU. In order to avoid setting breakpoints it allows to define a maximum number of instructions which can be simulated/emulated.This is particularly useful when the program is located in flash and flash breakpoints are used. Simulating instructions avoids to reprogram the flash and speeds up (single) stepping.
Syntax
ParameterMeaningNumStepsMaximum number of instructions allowed to be simulated.
Instruction simulation stops whenever a breakpointed instruction is hit, an instruction which cannot be simulated/emulated is hit or when NumSteps is reached.Flags0: Do not start the CPU if a BP is in range of NumSteps
1: Overstep BPs
Example
halt
Halts the CPU Core. If successful, shows the current CPU registers.
Syntax
hwinfo
This command can be used to get information about the power consumption of the target (if the target is powered via J-Link). It also gives the information if an overcurrent happened.
Syntax
ip
Closes any existing connection to J-Link and opens a new one via TCP/IP. If no IP Address is specified, the Emulator selection dialog shows up.
Syntax
ParameterMeaningAddrValid values:
IP Address: Connects the J-Link with the specified IP-Address
Host Name: Resolves the host name and connects to it.
*: Invokes the Emulator selection dialog.
Example
is
This command returns information about the length of the scan chain select register.
Syntax
jtagconf
Configures a JTAG scan chain with multiple devices on it.
For more detailed information on how to configure a scan chain with multiple devices please refer to Determining values for scan chain configuration.
Syntax
ParameterMeaningIRPreSum of IRLens of all devices closer to TDI, where IRLen is the number of bits in the IR (Instruction Register) of one device.DRPreNumber of devices closer to TDI.
Example
loadfile
This command programs a given data file to a specified destination address. Currently supported data files are:
**.mot
**.srec
**.s19
**.s
**.hex
**.bin
Syntax
ParameterMeaningFilenameSource filenameAddrDestination address. If not passed, 0x0 is assumed. Only used for .bin files. Ignored
https://diarynote-jp.indered.space
コメント