Sign in

Not a member? | Forgot your Password?

Search 68hc12

Search tips

Subscribe to 68hc12

Free PDF Downloads

Advanced Linux Programming

What Every Programmer Should Know About Memory

Introduction to Embedded Systems

C++ Tutorial

Embedded Systems - Theory and Design Methodology

Microcontroller Programming and Interfacing

Introduction to Microcontrollers


More Free PDF Downloads

Discussion Groups

See Also

ElectronicsDSPFPGA

Find us on Facebook





Discussion Groups | 68HC12 | CodeWorrier + Multilink has landed.

Join our technical discussions about Freescale Microcontrollers: M68HC12. For more discussions, visit Freescale's official forums at community.freescale.com

CodeWorrier + Multilink has landed. - Bruce McMillan - Sep 23 2:43:00 2003

Well, it took some 12 months on & off, but I can now say that
CodeWorrier + Multilink is a nice package.

Since I suspect I'm not the only lost soul out there, I thought I
might relate what has happened to get it working. I remain unclear as
to what the predominant problem was (but I'm sure using the PLL
doesn't help) so here's a check list:

> Upgrade to CW 2.0, particularly if working in assembler - there is
now a good range of fixed & relative assembler templates

> reduce the length of the cable between the MultiLink & your target -
I have it at about 5 inches.

> Change parallel port from ECP to standard. XP may not allow this in
the Bios, so it can be done in MS Device Manager - it's not obvious
how to do it so here's a link to explanations for various operatin
systems,
http://my.okidata.com/idocs2.nsf/0/AEB8E5466DB067F785256A96004C69EF?OpenDocument

> life will be easier if your code does not protect the boot block -
at least during code development

> upgrade the firmware of the BDM multilink by going to the
PEmicro.com website (this worked effortlessly).

> tick the "set CLKSW" box in CW under ICD12|Communication

> once CW (actually the Multilink pod) has auto detected comms speed,
uncheck the auto-detect box in CW under ICD12|Set MCU speed

> I got inside the Multilink & cut a leg off an IC as explained in the
FAQ section of the PEmicro site - I suspect this was unnecessary.

> add some extra powersupply bypass caps right at the BDM in port on
your target system (I also added a bypass cap on the BDM line itself)

> Last and most importantly - this will ABSOLUTELY guarantee success -
but a USB Multilink. As soon as the credit card transaction is
accepted, you will find that your parallel port Multi-link will start
to work unfailingly.

[To put this in context, never had any problems interfacing between my
target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
sainthood). I got there with MultiLink in the end because as we are
going to a 3V3 target, I simply had to.]

good luck!
Bruce





Re: CodeWorrier + Multilink has landed. - Doron Fael - Sep 23 4:14:00 2003

Bruce,

It sounds like you have invested a lot of accumulated time to find all the
small configuration details to allow the CodeWorrier + Multilink solution
to work for you.

I don't know if this will be relevant to you, but I am sure it is for other
list members:

There are better BDM debug solutions that work out of the box without
requiring a lot of time to configure the tool to work.

These solutions come from 3rd parties that specialize in making debugging
tools only (not compilers and debugging tools). Among these 3rd parties you
can find Nohau that I work for, as well as Lauterbach, iSystem and Noral.
For around $2000, you can get a very good BDM that will work
out-of-the-box, with no major configurations.

A full-ICE makes the configuration even simpler and supplies higher end
debugging features, but is also more expensive.

Can one justify an investment of $2000 or even higher in order to save a
lot of setup time, debugging time, and time to hunt for the tool bugs? In
my opinion the answer is yes.

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

