Build ARM embedded development environment

Project objectives ： stay KeilMDK Development in environment AMR Embedded system

Host environment ：window 7

 

One , install KeilMDK v4.20

【1】 download keiMDK v4.20, decompression

Install first mdk420.exe, stay mkd420 double-click , By default , All the way next, installation is complete .

【2】 decompression MDKKEYGEN_3.5-4.20.rar To the current folder , Release keygen.exe.

Then start the installation keil uVision4, Double click keygen.exe Open its interface

【3】 Click on File->License Management, as follows

 

Copy right CID The contents of the column , Paste into the following figure CID Column , And on the right Target Select ARM

Click on "Generate", In the text column above it LIC code , Then copy it , Go to the above figure License Management Of LIC Paste in the column , And then click “Add LIC”, Registration is complete . And then restart Keil uVision4 take effect .

 

Two , install JLink

 JLink The drive package for is Setup_JLinkARM_V424c.zip, You can find , Unzip it , Then double click. , Can be installed .

3、 ... and , install Proteus Simulation environment

【1】 What's installed here is proteus 7.8 sp2 edition , Download address ：http://www.qjwm.com/down_1894872.html

After downloading and decompressing, see the following figure

 

  double-click P77.8sp2.exe, All the way by default next, Be careful , When installed license when , Navigate to the installation package *.lxk file , Until completion .

【2】 To crack

Double click on Proteus Pro 7.8 SP2 Crack 1.0.exe, Here's the picture

 

 

Click on “ Browse ”, Locate the proteus Installation directory , Then click upgrade , A moment later , You can see the message dialog box of successful upgrade .

Four ,keilMDK and proteus Joint tune

【1】 Install the joint commissioning patch vdmagdi.exe, You can find

Then double click to install by default .

【2】MDK4 How to set it up

find keilMDK4 Under the root directory of the installation directory tools.ini file , Open in Notepad

find “[ARM]”, In the code 7 Line is , It can be used “ edit -> lookup ”, take [ARM] The blue bold part under the label , namely TDRV12=BIN\VDMARM.DLL ("Proteus VSM Simulator") The first two lines Copy , And then to [ARMADS] Paste the red part under the label, that is TDRV12=BIN\VDMARM.DLL ("Proteus VSM Simulator") The first two lines . After that CPUDLL0 Add the following red part in the brackets of the line , namely TDRV12, The results are as follows ：

[ARM]
PATH="C:\Keil\ARM\"
VERSION=4.20
PATH1="C:\Program Files\CodeSourcery\Sourcery G++ Lite\"
TOOLPREFIX=arm-none-eabi-
CPUDLL0=SARM.DLL(TDRV0,TDRV5,TDRV6,TDRV10,TDRV12)                             # Drivers for

ARM7/9 devices
CPUDLL1=SARMCM3.DLL(TDRV1,TDRV2,TDRV3,TDRV4,TDRV5,TDRV7,TDRV8,TDRV9,TDRV11)   # Drivers for

Cortex-M devices
CPUDLL2=SARMCR4.DLL(TDRV7)                                                    # Drivers for

Cortex-R4 devices
BOOK0=HLP\RELEASE_NOTES.HTM("Release Notes",GEN)
BOOK1=HLP\ARMTOOLS.chm("Complete User's Guide Selection",C)
BOOK2=HLP\RL_RELEASE_NOTES.HTM("RL-ARM Release Notes",GEN)
BOOK3=HLP\RVI.chm("RV Compiler Introduction",GEN)
BOOK4=CMSIS\index.htm("CMSIS Documentation",GEN)
BOOK5=C:\Program Files\CodeSourcery\Sourcery G++ Lite\share\doc\arm-2007q3-53-arm-none-

eabi\pdf\gcc\gcc.pdf("GNU C Compiler",GEN)
BOOK6=C:\Program Files\CodeSourcery\Sourcery G++ Lite\share\doc\arm-2007q3-53-arm-none-

eabi\pdf\as.pdf("GNU Assembler",GEN)
BOOK7=C:\Program Files\CodeSourcery\Sourcery G++ Lite\share\doc\arm-2007q3-53-arm-none-

eabi\pdf\ld.pdf("GNU Linker",GEN)
BOOK8=C:\Program Files\CodeSourcery\Sourcery G++ Lite\share\doc\arm-2007q3-53-arm-none-

