WIN10 64-bit Jlink V8 firmware Loss Repair Summary

The adjustment of the morning of the program, the line of sight did not leave a while, and then found that Jlink automatically disconnected, and then reseat the Jlink, restart are not, only to find that the light has not been lit, the original firmware is damaged, decisive ways to repair the big uncle.

Previously fixed this problem, but then the system is Win7 32 bit, now with WIN10 64 bit do not know can repair, so check data, repair process as follows:

#0, prepare tools before starting
1.sam-ba v2.12.exe for burning firmware,: http://download.csdn.net/detail/hzt12345hf/9457629

The new version of Sam-ba (for example, Sam-ba v2.9) is not properly connected to Jlink, so this version is still used.

2.JLink V8 firmware,: http://download.csdn.net/detail/hzt12345hf/9457633

Be sure to use this firmware, other firmware will cause "J-link the Connected emulator is a J-link clone" "problem, that is jlink not genuine, for specific reasons please check this sticker: http://blog.sina.com.cn/s/ Blog_8a30d1990102vo66.html

3. Latest Jlink drive,: https://www.segger.com/jlink-software.html

#1, the first is to erase the Jlink Flash program (the chip is Atmel's AT91SAM7S64), through the short-circuit erase (a place in the figure) to achieve erasure:

Step Requirements:

1) power on first.

　　2) short-connect erase (J1), keep the short-connect state 20s.

　　3) power off. 4) Remove the short connection

The three versions commonly used on the market Jlink short-connect locations slightly different, as shown in:

#2, then copy the Sam-ba Boot firmware to the first two sectors of flash, by short-connect the TST (Figure B) to achieve
Step Requirements:

　　1) Short-Connection TST (J2).

　　2) power on, and keep short connect 30s.

　　3) power off. 4) Remove the short connection.

#3, installed Sam-ba v2.12, reconnect Jlink to the computer, will prompt to install the driver, however I use WIN10 and do not see the installation driver, are the system automatically installed, just see this in the Device Manager, as long as there is this can be.

The default must be "Bossa program Port" or "USB Serial Device" the words, if you can not try to roll back drive or update driver, the driving position in the Sam-ba_ 2.12 in the DRV folder in the installation directory. As shown in the following:

#4, install the driver, open the SAM-BA_2.12 program, select the corresponding COM port, select the chip model, Jlink the default chip is AT91SAM7S64, then connect into the main interface.

#5, the default configuration is that nothing needs to change, click the File Selection button to the right of the send filename, select the downloaded Jlink-v8.bin file, and then click the Send File button to burn the firmware.

Note: When burning, you will be prompted whether to lock flash, you need to click Yes, as shown in:

After burning, will prompt whether to lock flash, I found that click Yes, locked after the firmware can not be updated, so I generally choose No. If you don't want to update the firmware, you can click Yes.

Burn the Write success interface as shown in:

#6, to this, re-plug the Jlink can be used again.

Small additions:

If you open it using the Jlink command mode, as shown in:

First prompt update, dot yes or no can, I wearies click Yes, let it update,

After the update, a variety of jlink information is displayed.
If there is no connection to the microcontroller interface as shown below:

If the interface after connecting to the microcontroller is as follows:

Note, however, recently found that the update Jlink firmware after a variety of problems, and Jlink's burning tool Jflash use the latest version is also prone to burning problems, as to why everyone knows (piracy problem), so the general Jlink must not update the firmware upgrade , Jlink Drive also try not to use the latest, as long as you can use to try not to change, otherwise various problems, the current test of 5.10 is no problem.

The original URL link is: http://blog.csdn.net/hzt12345hf/article/details/50846447

WIN10 64-bit Jlink V8 firmware Loss Repair Summary