At 07:43 AM 9/23/2003 +0000, you wrote:
>Well, it took some 12 months on & off, but I can now say that
>CodeWorrier + Multilink is a nice package.
>
>Since I suspect I'm not the only lost soul out there, I thought I
>might relate what has happened to get it working. I remain unclear as
>to what the predominant problem was (but I'm sure using the PLL
>doesn't help) so here's a check list:
>
> > Upgrade to CW 2.0, particularly if working in assembler - there is
>now a good range of fixed & relative assembler templates
>
> > reduce the length of the cable between the MultiLink & your target -
>I have it at about 5 inches.
>
> > Change parallel port from ECP to standard. XP may not allow this in
>the Bios, so it can be done in MS Device Manager - it's not obvious
>how to do it so here's a link to explanations for various operatin
>systems,
>http://my.okidata.com/idocs2.nsf/0/AEB8E5466DB067F785256A96004C69EF?OpenDocument
>
> > life will be easier if your code does not protect the boot block -
>at least during code development
>
> > upgrade the firmware of the BDM multilink by going to the
>PEmicro.com website (this worked effortlessly).
>
> > tick the "set CLKSW" box in CW under ICD12|Communication
>
> > once CW (actually the Multilink pod) has auto detected comms speed,
>uncheck the auto-detect box in CW under ICD12|Set MCU speed
>
> > I got inside the Multilink & cut a leg off an IC as explained in the
>FAQ section of the PEmicro site - I suspect this was unnecessary.
>
> > add some extra powersupply bypass caps right at the BDM in port on
>your target system (I also added a bypass cap on the BDM line itself)
>
> > Last and most importantly - this will ABSOLUTELY guarantee success -
>but a USB Multilink. As soon as the credit card transaction is
>accepted, you will find that your parallel port Multi-link will start
>to work unfailingly.
>
>[To put this in context, never had any problems interfacing between my
>target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
>sainthood). I got there with MultiLink in the end because as we are
>going to a 3V3 target, I simply had to.]
>
>good luck!
>Bruce >
>-------------------- >
>">http://docs.yahoo.com/info/terms/



_____________________________
 Free pdf download: What Every Programmer Should Know About Memory.


Re: CodeWorrier + Multilink has landed. - ra - Sep 23 4:54:00 2003


On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan wrote:

> [To put this in context, never had any problems interfacing between my
> target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
> sainthood).


Hello Bruce

I wonder if you could share any advice about the D-Bug12 solution
(which remains a very attractive one if one cannot afford Doron's 2000$
route!).
I have the Codewarrior successfully communicating with a DP256 as pod,
but when it tries to load the s-records the elf loader bows out with an
error saying it cannot write to address C000-C0090.
The hardware connection seems to be ok, because if I reformat the same
S-Record file with SRecCvrt and upload it manually with a terminal
emulation program, it works fine.

Is there some preload command needed for the Codewarrior to accomplish
this?

Many thanks!
Robert





Re: CodeWorrier + Multilink has landed. - Bruce McMillan - Sep 23 5:44:00 2003

Robert,
I think it's clear that I'm not holding myself out as an expert.
My advice would be that if you are confident that the code will
compile/assemble correctly under CW (it's not clear what you are using
in the manual solution), then it should be as simple as getting a
template for your processor & pod, and substituting your code for the
Main.asm or Main.c.

Falling over at $C000 suggests that your code may protect the top
page. This was one of my tips. In my experience the preload routine
(p&e_preload.cmd in my case) doesn't clear the protection & you have
to do it manually in CW under ICD-12|Unsecure (I don't know what
routine this invokes.)

The template may encompass several pods - select the right one in teh
drop down menu inside the window that shows the file structure - don't
know what it's called.

bruce

--- In , ra <swar@c...> wrote:
>
> On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan wrote:
>
> > [To put this in context, never had any problems interfacing between my
> > target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
> > sainthood). > Hello Bruce
>
> I wonder if you could share any advice about the D-Bug12 solution
> (which remains a very attractive one if one cannot afford Doron's 2000$
> route!).
> I have the Codewarrior successfully communicating with a DP256 as pod,
> but when it tries to load the s-records the elf loader bows out with an
> error saying it cannot write to address C000-C0090.
> The hardware connection seems to be ok, because if I reformat the same
> S-Record file with SRecCvrt and upload it manually with a terminal
> emulation program, it works fine.
>
> Is there some preload command needed for the Codewarrior to accomplish
> this?
>
> Many thanks!
> Robert






