S12 / MagniV Microcontrollers中的主题 Re: MM912G634DV1AE Programming

MM912G634DV1AE Programming

adelantesey — Sun, 23 Jun 2013 10:33:12 GMT

I have problem for programming with MM912G634DV1AE , my programmer is MULTILINK UNIVERSAL I have error with subject about can not write in 0xFFF8!

what is your suggestion ?

Re: MM912G634DV1AE Programming

RadekS — Mon, 24 Jun 2013 15:06:27 GMT

I suppose that there will some issue with interrupt vectors.

Please check your code if you have interrupt vectors defined twice.

Node: don’t forget vector definition(s) in prm file.

Re: MM912G634DV1AE Programming

adelantesey — Tue, 25 Jun 2013 04:12:24 GMT

thanks for your response ,

do you have any sample code? I think my Code has a problem but I do not have sample code.

Re: MM912G634DV1AE Programming

RadekS — Tue, 25 Jun 2013 08:35:56 GMT

I attached contents of CD for KIT912H634 evaluation board and user manual.

Re: MM912G634DV1AE Programming

adelantesey — Tue, 25 Jun 2013 11:13:59 GMT

thank you so much, I'll check and come back.

Re: MM912G634DV1AE Programming

adelantesey — Tue, 25 Jun 2013 11:55:14 GMT

Mr.Radek Sestak

I test with your software and I have this problem again,

Error is : " Error while writing to FFFE..101FE"

what is your suggestion ?

Re: MM912G634DV1AE Programming

RadekS — Tue, 25 Jun 2013 14:33:25 GMT

Strange, everything works correctly on my side.

Please check if you have at least 8V at TCK pin (44). This disable internal watchdog – it is necessary during loading software and debugging.

Are you sure that you have MM912G634 and not MM912F634?

Could you please try connecting to MCU and check Part ID (addresses 0x001A and 0x001B)? There should be 0x38C0 in case of MM912G634 or MM912H634. In case of MM912F634 it should be 0x3800 or 0x3801.

Please check if you already install CodeWarrior for HCS12(X) v5.1 MM912H634 Service Pack:

http://www.freescale.com/webapp/sps/site/overview.jsp?code=CW_UPDATES_HCS12_51

Example codes which I posted above contain small error. There is wrong unsecure command file (old version - it fits to MM912F634). However this should not have any connection to your issue. In attachment you can find correct cmd file for MM912G634 and MM912H634 devices.

If you use KIT912H634 evaluation board, please disconnect JP14 and JP15 jumpers (this disconnect TBDML interface).

