loadinghead.netlify.com

SEGGER's in-circuit flash programming solutions are ultra-fast and reliable making them the perfect choice for mass production environments. Closing the gap between RISC-V and Arm for embedded applications. Watch how the SEGGER J-Link WiFi’s 2.4 GHz 802.11 a/b/g/n WiFi interface removes the physical connection between J-Link and the host. (, 12:38 AM) madgot Wrote: Hi, i have an Segger J-Link Edu interface to use with JTAG-programming of flash chips. 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.

1. Segger J Flash Lite V6.40
2. Segger J Flash 4.84a Download

When using a bootloader (see “Serial Bootloader for the Freedom Board with Processor Expert“), then I usually protect the bootloader FLASH areas, so it does not get accidentally erased by the application ;-). When programming my boards with the P&E Multilink, then the P&E firmware will automatically unlock and erase the chip. That’s not the same if working with the Segger J-Link, as it but requires extra steps.

If I try to re-program the protected bootloader with Segger J-Link (both in CodeWarrior and Eclipse/KDS with GDB), then the download silently fails. The effect is that somehow the application on the board does not match what it should be. Looking at the Console view, it shows that erase has failed (but no real error reported) :-(:

Vampire diaries soundtrack free download zip. J-Link Failed to Erase in CodeWarrior

The GNU ARM Eclipse Segger integration with GDB (e.g. Kinetis Design Studio) is not better: no error sign, the only thing is a hidden ERROR in the Console log of the JLinkGDBServerCL:

ERROR Algo135 Flash Protection Violation about failed FLASH Programming

What I need is to unprotect the memory and then erase it.

The Segger J-Link features a very fast programming. Part of that speed is that the Segger firmware checks each FLASH page if it really needs to be programmed, and only then it erases and reprogrammed that page. So downloading twice the same application actually will not touch the FLASH memory at all. Additionally, it does not do a complete erase of the device: it only programs the pages I’m using in my application. The advantage of that is first speed. And it does not erase the application data I’m using in non-volatile memory (see “Configuration Data: Using the Internal FLASH instead of an external EEPROM“). However, sometimes I really need to clear all my data in FLASH too, and then I need to erase all my FLASH pages on the device.

Segger has product named ‘J-Flash’ which is used to Flash and Erase devices outside of an IDE. There is a free-of-charge ‘Lite’ version available for download from Segger. This utility is not intended to be used for production. With this utility I have a GUI to erase and program my device.

But J-Flash Lite cannot unlock my locked FLASH pages :-(.

If my device is not locked, I can use the CodeWarrior ‘Flash file to target’ (see “Flashing with a Button (and a Magic Wand)“) to erase the device:

Erasing Device with Flash File to Target

Again, this does not work if the device is locked. CodeWarrior has another feature called ‘Target Task’ which can be used to erase/unsecure (if your device is supported), see “Device is secure?“.

So I need to use a different tool to unlock and unprotect my device: the J-Link Commander.

To unlock the device, Segger has a utility named ‘J-Link Commander’, available from http://www.segger.com/jlink-software.html. The binary is ‘jlink.exe’ on Windows and is a command line utility. To unlock the device use

But it seems that I need to do an unlock, followed by an erase to make it permanent. To erase the device, I can use the same command line utility. But I need to specify the device name first, and then I can erase it (example for the KL25Z):

❗ I need to do the erase operation right after the unlock. a) set device b) unlock and c) erase, otherwise it will fail?

Unlocking and Erasing with J-Link Commander

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.

To me, the Segger way and tools are very powerful. In this case, things are very flexible, but not that obvious. So I hope this post can help others to get his device unlocked and erased.

Happy Erasing 🙂

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. Cla vocals for mac 2017. 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.

Segger J Flash Lite V6.40

CCG Mem Poke 32 Use these VIs to read and write values to specific memory addresses.' Is it sufficient?

Segger J Flash 4.84a Download