_____________________________
 Free pdf download: Advanced Linux Programming.


Re: CodeWorrier + Multilink has landed. - Bruce McMillan - Sep 23 5:58:00 2003

Robert,
re-reading, I'm not sure I answered your question. If the combination
in question is CW + EVB + DBug-12, then I did'nt try that (I used
DBug-12 with MiniIDE terminal program.) I think the shortcut is to ask
the MW people on the list as to whether a Statonary template is
available for the EVB as Pod - in looking just now I couldn't find
one. You had better specify C or assembler source.

I did try D-Bug12 with NoICE but couldn't get it to do paging for some
reason.

tks
Bruce.
--- In , "Bruce McMillan"
<bruce_at_pocket_neurobics@y...> wrote:
> Robert,
> I think it's clear that I'm not holding myself out as an expert.
> My advice would be that if you are confident that the code will
> compile/assemble correctly under CW (it's not clear what you are using
> in the manual solution), then it should be as simple as getting a
> template for your processor & pod, and substituting your code for the
> Main.asm or Main.c.
>
> Falling over at $C000 suggests that your code may protect the top
> page. This was one of my tips. In my experience the preload routine
> (p&e_preload.cmd in my case) doesn't clear the protection & you have
> to do it manually in CW under ICD-12|Unsecure (I don't know what
> routine this invokes.)
>
> The template may encompass several pods - select the right one in teh
> drop down menu inside the window that shows the file structure - don't
> know what it's called.
>
> bruce
>
> --- In , ra <swar@c...> wrote:
> >
> > On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan
wrote:
> >
> > > [To put this in context, never had any problems interfacing
between my
> > > target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
> > > sainthood).
> >
> >
> > Hello Bruce
> >
> > I wonder if you could share any advice about the D-Bug12 solution
> > (which remains a very attractive one if one cannot afford Doron's
2000$
> > route!).
> > I have the Codewarrior successfully communicating with a DP256 as
pod,
> > but when it tries to load the s-records the elf loader bows out
with an
> > error saying it cannot write to address C000-C0090.
> > The hardware connection seems to be ok, because if I reformat the
same
> > S-Record file with SRecCvrt and upload it manually with a terminal
> > emulation program, it works fine.
> >
> > Is there some preload command needed for the Codewarrior to
accomplish
> > this?
> >
> > Many thanks!
> > Robert







Re: CodeWorrier + Multilink has landed. - Gilles Blanquin - Sep 23 7:23:00 2003


Hi Bruce, Hi Robert.

The D-Bug12 interface in CodeWarrior for the HC12 v2.0 has never been
updated to support D-Bug12 monitors newer than v2.0.2 . This monitor was
delivered with HC912B32 derivatives on M68HC12B32EVB boards.

You might find stationery template only for HC812A4 and HC912B32 devices in:
-"(CodeWarrior_Examples)\HC12\D-Bug12 Target Interface" in "CodeWarrior for
the HC12 v2.0"
- "Examples\HC12\D-Bug12 Target Interface" in "CodeWarrior / MOT V1.2 for
HC12".

However, the new CodeWarrior for HC12 V3.0 just released and available from
Metrowerks web site provides a target interface to debug with the new
Serial Monitor for HCS12 devices (AN here below).

http://e-www.motorola.com/files/microcontrollers/doc/app_note/AN2548.pdf