If you use KIT912H634 evaluation board, please connect JP6 and set JP7 jumper to position 1-2 (this disable internal watchdog.

Re: MM912G634DV1AE Programming

adelantesey — Wed, 26 Jun 2013 04:17:00 GMT

thank you so much for your following,

I have MM912H634 and MM912F634 together ,i could not program into both of them.

about part ID i checked and for 912H is 0xID3 for 912G is 0x1E1 and 912F is 0x1D4.of course this numbers write in our code warier .

some question :

1- can I write software with MM912G and program on the MM912F or H

2- this problem is for software or hardware

3- your attachment was incorrect please sent me again or sent me simple sample because only i want make sure that this problem is for soft ware or hardware

thanks a lot

Re: MM912G634DV1AE Programming

adelantesey — Wed, 26 Jun 2013 12:33:12 GMT

My TCK pin contact to GND ,I checked again and our error is fixed !!??enclosed you can find my schematic, what is your advise?

Re: MM912G634DV1AE Programming

RadekS — Wed, 26 Jun 2013 14:40:08 GMT

The problem is: If voltage at TCLK pins is bellow 7V, window watchdog at analog die will be active and Initial Non-window Watchdog Timeout is just 150ms (110…190ms). So, you have to program MCU in shorter time than 110ms (after reset) or you have to make some hardware changes for programming.

Recommendation:

Disassemble R15. MM912G634 supports only Loop Controlled Pierce Oscillator Connection (see Figure 83. OSCLCP Block Diagram).
Disable window watchdog or disconnect reset signal.
1. Disable window watchdog – disconnect TCLK pin from GND and connect TCLK pin to GND by pull-down resistor. During programming just connect at least 8V to TCLK pin.
2. Disconnect reset signal – window watchdog is located on analog die, if you disconnect RESET_A and RESET pins, analog die will not cause MCU reset. RESET signal must stay connected to BDM interface.

Note: There is third option, connect just +5V to VDDX for powering MCU, however we strictly not recommend this solution.

Re: MM912G634DV1AE Programming

adelantesey — Sat, 29 Jun 2013 03:47:37 GMT

thanks a lot for your information,

yesterday I can program of course my problem was RESET_A .

Now RESET_A pin always should be disconnect to GND or contact to GND with separate capacitor ?

Re: MM912G634DV1AE Programming

adelantesey — Mon, 01 Jul 2013 14:06:30 GMT

could you help with sample code ?I could not toggle pins of PORTA and PORTB in output ?why? hse a special note?D2DI has a note?

thanks,

Re: MM912G634DV1AE Programming

RadekS — Mon, 01 Jul 2013 16:06:48 GMT

MM912F634 is incompatible with MM912G634 and MM912H634.

MM912F634 has older MCU core built on 250nm.

MM912H (G) 634 has newer MCU core built on 180nm (different clock module, flash,…).

Difference between MM912H634 and MM912G634 is only in flash size.

Re: MM912G634DV1AE Programming

RadekS — Mon, 01 Jul 2013 16:11:54 GMT

RESET_A pin has to be connected to RESET pin.

I would like to recommend disconnect RESET_A and RESET pins only for programming (watchdog on analog die will not interrupt MCU) - as workaround in production.

For debugging purpose is better connecting at least 8V to TCLK pin. This will disable window watchdog and you can fully use both dies.

If you connect at least 8V to TCLK pin, RESET_A pin could be connected to RESET pin all the time.

Re: MM912G634DV1AE Programming

adelantesey — Tue, 02 Jul 2013 03:59:19 GMT

1- for mass production RESET_A pin has to be connected to RESET pin or not?if yes for programming has not problem?

2- I have only MM912F in my hand and I want write software in mm912F after development switch to MM912G is it possible ?

3- Now I have new problem I could not toggle pins of PORTA and PORTB in output ?why? has a special note?run D2DI has a note?

looking forward to your comment .

thanks

Re: MM912G634DV1AE Programming

RadekS — Tue, 02 Jul 2013 12:08:28 GMT

During programming in mass production and debugging – at least 8V has to be connected to TCLK pin. If is it not possible (error on PCB), you can temporary disconnect RESET_A and RESET pins during programming (after that connect back).
Yes, it is possible. You can write software for MM912F634 and after that you can migrate (with some software changes) this code to MM912G634.
There isn’t anything special. Port A is located at MCU therefore you need only set DDR register to output mode. Port B is located at analog die therefore you need initialize D2D interface and set DDR bits to output mode. In attachment you can find simple example code.

Re: MM912G634DV1AE Programming

adelantesey — Tue, 02 Jul 2013 12:34:47 GMT

thank you so much for your help,

Now I disconnected RESET_A to RESET before programming after that contact again to RESET but micro can not run again!!! Micro burst is reset ?why?

1- do you think are there any problem in my schematic ?

2- why my micro burst is reset?

Re: MM912G634DV1AE Programming

RadekS — Tue, 02 Jul 2013 13:10:02 GMT

Your program contains a function for periodically resetting of window watchdog?

If yes, please check if you feed watchdog in proper time interval (second half of timeout period).

If not, please add function for feed watchdog or connect at least 8V to TCLK pin.

Re: MM912G634DV1AE Programming

adelantesey — Sat, 06 Jul 2013 05:44:23 GMT

I contacted at least 8V to TCLK pin and solved my problem,

now i have two question :

1- how can i use interrupt timer?

2- what is interrupt vector for Timer ?

3-do you have source code for init timer ?

4- I can not use Low side driver i'd write

	B_LSCEN	= 0x05;
	B_LSCR	= 0x03;

and for disable B_LSCR = 0;

why I can not use it?it has a special note?Alse I can use High side driver without any problem.

Re: MM912G634DV1AE Programming

RadekS — Mon, 08 Jul 2013 16:26:04 GMT

About 1..3)

Timer is located on analog die therefore you should use D2D interrupt for handling Timer interrupt.

D2D Interface interrupt vector is Vector base + 0x00F2 (interrupt 6).

Yes, in atachment you can find simple example code for MM912H634.

About 4)

Strange, it works correctly on my side. What you have connected to LS pins?