Reply by Andrew Lohmann's New Email Server August 11, 20042004-08-11
Hi The strategy I am using to move from HD6301 (improvement on MC6801) to MC9S12E128 did have some hitches but is worth considering:

I chose Cosmic C and Zap using P&E Multilink12, it is one of the best CAD tools I have used but here were some issues - the documentation is a bit difficult. The compiler is generally recommend to be the best, but consider using CodeWrite instead of IDEA.

BDM is generally very reliable but watch out for some limitations see:
http://www.softecmicro.com/support.html?typeail&title=inDART-HCS12%2FD#FAQ20

Also see:- section 1.3.3 Low-Power Modes
http://www.freescale.com/files/microcontrollers/doc/ref_manual/S12BDMV4.pdf

I found that BDM will only tolerate short periods of waiting in "wai", when
CRG CLKSEL bits for: PSTP SYSWAI PLLWAI CWAI RTIWAI COPWAI, are not set.

Both the USB and the Parallel Multilink12 (with patch) run equally well with XP Pro. NT4 is slightly more stable (if you do chose to use the wai mode).

To summarise:
COP Watchdog Reset & External Reset, STOP and WAIT Power-Down Modes,
Self-Clock Mode can only be supported using a full HCS12 emulator, and
cannot be supported by BDM at all. But there should be no difficulty in working around these limitations and use BDM.