eabi\pdf\binutils.pdf("GNU Binary Utilities",GEN)
BOOK9=Signum\Docs\SigUV3Arm.htm("Signum Systems JTAGjet Driver Documentation",GEN)
TDRV0=BIN\UL2ARM.DLL("ULINK ARM Debugger")
TDRV1=BIN\UL2CM3.DLL("ULINK Cortex Debugger")
TDRV2=BIN\AGDIRDI.DLL("RDI Interface Driver")
TDRV3=BIN\ABLSTCM.dll("Altera Blaster Cortex Debugger")
TDRV4=BIN\lmidk-agdi.dll("Stellaris ICDI")
TDRV5=Signum\SigUV3Arm.dll("Signum Systems JTAGjet")
TDRV6=Segger\JLTAgdi.dll("J-LINK / J-TRACE")
TDRV7=Segger\JL2CM3.dll("Cortex-M/R J-LINK/J-Trace")
TDRV8=STLink\ST-LINKIII-KEIL.dll ("ST-Link Debugger")
TDRV9=BIN\ULP2CM3.DLL("ULINK Pro Cortex Debugger")
TDRV10=BIN\ULP2ARM.DLL("ULINK Pro ARM Debugger")
TDRV11=NULink\Nu_Link.dll("NULink Debugger")
DELDRVPKG0=ULINK\UninstallULINK.exe("ULINK Pro Driver V1.0")
LIC0=76FVE-54G9J-9GA70-BNFXE-MV3YB-KY1EC
TDRV12=BIN\VDMARM.DLL ("Proteus VSM Simulator")
BOOK10=HLP\VDMAGDI.HLP ("Proteus VSM AGDI Driver")
[ARMADS]
PATH="C:\Keil\ARM\"
PATH1="BIN40\"
CPUDLL0=SARM.DLL(TDRV0,TDRV5,TDRV6,TDRV10,TDRV12)                             # Drivers for

ARM7/9 devices
CPUDLL1=SARMCM3.DLL(TDRV1,TDRV2,TDRV3,TDRV4,TDRV5,TDRV7,TDRV8,TDRV9,TDRV11)   # Drivers for

Cortex-M devices
CPUDLL2=SARMCR4.DLL(TDRV7)                                                    # Drivers for

Cortex-R4 devices
BOOK0=HLP\RELEASE_NOTES.HTM("Release Notes",GEN)
BOOK1=HLP\ARMTOOLS.chm("Complete User's Guide Selection",C)
BOOK2=HLP\RL_RELEASE_NOTES.HTM("RL-ARM Release Notes",GEN)
BOOK3=HLP\RVI.chm("RV Compiler Introduction",GEN)
BOOK4=CMSIS\index.htm("CMSIS Documentation",GEN)
BOOK5=Signum\Docs\SigUV3Arm.htm("Signum Systems JTAGjet Driver Documentation",GEN)
TDRV0=BIN\UL2ARM.DLL("ULINK ARM Debugger")
TDRV1=BIN\UL2CM3.DLL("ULINK Cortex Debugger")
TDRV2=BIN\AGDIRDI.DLL("RDI Interface Driver")
TDRV3=BIN\ABLSTCM.dll("Altera Blaster Cortex Debugger")
TDRV4=BIN\lmidk-agdi.dll("Stellaris ICDI")
TDRV5=Signum\SigUV3Arm.dll("Signum Systems JTAGjet")
TDRV6=Segger\JLTAgdi.dll("J-LINK / J-TRACE")
TDRV7=Segger\JL2CM3.dll("Cortex-M/R J-LINK/J-Trace")
TDRV8=STLink\ST-LINKIII-KEIL.dll ("ST-Link Debugger")
TDRV9=BIN\ULP2CM3.DLL("ULINK Pro Cortex Debugger")
TDRV10=BIN\ULP2ARM.DLL("ULINK Pro ARM Debugger")
TDRV11=NULink\Nu_Link.dll("NULink Debugger")
TDRV12=BIN\VDMARM.DLL ("Proteus VSM Simulator")
BOOK10=HLP\VDMAGDI.HLP ("Proteus VSM AGDI Driver")
RTOS0=Dummy.DLL("Dummy")
RTOS1=VARTXARM.DLL ("RTX Kernel")
DELDRVPKG0=ULINK\UninstallULINK.exe("ULINK Pro Driver V1.0")
[KARM]
TDRV0=BIN\VDMARM.DLL ("Proteus VSM Simulator")
BOOK0=HLP\VDMAGDI.HLP ("Proteus VSM AGDI Driver")
[C51]
TDRV0=BIN\VDM51.DLL ("Proteus VSM Simulator")
BOOK0=HLP\VDMAGDI.HLP ("Proteus VSM AGDI Driver")

【3】 Save and exit , restart keiMDK, Click on uVision4->Project->Options for xxxx, eject Options for xxxx Dialog box , Click on Debug page , Click the drop-down button to see “Proteus VSM Simulator”, Here's the picture

 【4】 Click on “Settings” Button , You can set the location of the simulation host IP Address and port, etc , Here's the picture

 

【5】 Check ISIS Professional->Debug->Use Romote Debug Monitor, You can simulate it . Here's the picture

 

【6】 The simulation test

perform uVission4->Project->Open Project ...-> C:\Keil\ARM\Examples\Hello.uvproj, open hello engineering , On the left side Project In the column LPC2100 Right click on the project directory ->Options fro Target 'LPC2100'.., Here's the picture

 

 

  Click in the pop-up dialog box device label , Here's the picture , Choose LPC2138

Then click Debug label , Check on the right Use Radio button , And select “Proteus VSM Simulator”, Here's the picture

 

And then click "OK" Button , End setting . Then compile .

open ISIS Professional->File->Open Design.., Open the dialog box as shown in the following figure , And locate LPC2138 with Graphics LCD, Then confirm that you have checked Debug->Use Remote Debug Monitor.

 

 

perform uVision4->Debug->Start/Stop Debug Session, At this time, the project is in debug state , Corresponding , stay ISIS Professional See also in Debug State of the project .