Regards,
Gilles
At 12:58 PM 9/23/2003, you wrote:
>Robert,
>re-reading, I'm not sure I answered your question. If the combination
>in question is CW + EVB + DBug-12, then I did'nt try that (I used
>DBug-12 with MiniIDE terminal program.) I think the shortcut is to ask
>the MW people on the list as to whether a Statonary template is
>available for the EVB as Pod - in looking just now I couldn't find
>one. You had better specify C or assembler source.
>
>I did try D-Bug12 with NoICE but couldn't get it to do paging for some
>reason.
>
>tks
>Bruce.
>--- In , "Bruce McMillan"
><bruce_at_pocket_neurobics@y...> wrote:
> > Robert,
> > I think it's clear that I'm not holding myself out as an expert.
> > My advice would be that if you are confident that the code will
> > compile/assemble correctly under CW (it's not clear what you are using
> > in the manual solution), then it should be as simple as getting a
> > template for your processor & pod, and substituting your code for the
> > Main.asm or Main.c.
> >
> > Falling over at $C000 suggests that your code may protect the top
> > page. This was one of my tips. In my experience the preload routine
> > (p&e_preload.cmd in my case) doesn't clear the protection & you have
> > to do it manually in CW under ICD-12|Unsecure (I don't know what
> > routine this invokes.)
> >
> > The template may encompass several pods - select the right one in teh
> > drop down menu inside the window that shows the file structure - don't
> > know what it's called.
> >
> > bruce
> >
> > --- In , ra <swar@c...> wrote:
> > >
> > > On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan
>wrote:
> > >
> > > > [To put this in context, never had any problems interfacing
>between my
> > > > target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
> > > > sainthood).
> > >
> > >
> > > Hello Bruce
> > >
> > > I wonder if you could share any advice about the D-Bug12 solution
> > > (which remains a very attractive one if one cannot afford Doron's
>2000$
> > > route!).
> > > I have the Codewarrior successfully communicating with a DP256 as
>pod,
> > > but when it tries to load the s-records the elf loader bows out
>with an
> > > error saying it cannot write to address C000-C0090.
> > > The hardware connection seems to be ok, because if I reformat the
>same
> > > S-Record file with SRecCvrt and upload it manually with a terminal
> > > emulation program, it works fine.
> > >
> > > Is there some preload command needed for the Codewarrior to
>accomplish
> > > this?
> > >
> > > Many thanks!
> > > Robert >
>-------------------- >
>">http://docs.yahoo.com/info/terms/







Re: CodeWorrier + Multilink has landed. - ra - Sep 23 9:10:00 2003

Dear Gilles

Many thanks for the response!
I am trying to get the D-Bug12 Target to work with the new Version 3
Codewarrior.
I used the New Project Wizard to create the files for the Monitor
target.
When I run it, I can see the True Time Simulator successfully
communicating with the DP256 in Pod mode, but when it tries to upload
the code, the "Elf Loader" gives an error.
Is there any documentation on how to configure this?
Is it at the level of the Burner options? (now the S-record type is set
to "Automatic", with the code set to banked memory).
Or is some pre-load command file needed?
The target device is unsecured, and I can manually upload the s-records
to it with Hyperterminal talking to the same DP256 in Pod mode.

Many thanks for any additional insights you might have!
Robert On Dienstag, Sep 23, 2003, at 14:23 Europe/Paris, Gilles Blanquin wrote:

