Hello together,
I have several question about CW_HC12_v5.1:
1, For the MCU MM912H634, I can only use CW_HC12_v5.1? How about the latest IDE CW10.6, it supports the MM912H634?
2, I used the CW_HC12_v5.1_SPECIAL at this moment, how can I get the full version ?
3, When I simulate my program with CodeWorrior True-Time Simullator hiwave.exe, result is different with full Start/Continue(F5) mode and Step over(F10) mode, why?
With Step over(F10) mode, some MCU rigisters and some variants I changed the value in my code have no any change in CodeWorrior True-Time Simullator's detect windows, why? As below:
Finally, I feel CW_HC12_v5.1 is too old to keep pace with the IDE software development, When will Freescale upgrade the CW_HC12_v5.1?
Thanks!
Best Regards
David Dai
Hi,
regarding to your questions:
1. you are correct MM912H634 is only supported by CW_HC12_v5.1. CW10.6 doesn't support MM912H634. as I know there is no plan for CW10.x supporting HCS12 in the near future release.
if you want, you can propose your requirement as a feature request to support@freescale.com. Freescale support could escalate it.
2. the long term full version is not free. here is the link to order full version
CodeWarrior Suites (Bas, Stand, Pro)|Freescale
3. regarding to the left side picture, i wonder you debug the project in full simulation mode without connecting board. in full simulation mode, not all hardware register can work normal. you need connect a board to make sure register view perform full function work.
regarding to the right side picture, i wonder it is an optimization problem, please cast the related local variable with volatile:
volatile int i=0;
this should fix the problem.
4. CW5.1 is in maintenance mode, Freescale still develops patch for bug fix. here is the document for
How to download a Service Pack / Patch / Update?
can this help you?
Have a great day,
Zhang Jun
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Jennie,
Thanks a lot for your answer!
For the question 3,
Actually, I did connect board, I can drive my motor normally.
How to understand "make sure register view perform full function work"?
For the local variable, also I already cast with volatile, as below.
I else can't detect the real-time change at Stepped Over mode.
Thanks!
Best Regards
David Dai
Hi
to avoid optimization, volatile is used for local variable.
for global variable, adding the variable name in prm file ENTRIES section can avoid being optimized. for example:
ENTRIES /* keep the following unreferenced variables */
variable_name1 variable_name2
END
can this help you?
Have a great day,
Zhang Jun
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------