This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
manual:demos:evbplus_dragon12p_codewarrior [2014/07/24 17:31] voorburg |
manual:demos:evbplus_dragon12p_codewarrior [2019/06/29 17:44] voorburg |
||
---|---|---|---|
Line 13: | Line 13: | ||
To program the bootloader into the internal flash on the HCS12DG256 microcontroller, the [[http://www.pemicro.com/products/product_viewDetails.cfm?product_id=33| P&E Micro USB BDM Multilink]] interface was used. However, this is not required if you have another means of programming the internal flash. | To program the bootloader into the internal flash on the HCS12DG256 microcontroller, the [[http://www.pemicro.com/products/product_viewDetails.cfm?product_id=33| P&E Micro USB BDM Multilink]] interface was used. However, this is not required if you have another means of programming the internal flash. | ||
- | To compile the demo programs you can use the [[http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW-SUITE-SPECIAL&tid=CWH|Freescale Codewarrior for HCS12(X)]] development environment. | + | To compile the demo programs you can use the [[https://www.nxp.com/support/developer-resources/software-development-tools/codewarrior-development-tools/codewarrior-legacy/codewarrior-development-suite-special:CW-SUITE-SPECIAL|Codewarrior Development Studio for HCS12(X)]] development environment. |
===== Building and programming the Bootloader ===== | ===== Building and programming the Bootloader ===== | ||
+ | |||
Before the bootloader can be used, it needs to be built and programmed into the HCS12DG256's internal flash memory. The steps in this section only need to be done once. | Before the bootloader can be used, it needs to be built and programmed into the HCS12DG256's internal flash memory. The steps in this section only need to be done once. | ||
Line 28: | Line 29: | ||
===== Building the Demo Program ===== | ===== Building the Demo Program ===== | ||
+ | |||
When using Freescale Codewarrior, simply open the project from within Codewarrior and select //Project->Make// from the menu. The project file is located at: \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\ide\ | When using Freescale Codewarrior, simply open the project from within Codewarrior and select //Project->Make// from the menu. The project file is located at: \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\ide\ | ||
The output file is | The output file is | ||
+ | |||
* \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\bin\**demoprog_evbplus_dragon12p.abs.sx** | * \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\bin\**demoprog_evbplus_dragon12p.abs.sx** | ||
===== Firmware update procedure ===== | ===== Firmware update procedure ===== | ||
+ | |||
To download the demo program \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\bin\**demoprog_evbplus_dragon12p.abs.sx** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: | To download the demo program \Target\Demo\HCS12_Evbplus_Dragon12p_CodeWarrior\**Prog**\bin\**demoprog_evbplus_dragon12p.abs.sx** using the bootloader, follow the instructions in the following links, depending on the communication interface you intend to use: | ||
Line 41: | Line 45: | ||
===== Resolving Build Errors ===== | ===== Resolving Build Errors ===== | ||
+ | |||
When building the demo binaries for the first time, build errors might occur caused by CodeWarrior projects not correctly dealing with relative directories and having source-files in a project that have the same name as source-files in the library path. These errors are quickly resolved by removing the file from the project and adding them again. | When building the demo binaries for the first time, build errors might occur caused by CodeWarrior projects not correctly dealing with relative directories and having source-files in a project that have the same name as source-files in the library path. These errors are quickly resolved by removing the file from the project and adding them again. | ||