>
>
> Hi Bruce, Hi Robert.
>
> The D-Bug12 interface in CodeWarrior for the HC12 v2.0 has never been
> updated to support D-Bug12 monitors newer than v2.0.2 . This monitor
> was
> delivered with HC912B32 derivatives on M68HC12B32EVB boards.
>
> You might find stationery template only for HC812A4 and HC912B32
> devices in:
> -"(CodeWarrior_Examples)\HC12\D-Bug12 Target Interface" in
> "CodeWarrior for
> the HC12 v2.0"
> - "Examples\HC12\D-Bug12 Target Interface" in "CodeWarrior / MOT V1.2
> for
> HC12".
>
> However, the new CodeWarrior for HC12 V3.0 just released and available
> from
> Metrowerks web site provides a target interface to debug with the new
> Serial Monitor for HCS12 devices (AN here below).
>
> http://e-www.motorola.com/files/microcontrollers/doc/app_note/
> AN2548.pdf
>
> Regards,
> Gilles >
> At 12:58 PM 9/23/2003, you wrote:
>> Robert,
>> re-reading, I'm not sure I answered your question. If the combination
>> in question is CW + EVB + DBug-12, then I did'nt try that (I used
>> DBug-12 with MiniIDE terminal program.) I think the shortcut is to ask
>> the MW people on the list as to whether a Statonary template is
>> available for the EVB as Pod - in looking just now I couldn't find
>> one. You had better specify C or assembler source.
>>
>> I did try D-Bug12 with NoICE but couldn't get it to do paging for some
>> reason.
>>
>> tks
>> Bruce.
>> --- In , "Bruce McMillan"
>> <bruce_at_pocket_neurobics@y...> wrote:
>>> Robert,
>>> I think it's clear that I'm not holding myself out as an expert.
>>> My advice would be that if you are confident that the code will
>>> compile/assemble correctly under CW (it's not clear what you are
>>> using
>>> in the manual solution), then it should be as simple as getting a
>>> template for your processor & pod, and substituting your code for the
>>> Main.asm or Main.c.
>>>
>>> Falling over at $C000 suggests that your code may protect the top
>>> page. This was one of my tips. In my experience the preload routine
>>> (p&e_preload.cmd in my case) doesn't clear the protection & you have
>>> to do it manually in CW under ICD-12|Unsecure (I don't know what
>>> routine this invokes.)
>>>
>>> The template may encompass several pods - select the right one in teh
>>> drop down menu inside the window that shows the file structure -
>>> don't
>>> know what it's called.
>>>
>>> bruce
>>>
>>> --- In , ra <swar@c...> wrote:
>>>>
>>>> On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan
>> wrote:
>>>>
>>>>> [To put this in context, never had any problems interfacing
>> between my
>>>>> target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
>>>>> sainthood).
>>>>
>>>>
>>>> Hello Bruce
>>>>
>>>> I wonder if you could share any advice about the D-Bug12 solution
>>>> (which remains a very attractive one if one cannot afford Doron's
>> 2000$
>>>> route!).
>>>> I have the Codewarrior successfully communicating with a DP256 as
>> pod,
>>>> but when it tries to load the s-records the elf loader bows out
>> with an
>>>> error saying it cannot write to address C000-C0090.
>>>> The hardware connection seems to be ok, because if I reformat the
>> same
>>>> S-Record file with SRecCvrt and upload it manually with a terminal
>>>> emulation program, it works fine.
>>>>
>>>> Is there some preload command needed for the Codewarrior to
>> accomplish
>>>> this?
>>>>
>>>> Many thanks!
>>>> Robert
>>
>>
>>
>> --------------------
>>
>>
>>
>> ">http://docs.yahoo.com/info/terms/ > ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Upgrade to 128-Bit SSL Security!
> http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/dN_tlB/TM
> ---------------------------------
> ~->
>
> -------------------- >
> ">http://docs.yahoo.com/info/terms/
>






_____________________________
 Free pdf download: Advanced Linux Programming.


Re: CodeWorrier + Multilink has landed. - Gilles Blanquin - Sep 23 10:28:00 2003


Hi Bruce.

As I wrote in the previous reply, CodeWarrior does not support the latest
D-Bug12 monitor. The latest compatibility was with the version 2.0.2.

The HCS12 Serial Monitor is a new monitor and is different from the D-Bug12
monitor (no compatibility at all).

Regards,
Gilles For info, current D-Bug12 monitor:

DB12S12FW version 4.0.0b18
This version runs on all MC9S12Dx256, MC9S12Dx128, MC9S12A256, MC9S12A128,
MC9S12H256 and the BDM Programmer. This firmware supports programming all
Flash HC12 and HCS12 devices.

