So far I've found no way to run my S12ZVM-Controller stand alone without Codewarrior. The Code is created with Processor Expert. I want the Controller to be flashed Properly and to work without performing a new Programming process with Code Warrior.
After a Reset it is possible to communication via UART with the Controller which means that the Programm is Running. However the GDU is not working and the Motor is not actuated. When I program the Controller with the Multilink in Codewarrior (Run: Ctrl F11) the Program is initialised properly and the GDU starts. Is there any Configuration within Codewarrior or of the BCD-Interface to make my Application true stand alone?
Hello Daniel,
thank you for your reply
in the attach session (Pic 2) some of the Register Values are different than in Run-Mode (Pic 1).
For instance the bit GLVLSF in the GDUG-Register is set which means that
all high-side and low-side pre-drivers are turned off.
So possibly there is a low Voltage condition on the VLS-OUT Pin detected
during Power-ON (because the Capacitor could be not charged yet or something
like that). However with a Multimeter a Voltage of ~11Volts can be measured on the
Pin in Both conditions (proper operation and improper operation).
What would be the best way to escape this condition?
Can I perform a Software-Reset somehow?
Pic 1. Proper Operation (Run via CW)
Pic 2. Insufficient Operation (Stand alone)
Kind Regards,
Christian
Hi,
Please have a look at the GDUF register description. There is a note for GLVLSF and GLVLSIF: Out of power on reset the flags may be set. You can wait in a while loop, clearing this flags, until the low voltage condition is gone.
while (GDUF_GLVLSF) {
GDUF_GLVLSF = 1;
GDUF_GLVLSIF = 1;
}
Regards,
Daniel
Thanks, this is working.
I think a Software Reset would also resolve the Problem: After a Hardware-Reset
(Shorting the RESET-Pin to GND) the System is also initialised correctly.
Nevertheless I have used the method recommended.
Kind regards
Christian
Hi,
While it is running alone, you can try to connect the debugger back to the MCU in attach session.
And then check registers for fault flags etc.
Regards,
Daniel