Install the embedded microcontroller development environment Keil5MDK and integrate the C51 development environment
1 Overview
This article introduces the embedded development tools produced by Keil, mainly introducing two commonly used products
- KeilMDK is mainly used in the development and debugging of ARM chip programs;
- C51 is mainly used for 51 microcontroller program development;
After installing the two tools, integrate the two tools together to achieve seamless switching between ARM chip and 51 microcontroller chip program development in the MDK tool without opening the two tools.
2. Download development tools
Before installing the tool, you first need to download it from the Keil official website or obtain it from the network disk.
2.1. Obtain address from network disk
Link: https://pan.baidu.com/s/1cOoWp27g-S_XPQjPm4Hg_A
Extraction code: keil
2.2.Download from Keil official website
Keil official website: https://www.keil.com/
1. Log in to the official website.
Log in to the official website Downloads
and click Download to jump to the download page.
2. Download MDK-Arm and C51 respectively
, fill in the relevant information, and click Submit
the button to download.
3. MDK tool installation
3.1.MDK installation
1. Open the MDK installation package, follow the default information for everything, click Next, and use the default installation directory. Continue to the next C:\Keil
step
. 2. Fill in the information. Next step
. 3. Keep going to the next step until you are prompted whether to install a serial device. Select 确定
.
3. Until the installation is completed.
3.2.MDK registration
- Right click -
管理员身份
open MDK tool - Click
File
to selectlicense Management
- Copy
CID
number
- Open the registration machine provided by Netdisk
- Paste the copied
CID
number into the CID location - Target selection
ARM
- Click
Generate
- Generated by copy
序列号
- Open the MDK tool, paste the CID serial number, stand-alone
AddLIC
, and it will prompt that the registration is completed successfully.
- Modify
TOOLS.INI
the file name. Modify the file name
in to any other name at will, for example, change itC:\Keil
toTOOLS.INI
STOOLS.INI
Why do you need to modify
TOOLS.INI
the file name?
Because installing the C51 tool below will also generate a file with this name. The name will also cause conflicts, so change it to another name first, and then change the file name when integrating the two tools. Change it back.
4.C51 tool installation
4.1.C51 installation
1. Open the C51 installation package and follow the default information. Click Next. Use the default installation directory C:\Keil
to continue to the next step.
Important: The installation directory must be consistent with the MDK directory, for example, both are installed C:\Keil
in the folder.
2. Fill in the information and next step
3. Installation completed
4.2. Integrate MDK and C51 tools
- 1. Open the
C:\Keil
MediumSTOOLS.INI
file and check[c51]
whether the content starting with " exists". If it exists, skip the following步骤2
. The path shown
STOOLS.INI
in the file may not be the path we installed , just change it to .[c51]
PATH
C:\Keil
C:\Keil
[C51]
//原版C51路径
PATH="C:\Keil_v5\C51\"
VERSION=V9.61
//修改后的C51路径
PATH="C:\Keil\C51\"
VERSION=V9.61
For example, the following is STOOLS.INI
the complete content of the file, including [c51]
the beginning.
[UV2]
ORGANIZATION="abd"
NAME="Administrator", "abd"
EMAIL="[email protected]"
ARMSEL=1
BOOK0=UV4\RELEASE_NOTES.HTM("uVision Release Notes",GEN)
[ARM]
PATH="C:\Keil\ARM\"
VERSION=4.60
PATH1="C:\Program Files\arm-none-eabi-gcc-4_6\"
TOOLPREFIX=arm-none-eabi-
CPUDLL0=SARM.DLL(TDRV0,TDRV5,TDRV6,TDRV10) # Drivers for ARM7/9 devices
CPUDLL1=SARMCM3.DLL(TDRV1,TDRV2,TDRV3,TDRV4,TDRV5,TDRV7,TDRV8,TDRV9,TDRV11,TDRV12,TDRV13,TDRV14) # 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=CMSIS\index.html("CMSIS Documentation",GEN)
BOOK3=Signum\Docs\SigUV3Arm.htm("Signum Systems JTAGjet Driver Documentation",GEN)
TDRV0=BIN\UL2ARM.DLL("ULINK2/ME ARM Debugger")
TDRV1=BIN\UL2CM3.DLL("ULINK2/ME 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 ARM")
TDRV7=Segger\JL2CM3.dll("J-LINK / J-TRACE Cortex")
TDRV8=STLink\ST-LINKIII-KEIL.dll ("ST-Link (Deprecated Version)")
TDRV9=BIN\ULP2CM3.DLL("ULINK Pro Cortex Debugger")
TDRV10=BIN\ULP2ARM.DLL("ULINK Pro ARM Debugger")
TDRV11=NULink\Nu_Link.dll("NULink Debugger")
TDRV12=SiLabs\SLAB_CM_Keil.dll("SiLabs UDA Debugger")
TDRV13=STLink\ST-LINKIII-KEIL_SWO.dll ("ST-Link Debugger")
TDRV14=BIN\CMSIS_AGDI.dll("CMSIS-DAP Debugger")
DELDRVPKG0=ULINK\UninstallULINK.exe("ULINK Pro Driver V1.0")
LIC0=TIVNB-2HEP3-FW92N-YSNH9-DYAS4-89VS1
[ARMADS]
PATH="C:\Keil\ARM\"
PATH1=".\ARMCC\bin\"
CPUDLL0=SARM.DLL(TDRV0,TDRV5,TDRV6,TDRV10) # Drivers for ARM7/9 devices
CPUDLL1=SARMCM3.DLL(TDRV1,TDRV2,TDRV3,TDRV4,TDRV5,TDRV7,TDRV8,TDRV9,TDRV11,TDRV12,TDRV13,TDRV14) # 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=CMSIS\index.html("CMSIS Documentation",GEN)
BOOK3=Signum\Docs\SigUV3Arm.htm("Signum Systems JTAGjet Driver Documentation",GEN)
TDRV0=BIN\UL2ARM.DLL("ULINK2/ME ARM Debugger")
TDRV1=BIN\UL2CM3.DLL("ULINK2/ME 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 ARM")
TDRV7=Segger\JL2CM3.dll("J-LINK / J-Trace Cortex")
TDRV8=STLink\ST-LINKIII-KEIL.dll ("ST-Link (Deprecated Version)")
TDRV9=BIN\ULP2CM3.DLL("ULINK Pro Cortex Debugger")
TDRV10=BIN\ULP2ARM.DLL("ULINK Pro ARM Debugger")
TDRV11=NULink\Nu_Link.dll("NULink Debugger")
TDRV12=SiLabs\SLAB_CM_Keil.dll("SiLabs UDA Debugger")
TDRV13=STLink\ST-LINKIII-KEIL_SWO.dll ("ST-Link Debugger")
TDRV14=BIN\CMSIS_AGDI.dll("CMSIS-DAP Debugger")
RTOS0=Dummy.DLL("Dummy")
RTOS1=VARTXARM.DLL ("RTX Kernel")
DELDRVPKG0=ULINK\UninstallULINK.exe("ULINK Pro Driver V1.0")
[C51]
PATH="C:\Keil\C51\"
VERSION=V9.61
BOOK0=HLP\Release_Notes.htm("Release Notes",GEN)
BOOK1=HLP\C51TOOLS.chm("Complete User's Guide Selection",C)
TDRV0=BIN\MON51.DLL ("Keil Monitor-51 Driver")
TDRV1=BIN\ISD51.DLL ("Keil ISD51 In-System Debugger")
TDRV2=BIN\MON390.DLL ("MON390: Dallas Contiguous Mode")
TDRV3=BIN\LPC2EMP.DLL ("LPC900 EPM Emulator/Programmer")
TDRV4=BIN\UL2UPSD.DLL ("ST-uPSD ULINK Driver")
TDRV5=BIN\UL2XC800.DLL ("Infineon XC800 ULINK Driver")
TDRV6=BIN\MONADI.DLL ("ADI Monitor Driver")
TDRV7=BIN\DAS2XC800.DLL ("Infineon DAS Client for XC800")
TDRV8=BIN\UL2LPC9.DLL ("NXP LPC95x ULINK Driver")
TDRV9=BIN\JLinkEFM8.dll ("J-Link / J-Trace EFM8 Driver")
TDRV10=BIN\JLinkIS2083.dll ("J-Link / J-Trace IS2083 Driver")
TDRV11=BIN\Nuvoton_8051_Keil_uVision_Driver.dll ("Nuvoton 8051 Keil Driver")
RTOS0=Dummy.DLL("Dummy")
RTOS1=RTXTINY.DLL ("RTX-51 Tiny")
RTOS2=RTX51.DLL ("RTX-51 Full")
LIC0=32KYW-Q6IYR-A1LP3-AA3U5-3QT6J-FC060
If 步骤1
there is no [c51]
content at the beginning of , then execute the following 步骤2
. The purpose is to put MDK
the content and C51
content in a TOOLS.INI
file.
- 2. After the C51 is installed,
C:\Keil
a newTOOLS.INI
file will be generated in the directory. Open the file and[c51]
copy the entire content from beginning to end.STOOLS.INI
Paste at the end of the file content
[C51]
PATH="C:\Keil\C51"
VERSION=V9.61
BOOK0=HLP\Release_Notes.htm("Release Notes")
BOOK1=HLP\C51TOOLS.chm("Complete User's Guide Selection", C)
TDRV0=BIN\MON51.DLL ("Keil Monitor-51 Driver")
TDRV1=BIN\ISD51.DLL ("Keil ISD51 In-System Debugger")
TDRV2=BIN\MON390.DLL ("MON390: Dallas Contiguous Mode")
TDRV3=BIN\LPC2EMP.DLL ("LPC900 EPM Emulator/Programmer")
TDRV4=BIN\UL2UPSD.DLL ("ST-uPSD ULINK Driver")
TDRV5=BIN\UL2XC800.DLL ("Infineon XC800 ULINK Driver")
TDRV6=BIN\MONADI.DLL ("ADI Monitor Driver")
TDRV7=BIN\DAS2XC800.DLL ("Infineon DAS Client for XC800")
TDRV8=BIN\UL2LPC9.DLL ("NXP LPC95x ULINK Driver")
TDRV9=BIN\JLinkEFM8.dll ("J-Link / J-Trace EFM8 Driver")
TDRV10=BIN\JLinkIS2083.dll ("J-Link / J-Trace IS2083 Driver")
TDRV11=BIN\Nuvoton_8051_Keil_uVision_Driver.dll ("Nuvoton 8051 Keil Driver")
RTOS0=Dummy.DLL("Dummy")
RTOS1=RTXTINY.DLL ("RTX-51 Tiny")
RTOS2=RTX51.DLL ("RTX-51 Full")
- 3.
C:\Keil
DeleteTOOLS.INI
the file in the directory andSTOOLS.INI
change the file name toTOOLS.INI
4.3.C51 registration
- Right click -
管理员身份
open MDK tool - Click
File
to selectlicense Management
- Copy
CID
number
- Open the registration machine provided by Netdisk
- Paste the copied
CID
number into the CID location - Target selection
C51
- Click
Generate
- Generated by copy
序列号
5. Open the MDK tool, paste the CID serial number, stand-alone AddLIC
, and it will prompt that the registration is completed successfully.
5. Summary
Keil5MDK and integrating C51 are very simple. There are two key steps.
- MDK and C51 are two tools and both need to be installed.
- MDK and C51 tools are integrated, and only configuration information needs to be added to the MDK
TOOLS.INI
file.C51
The next article will introduce how to create a project in MDK C51
, compile and download it, and burn it to the microcontroller.