readme.txt

来自「CodeWarrior for HCS12 V4.7」· 文本 代码 · 共 53 行

MC9S12DP256 using SDI:
---------------------------

IMPORTANT NOTE: To use the simulator/debugger, you have to enable it first using
                Project->Enable Debugger

This Project is set up to run the MC9S12DP256 with 
the SDI Interface using the corresponding Motorola EVB board.

Three different targets are available, using three different 
Linker Parameter Files (.PRM), with the same source file fibodp256.c.

1- SDI Debug (RAM)
Using this project, the generated application fiboramdp256.abs is
located in RAM. 
When debugging, the application is automatically loaded.

Note: for this target the Compiler option -ol0 has been set up
to disable some compiler optimizations in order to be able to see 
all the local variables in the debugger Data component.

2- SDI Flat (FLASH)
Using this project, the generated application fiboflatddp256.abs 
is NOT banked but is located in the Internal Flash memory of 
the MC9S12DP256.
 
When debugging, the application is NOT automatically loaded.
Once the True Time Debugger is started and the connection to the 
target board is established, please select the SDI | Flash 
menu entry in order to load the application in ".\bin\fiboflatdp256.abs"

Note: for this target, all the local variables in the debugger 
Data component are not visible due to Compiler optimizations.
To disable this compiler optimization in order to be able to see 
all the local variables in the debugger Data component, please add -ol0.

3- SDI Banked (FLASH)
Using this project, the generated application fibobankeddp256.abs 
is banked and is located in the Internal Flash memory of 
the MC9S12DP256.
 
When debugging, the application is NOT automatically loaded.
Once the True Time Debugger is started and the connection to the 
target board is established, please select the SDI | Flash 
menu entry in order to load the application in ".\bin\fibobankeddp256.abs"

Note: for this target, all the local variables in the debugger 
Data component are not visible due to Compiler optimizations.
To disable this compiler optimization in order to be able to see 
all the local variables in the debugger Data component, please add -ol0.