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? Topic: Segger J-Link ARM + Keygen (Read 28215 times) 0 Members and 1 Guest are viewing this topic. Newbie Offline Posts: 7 Thank You-Given: 4. Found 12 results for segger j flash arm v4.00a serial number. Search from over ninety-thousand serial numbers at SerialShack. SEGGER J-FLASH ARM KEYGEN: Depending on what you use the app for and who you communicate with through it, the timer feature may just be a novelty, or it may serve a.
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
J-flash Keygen
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.
J-flash Keygen
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
Technology
Accessories
Tools
Models
You can buy a Segger JTAG J-Link clone for few USD on, aliexpress, dx. If you try to update its firmware with the official Segger tool, you'll brick the probe.
Don't worry, smart people have already put a checklist to restore a working firmware and even update it to the latest official version. I just put all the needed info into one single page. Unbrick it To restore the firmware, you need to follow the instruction from The best part? It works from Linux. For the step 9, you'll need the binary image to flash; use that one. It's from the same forum than above but without password and without additional useless.exe files. Download and install SAM-BA package from atmel.com.
Metadoll flash; Segger j-flash arm; Rmclock pro. Complete v2 coremelt keygen. Coremelt v2 complete key generator.
Open the j-link case by gently popping the plastic edge near the jtag or usb ports. Identify the ERASE (pin 50) / TST (pin 40) jumpers/pins. Short ERASE jumper to pull-high and connect the jlink to usb; wait for a minute and disconnect usb.
('pull-high', means set a jumper between the ERASE pin and the 3.3V pin next to it.). Remove the ERASE jumper and short the TST jumper to pull-high and connect the jlink to usb; wait for a minute and disconnect usb. Break/remove the TST jumper and reconnect USB.
Your jlink should now be identified as AT91 USB to serial adapter and a COM port should be assigned to it - if this doesn't happen repeat from step 3. Something like cdcacm 1-1.2:1.0: ttyACM0: USB ACM device should appear in syslog or dmesg. Open SAM-BA program; select COM/ttyACM port that was assigned to your jlink and in board select 'at91sam7s64-ek'; click CONNECT. Select 'FLASH' and select the BIN file you downloaded before and select to load the firmware into flash; the application will ask you if you want to unlock - select YES; at the end of programming there will be a similar question if you want to lock - select NO! (very important).
Congratulations, you are done. Reconnect the device and you should have a working jlink Update the firmware The previous step will reflash with a firmware from 2009. Info: J-Link ARM V8 compiled May 27 2009 17:31:22 Quite old and I prefer to have the latest one. Fortunately, the firmware you just flashed has a fake SerialNumber set to -1 and it happens to be enough to let the J-Link Configurator tool to flash it to the latest firmware without bricking it. This time you'll need a windows machine.
I used a Windows10 image under vmware and it worked fine. go to and fetch the Windows software pack. The one I used was version 5.00g. install it and run the J-Link Configurator. It should detect the probe and allow you to update it to the latest firmware. Congratulations, you are done. Reconnect the device and you should have a working J-Link this the latest firmware Info: J-Link ARM V8 compiled Nov 28 2014 13:44:46 Edit1 While origin of the binary firmware used in this tuto remains unknown, several posts suggest to modify the 'GDBFull' string to either 'GDBFULL' or 'GDB' From: After found the BIN file, you have to open it with an hex editor and change the string 'GDBFull' with 'GDB' and also change the serial number.
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. Remember the raw data are little-endian. For the new serial number use something like '4054xxxx' where xxxx are random numbers. You need to change the serial number or you will get this error message about the device being 'defective'. I highly suggest that you DO NOT upgrade the firmware to a newer version until you first establish your own unique serial number (one that hasn't been 'blacklisted'). Only then will you be guaranteed success. To do that you use the 'J-Link Commander' program.
The serial number is NOT stored in the binary firmware file. It gets stored in the EEPROM of the SAM7S64 chip. The newer J-Link DLLs will cause the 'error message' if they see a serial number hasn't been set or if the serial number is one that is known to be used for 'fake' devices. You use the 'J-Link Commander' to set the serial: 1) Start J-Link Commander. 2) At the prompt, enter (without the quotation marks): 'Exec SetSN = xxxxxxxx'. Choose an eight digit number, in place of the 'x's in that command, perhaps something in the range of 37000000 to 45000000 range. 3) Hit enter so it stores that in your j-link device.
Segger J Link
4) Exit J-Link Commander (type: 'exit' and hit ). 5) Run J-Link Configurator and upgrade the firmware. You should see the serial number that you set from now on (not -1 and )! Now your device should work without problems. I wasted a lot of time trying to inject serial numbers into the binary firmware file. It doesn't live there and I hope that you don't end up losing a lot of time doing the same. There is a lot of different methods found online to erase the Atmel chip in the j-link.
Segger Flasher
Atmel has their procedure for erasing the chip and restoring the bootloader. This is how it should be: Power the device. Put the ERASE jumper on. Wait at least one second. Remove power. Now, with the power OFF remove the ERASE jumper and instead apply the TST jumper instead.
Power the device and WAIT AT LEAST 10 SECONDS (the bootloader is being transferred internally in the chip at this time). Remove power. Now remove the TST jumper. Now when connected to your computer, the device should show up as a device that the ATMEL Sam-ba program can talk to. This will be the best way to start fresh, so you can load the old (2009) firmware that allows for an upgrade. Again, remember to only attempt the upgrade to a newer version of j-link firmware AFTER you have established your own, new Serial Number.!! One other thing that I forgot to mention.
It is probably necessary to use a binary file editor and change the 'old' firmware (2009 version) so that the string 'GDBFull' is altered. I substituted four space characters in place of the 'Full' part and it worked. Seems like others used all-caps for the rest of 'Full' instead (result: GDBFULL).
It could be that the upgrade process will key on the lower case version and know that it 'isn't proper'.!? Pierre, I would like to suggest that you post a binary file with the string edited to be GDBFULL or just GDB instead of the file that is there now.
It would make it easier for everyone downloading that by removing the steps needed to edit the file.! Regardless, ENORMOUS THANKS for providing the file that is there currently!!!!!
I found a workaround to debug Keil software with H-JTAG(free). How to configure KEIL(uVision3.51) with JTAG? In Keil, open ProjectOptions for targetDebugUse RDI interface DriverSettingsBrowser and search for Yr. H-JTAG.dll in approprite folder. With a cheap Olimex Wiggler it could work like a true debugger(tracing, stepping and so on).
But watch out, unless You're a pro, practice a lot. I actually used the H-JTAG v. 9 and - beside that Segger couldn't either download or debug my code- I was able to download my code via the RS232 interface and later correct the code until it was errorfree and, again download the correct code. Don't fret, there's always a workaround cheap JTAG stuff Godd luck « Last Edit: July 02, 2009, 08:44:04 08:44 by robban » Logged. This is the question. In the ARM toolset there are: 1.
Display functions. SPI and I2C functions. CAN functions.
Elemental IO functions. Send profile data (??). If you are interested in more details what is available, on the NI site there is 374931b.pdf file 'Getting Started with the LabVIEW Embedded module for ARM.
I'm quoting from this doc: 'New Memory Access VIs The Embedded Module for ARM Microcontrollers now includes a Memory Access palette, which includes the following VIs:. CCG Mem Peek 8. CCG Mem Peek 16. CCG Mem Peek 32. CCG Mem Poke 8. CCG Mem Poke 16.
CCG Mem Poke 32 Use these VIs to read and write values to specific memory addresses.' Is it sufficient?