MC9S12A128 vs MC9S12A128B

Hello,

I have some designs using the MC9S12A128B controller. Up until now these boards
have been stuffed with MC9S12A128B but in the latest batch, MC9S12A128 (without
B) has been used. My problem is that I can no longer program it with my
evaluation board (EVB Elektronik 9S12 256 Model 112 made by Elexsys) using D-
bug 12 V4.0.0b15 in BDM pod mode.

The chip can be erased using "fbulk" but as soon as I try to program it with
"fload" the evaluation board says "Can't write target memory". (The 128B can
still be programmed).

Using my P&E BDM multilink together with Codewarrior 3.1 works with both types.

Reading the d-bug manual I understand that this might have something to do with
that the controllers use different type of flash memory and need different type
of s-record files in d-bug12 (different in number of bytes per s record). I
have tried different type of s record files using SrecCvt but have never been
able to program the MC9S12A128 using d-bug12 and the evaluation board.

Am I on the right track at all? Anybody been down the same route and can advice
me how to get it to work with d-bug12 and my evaluation board again?

Best Regards / Ruben

=============================Ruben Jsson
AB Liros Electronic
Box 9124, 200 39 Malm Sweden
TEL INT +46 40142078
FAX INT +46 40947388
r...@pp.sbbs.se
============================= Start a New Thread

--- In 6..., "Ruben Jsson" wrote:
> The chip can be erased using "fbulk" but as soon as I try to
> program it with
> "fload" the evaluation board says "Can't write target memory".
> (The 128B can still be programmed).

It appears to me that the version of D-Bug12 just needs upgraded. The
one you are using probably just is not aware of the new PARTID.

D-Bug12 is up to V4.0.0b32 now.



Start a New Thread

>
> --- In 6..., "Ruben Jsson" wrote:
> > The chip can be erased using "fbulk" but as soon as I try to
> > program it with
> > "fload" the evaluation board says "Can't write target memory".
> > (The 128B can still be programmed).
>
> It appears to me that the version of D-Bug12 just needs upgraded. The
> one you are using probably just is not aware of the new PARTID.
>
> D-Bug12 is up to V4.0.0b32 now.
>

Yes, I will try that too. Just have to figure out how to get the new D-Bug12
into my eval board using Codewarrior and BDM multilink...

/ Ruben

=============================Ruben Jsson
AB Liros Electronic
Box 9124, 200 39 Malm Sweden
TEL INT +46 40142078
FAX INT +46 40947388
r...@pp.sbbs.se
============================= Start a New Thread

>
> --- In 6..., "Ruben Jsson" wrote:
> > The chip can be erased using "fbulk" but as soon as I try to
> > program it with
> > "fload" the evaluation board says "Can't write target memory".
> > (The 128B can still be programmed).
>
> It appears to me that the version of D-Bug12 just needs upgraded. The
> one you are using probably just is not aware of the new PARTID.
>
> D-Bug12 is up to V4.0.0b32 now.
>

Yes, that was it. Thanks.

/Ruben
=============================Ruben Jsson
AB Liros Electronic
Box 9124, 200 39 Malm Sweden
TEL INT +46 40142078
FAX INT +46 40947388
r...@pp.sbbs.se
============================= Start a New Thread