At 04:10 PM 9/23/2003, you wrote:
>Dear Gilles
>
>Many thanks for the response!
>I am trying to get the D-Bug12 Target to work with the new Version 3
>Codewarrior.
>I used the New Project Wizard to create the files for the Monitor
>target.
>When I run it, I can see the True Time Simulator successfully
>communicating with the DP256 in Pod mode, but when it tries to upload
>the code, the "Elf Loader" gives an error.
>Is there any documentation on how to configure this?
>Is it at the level of the Burner options? (now the S-record type is set
>to "Automatic", with the code set to banked memory).
>Or is some pre-load command file needed?
>The target device is unsecured, and I can manually upload the s-records
>to it with Hyperterminal talking to the same DP256 in Pod mode.
>
>Many thanks for any additional insights you might have!
>Robert >On Dienstag, Sep 23, 2003, at 14:23 Europe/Paris, Gilles Blanquin wrote:
>
> >
> >
> > Hi Bruce, Hi Robert.
> >
> > The D-Bug12 interface in CodeWarrior for the HC12 v2.0 has never been
> > updated to support D-Bug12 monitors newer than v2.0.2 . This monitor
> > was
> > delivered with HC912B32 derivatives on M68HC12B32EVB boards.
> >
> > You might find stationery template only for HC812A4 and HC912B32
> > devices in:
> > -"(CodeWarrior_Examples)\HC12\D-Bug12 Target Interface" in
> > "CodeWarrior for
> > the HC12 v2.0"
> > - "Examples\HC12\D-Bug12 Target Interface" in "CodeWarrior / MOT V1.2
> > for
> > HC12".
> >
> > However, the new CodeWarrior for HC12 V3.0 just released and available
> > from
> > Metrowerks web site provides a target interface to debug with the new
> > Serial Monitor for HCS12 devices (AN here below).
> >
> > http://e-www.motorola.com/files/microcontrollers/doc/app_note/
> > AN2548.pdf
> >
> > Regards,
> > Gilles
> >
> >
> >
> > At 12:58 PM 9/23/2003, you wrote:
> >> Robert,
> >> re-reading, I'm not sure I answered your question. If the combination
> >> in question is CW + EVB + DBug-12, then I did'nt try that (I used
> >> DBug-12 with MiniIDE terminal program.) I think the shortcut is to ask
> >> the MW people on the list as to whether a Statonary template is
> >> available for the EVB as Pod - in looking just now I couldn't find
> >> one. You had better specify C or assembler source.
> >>
> >> I did try D-Bug12 with NoICE but couldn't get it to do paging for some
> >> reason.
> >>
> >> tks
> >> Bruce.
> >> --- In , "Bruce McMillan"
> >> <bruce_at_pocket_neurobics@y...> wrote:
> >>> Robert,
> >>> I think it's clear that I'm not holding myself out as an expert.
> >>> My advice would be that if you are confident that the code will
> >>> compile/assemble correctly under CW (it's not clear what you are
> >>> using
> >>> in the manual solution), then it should be as simple as getting a
> >>> template for your processor & pod, and substituting your code for the
> >>> Main.asm or Main.c.
> >>>
> >>> Falling over at $C000 suggests that your code may protect the top
> >>> page. This was one of my tips. In my experience the preload routine
> >>> (p&e_preload.cmd in my case) doesn't clear the protection & you have
> >>> to do it manually in CW under ICD-12|Unsecure (I don't know what
> >>> routine this invokes.)
> >>>
> >>> The template may encompass several pods - select the right one in teh
> >>> drop down menu inside the window that shows the file structure -
> >>> don't
> >>> know what it's called.
> >>>
> >>> bruce
> >>>
> >>> --- In , ra <swar@c...> wrote:
> >>>>
> >>>> On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan
> >> wrote:
> >>>>
> >>>>> [To put this in context, never had any problems interfacing
> >> between my
> >>>>> target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
> >>>>> sainthood).
> >>>>
> >>>>
> >>>> Hello Bruce
> >>>>
> >>>> I wonder if you could share any advice about the D-Bug12 solution
> >>>> (which remains a very attractive one if one cannot afford Doron's
> >> 2000$
> >>>> route!).
> >>>> I have the Codewarrior successfully communicating with a DP256 as
> >> pod,
> >>>> but when it tries to load the s-records the elf loader bows out
> >> with an
> >>>> error saying it cannot write to address C000-C0090.
> >>>> The hardware connection seems to be ok, because if I reformat the
> >> same
> >>>> S-Record file with SRecCvrt and upload it manually with a terminal
> >>>> emulation program, it works fine.
> >>>>
> >>>> Is there some preload command needed for the Codewarrior to
> >> accomplish
> >>>> this?
> >>>>
> >>>> Many thanks!
> >>>> Robert
> >>
> >>
> >>
> >> --------------------
> >>
> >>
> >>
> >> ">http://docs.yahoo.com/info/terms/
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> > ---------------------~-->
> > Upgrade to 128-Bit SSL Security!
> > http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/dN_tlB/TM
> > ---------------------------------
> > ~->
> >
> > --------------------
> >
> >
> >
> > ">http://docs.yahoo.com/info/terms/
> >
>-------------------- >
>">http://docs.yahoo.com/info/terms/







