Transition from KEIL4 to MDK5, the first problem encountered is to download the MDK prompt need to upgrade the Keil firmware, a think of the environment is not the same, estimated that the estimated need to upgrade, so the hands of the upgrade, so the tragedy, the project interrupted, Daoteng firmware repair Daoteng a day, the following is the problem encountered.
After the firmware repair, jlink on the lights on, not bright, firmware upgrade has also done, not difficult, but seems to forget a problem, the original development environment in WinXP, and later replaced by Win7 64, is this environment let me depressed a day
1. Under Win XP can use the Jlink repair tutorial in Win7 can not use Sam-prog software write Flash is gray, the driver can not be loaded, unrecognized, and Sam-ba v2.9 under Win7 32-bit computer although it is recognizable, but after the dot connect, Will pop up error found an invalid ID, check for half a day, can't solve this problem, so change method.
Consult the information, said is Sam-ba v2.12 can win7 64 bit, good under a v2.12, put up after, can solve the driving problem, Jlink inserted after the recognition is at91-serial ... (forget), but choose a good COM port, board for At91sam7s64-ek, Dot Connect, no response, thought the computer card, restart several times, or the same, at this point, completely abandoned the Win7 under the scheme
In Win7 installed XP virtual machine, first installed the Win7 comes with XP mode, and then found that it is always unable to identify the jlink is not good to unload
And then try to install XP virtual machine under VMware, online tutorials are many, but also much more wrong, those who wrote the author did it???? Installation is not as smooth as Ubuntu, regardless of whether your image is. iso or. Gho, you need to format the disk, partition, specific tutorials in this
Http://jingyan.baidu.com/article/c1a3101eedfde0de656debf5.html
2. During this time, the problem is that after the partition is good, the virtual machine restart will start from the disk, and the disk at this time to format nothing, will display ntbl is missing, the solution is to let the virtual machine boot from the CD drive, that is, load your XP image, the actual operation is the virtual machine boot , the right hand crazy point mouse, left-handed F2, enter the BIOS, modify the boot sequence .
Win XP environment, the success of the half, now the problem is that you have to Jlink plug in, the Win7 under the time is not recognized, it is necessary to rob it to the virtual machine, the specific operation is in the virtual machine has a row of charts, find the Jlink of the chart, and then right click on the connection, the chart is lightened, is loaded into the virtual machine inside, at this time must keep the virtual machine network unblocked, with Bridge or NAT, as long as there is a network , and then XP will automatically identify the Jlink drive is atmel6214 ... You can then burn some firmware with Sam-prog in the tutorial.
Key key in, erase mouth and TST Port of the short connection is correct, the environment in the XP environment will be a lot smoother, not the words of their own creation, do not go to the Internet cafes, and the four or five Internet cafes are the win 7, attached to the firmware repair tutorial, software and Jlink V8 firmware.
About Win7 below Jlink firmware fix