1) NT4 is better behaved than XP Pro.
2) "wai" Instruction throws the BDM, and may be the primary cause of "can't abort target".
3) Mouse behaves erratically in XP Pro if compiled code with segments inadvertently overlapping, and/or segment address beyond the programme
counter range. (Don't use the Cosmic linker examples without correcting this)

Having taken care with the Colpits oscillator I found the BDM to be very reliable, but that is something you must not compromise.

Start with a new project using AN2485 software, you will have to through out some Metrowerks stuff. It is a sound set of headers for a range of HCS12 derivatives. then add your code from your older HC11 project. Andrew Lohmann AIIE
Design Engineer

PLEASE NOTE NEW EMAIL ADDRESS IS: Bellingham + Stanley Ltd.
Longfield Road, Tunbridge Wells, Kent, TN2 3EY, England.
Tel: +44 (0) 1892 500400
Fax: +44 (0) 1892 543115
Website: www.bs-ltd.com

----- Original Message -----
From:
To:
Sent: Wednesday, August 11, 2004 12:20 PM
Subject: Re: [68HC12] HC11 to HC12 We use the IAR compiler - works fine. We don't use their debugger
because you cant debug in RAM with it. With any debugger these days avoid
using the parallel port with Windows XP.

Rod Niner


Reply by August 11, 20042004-08-11
We use the IAR compiler - works fine. We don't use their debugger
because you cant debug in RAM with it. With any debugger these days avoid
using the parallel port with Windows XP.

Rod Niner
GSE Scales
42860 Nine Mile Road
Novi, MI 48375-4122
ph: 248.596.3350 The information contained in this electronic mail transmission is intended
by SPX Corporation for the use of the named individual or entity to which
it is directed and may contain information that is confidential or
privileged. If you have received this electronic mail transmission in
error, please delete it from your system without copying or forwarding it,
and notify the sender of the error by reply email so that the sender's
address records can be corrected.

08/10/2004 12:42 PM
Please respond to
To

cc

Subject
Re: [68HC12] HC11 to HC12
In a message dated 8/10/04 12:15:58 PM Eastern Daylight Time,
writes:

Hello Group:

Can anyone share the experiences they had
taking an HC11(E1) design to an HC12S(E128)?

What are the "look out fors"?

Is it as simple as Mot would have you believe?

I have IAR tools that I use for the 11 and want to
Use their tools for the 12.

Patrick Nefos

Did the hc11 use external ram and rom? That's tricky on the hc12....
Yahoo! Groups Links


Reply by August 11, 20042004-08-11
I think initial setup will be your biggest task. Also I remember the
serial port is more capable. SPI had promising improvements but what out
for errata. Also you I assume you will want a boot loader as an
improvement. Also had problems with stacking instructions when writing to
flash: there is an errata on that as well. If you want to emulate with
more than two breakpoints then running out of RAM needs to be considered.
We use an Axiom board with an adapter that takes I/O from the Axiom board
onto our embedded board. We don't stuff the connector on our embedded
board in production and for development stuff it and remove our processor. Rod Niner
GSE Scales
42860 Nine Mile Road
Novi, MI 48375-4122
ph: 248.596.3350 The information contained in this electronic mail transmission is intended
by SPX Corporation for the use of the named individual or entity to which
it is directed and may contain information that is confidential or
privileged. If you have received this electronic mail transmission in
error, please delete it from your system without copying or forwarding it,
and notify the sender of the error by reply email so that the sender's
address records can be corrected.

08/10/2004 12:13 PM
Please respond to
To

cc

Subject
[68HC12] HC11 to HC12
Hello Group:

Can anyone share the experiences they had
taking an HC11(E1) design to an HC12S(E128)?

What are the "look out fors"?

Is it as simple as Mot would have you believe?

I have IAR tools that I use for the 11 and want to
Use their tools for the 12.

Patrick Nefos

. Yahoo! Groups Links


Reply by Doron Fael August 10, 20042004-08-10
Hello Patrick,

The HC12 and HCS12 are pretty compatible with the older HC11 in the
following sense:

1. All the HC11 instructions, are legal on the HC12 and HCS12. The opcodes
are however different, so it is necessary to recompile the HC11 code using
an HC12/HCS12 assembler, before you can run it on the HC12.
2. The peripherals (SCI, SPI, TIMER etc) are also pretty compatible,
although some new features have been added here and there so the
peripherals are not 100% compatible, but they resemble much of the HC11
peripherals, so it is usually not too time-consuming to change existing
HC11 peripherals code to HC12 code.

The new MC9S12E128 is different from the HC11 in the following main points:
1. The HCS12 External bus is not user friendly - so don't plan on using the
external bus. The HCS12 is fine as long as you operate it in Single-Chip mode.
2. Speed - the HCS12 can run to 25MHz bus speed, much faster than the HC11
could.
3. The HCS12 architecture is 16 bits, so many instructions take less
bus-cycles to execute and new 16 bit instructions are added to farther
increase the performance.
4. The pinout is different.
5. More internal memory is available (Flash, Ram etc.)
6. 5V as well as 3.3V operation is possible on the MC9S12E128.
7. There is a new paging scheme to allow code greater than 64K to be
executed in a strait forward manner using the CALL and RTC instructions,
that did not exist on HC11.

The following document is also helpfull, if you didn't read it already.
http://www.freescale.com/files/microcontrollers/doc/app_note/AN1284.pdf

Hope this helps,
Doron
Nohau Corporation
HC12 In-Circuit Emulators
www.nohau.com/emul12pc.html

At 12:13 10/08/2004 -0400, you wrote:
>Hello Group:
>
>Can anyone share the experiences they had
>taking an HC11(E1) design to an HC12S(E128)?
>
>What are the "look out fors"?
>
>Is it as simple as Mot would have you believe?
>
>I have IAR tools that I use for the 11 and want to
>Use their tools for the 12.
>
>Patrick Nefos




Reply by August 10, 20042004-08-10
In a message dated 8/10/04 12:15:58 PM Eastern Daylight Time,
writes:

Hello Group:

Can anyone share the experiences they had
taking an HC11(E1) design to an HC12S(E128)?

What are the "look out fors"?

Is it as simple as Mot would have you believe?

I have IAR tools that I use for the 11 and want to
Use their tools for the 12.

Patrick Nefos

Did the hc11 use external ram and rom? That's tricky on the hc12....



Reply by August 10, 20042004-08-10
Hello Group:

Can anyone share the experiences they had
taking an HC11(E1) design to an HC12S(E128)?

What are the "look out fors"?

Is it as simple as Mot would have you believe?

I have IAR tools that I use for the 11 and want to
Use their tools for the 12.

Patrick Nefos

.