Re: CodeWorrier + Multilink has landed. - ra - Sep 24 1:42:00 2003

Dear Gilles

Many thanks for the additional clarification (I had interpreted "new
serial monitor" to mean the newer version 4 of D-Bug12 -- in the
monitor target's release note, this is not very clear too)

Last question: would you be able to send me the object code for the
needed new serial monitor or point me to where it can be downloaded?
I was not able to find it on the Motorola website nor at the location
indicated in the AN2548.pdf app-note.

Many thanks again!
Robert On Sep 23, 2003, at 17:28 Europe/Paris, Gilles Blanquin wrote:

>
>
> Hi Bruce.
>
> As I wrote in the previous reply, CodeWarrior does not support the
> latest
> D-Bug12 monitor. The latest compatibility was with the version 2.0.2.
>
> The HCS12 Serial Monitor is a new monitor and is different from the
> D-Bug12
> monitor (no compatibility at all).
>
> Regards,
> Gilles > For info, current D-Bug12 monitor:
>
> DB12S12FW version 4.0.0b18
> This version runs on all MC9S12Dx256, MC9S12Dx128, MC9S12A256,
> MC9S12A128,
> MC9S12H256 and the BDM Programmer. This firmware supports programming
> all
> Flash HC12 and HCS12 devices.
>
> At 04:10 PM 9/23/2003, you wrote:
>> Dear Gilles
>>
>> Many thanks for the response!
>> I am trying to get the D-Bug12 Target to work with the new Version 3
>> Codewarrior.
>> I used the New Project Wizard to create the files for the Monitor
>> target.
>> When I run it, I can see the True Time Simulator successfully
>> communicating with the DP256 in Pod mode, but when it tries to upload
>> the code, the "Elf Loader" gives an error.
>> Is there any documentation on how to configure this?
>> Is it at the level of the Burner options? (now the S-record type is
>> set
>> to "Automatic", with the code set to banked memory).
>> Or is some pre-load command file needed?
>> The target device is unsecured, and I can manually upload the
>> s-records
>> to it with Hyperterminal talking to the same DP256 in Pod mode.
>>
>> Many thanks for any additional insights you might have!
>> Robert
>>
>>
>> On Dienstag, Sep 23, 2003, at 14:23 Europe/Paris, Gilles Blanquin
>> wrote:
>>
>>>
>>>
>>> Hi Bruce, Hi Robert.
>>>
>>> The D-Bug12 interface in CodeWarrior for the HC12 v2.0 has never been
>>> updated to support D-Bug12 monitors newer than v2.0.2 . This monitor
>>> was
>>> delivered with HC912B32 derivatives on M68HC12B32EVB boards.
>>>
>>> You might find stationery template only for HC812A4 and HC912B32
>>> devices in:
>>> -"(CodeWarrior_Examples)\HC12\D-Bug12 Target Interface" in
>>> "CodeWarrior for
>>> the HC12 v2.0"
>>> - "Examples\HC12\D-Bug12 Target Interface" in "CodeWarrior / MOT V1.2
>>> for
>>> HC12".
>>>
>>> However, the new CodeWarrior for HC12 V3.0 just released and
>>> available
>>> from
>>> Metrowerks web site provides a target interface to debug with the new
>>> Serial Monitor for HCS12 devices (AN here below).
>>>
>>> http://e-www.motorola.com/files/microcontrollers/doc/app_note/
>>> AN2548.pdf
>>>
>>> Regards,
>>> Gilles
>>>
>>>
>>>
>>> At 12:58 PM 9/23/2003, you wrote:
>>>> Robert,
>>>> re-reading, I'm not sure I answered your question. If the
>>>> combination
>>>> in question is CW + EVB + DBug-12, then I did'nt try that (I used
>>>> DBug-12 with MiniIDE terminal program.) I think the shortcut is to
>>>> ask
>>>> the MW people on the list as to whether a Statonary template is
>>>> available for the EVB as Pod - in looking just now I couldn't find
>>>> one. You had better specify C or assembler source.
>>>>
>>>> I did try D-Bug12 with NoICE but couldn't get it to do paging for
>>>> some
>>>> reason.
>>>>
>>>> tks
>>>> Bruce.
>>>> --- In , "Bruce McMillan"
>>>> <bruce_at_pocket_neurobics@y...> wrote:
>>>>> Robert,
>>>>> I think it's clear that I'm not holding myself out as an expert.
>>>>> My advice would be that if you are confident that the code will
>>>>> compile/assemble correctly under CW (it's not clear what you are
>>>>> using
>>>>> in the manual solution), then it should be as simple as getting a
>>>>> template for your processor & pod, and substituting your code for
>>>>> the
>>>>> Main.asm or Main.c.
>>>>>
>>>>> Falling over at $C000 suggests that your code may protect the top
>>>>> page. This was one of my tips. In my experience the preload routine
>>>>> (p&e_preload.cmd in my case) doesn't clear the protection & you
>>>>> have
>>>>> to do it manually in CW under ICD-12|Unsecure (I don't know what
>>>>> routine this invokes.)
>>>>>
>>>>> The template may encompass several pods - select the right one in
>>>>> teh
>>>>> drop down menu inside the window that shows the file structure -
>>>>> don't
>>>>> know what it's called.
>>>>>
>>>>> bruce
>>>>>
>>>>> --- In , ra <swar@c...> wrote:
>>>>>>
>>>>>> On Dienstag, Sep 23, 2003, at 09:43 Europe/Paris, Bruce McMillan
>>>> wrote:
>>>>>>
>>>>>>> [To put this in context, never had any problems interfacing
>>>> between my
>>>>>>> target & the Motorola EVB as pod + D-Bug12 (I nominate Gordon for
>>>>>>> sainthood).
>>>>>>
>>>>>>
>>>>>> Hello Bruce
>>>>>>
>>>>>> I wonder if you could share any advice about the D-Bug12 solution
>>>>>> (which remains a very attractive one if one cannot afford Doron's
>>>> 2000$
>>>>>> route!).
>>>>>> I have the Codewarrior successfully communicating with a DP256 as
>>>> pod,
>>>>>> but when it tries to load the s-records the elf loader bows out
>>>> with an
>>>>>> error saying it cannot write to address C000-C0090.
>>>>>> The hardware connection seems to be ok, because if I reformat the
>>>> same
>>>>>> S-Record file with SRecCvrt and upload it manually with a terminal
>>>>>> emulation program, it works fine.
>>>>>>
>>>>>> Is there some preload command needed for the Codewarrior to
>>>> accomplish
>>>>>> this?
>>>>>>
>>>>>> Many thanks!
>>>>>> Robert
>>>>
>>>>
>>>>
>>>> --------------------
>>>>
>>>>
>>>>
>>>> ">http://docs.yahoo.com/info/terms/
>>>
>>>
>>> ------------------------ Yahoo! Groups Sponsor
>>> ---------------------~-->
>>> Upgrade to 128-Bit SSL Security!
>>> http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/dN_tlB/TM
>>> ---------------------------------
>>> ~->
>>>
>>> --------------------
>>>
>>>
>>>
>>> ">http://docs.yahoo.com/info/terms/
>>>
>>
>>
>>
>> --------------------
>>
>>
>>
>> ">http://docs.yahoo.com/info/terms/ > ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> Upgrade to 128-Bit SSL Security!
> http://us.click.yahoo.com/p7cEmB/s7qGAA/yigFAA/dN_tlB/TM
> ---------------------------------
> ~->
>
> -------------------- >
> ">http://docs.yahoo.com/info/terms/
>