FBULK ;NP doesn't always work on DP256 - Help!

Started by Steve Gordon October 28, 2002
Hello,

So far, we HAVE been able to erase and program the DP256 using the D-Bug12
Version 4.x.x.

A problem is happening when the chip is programmed incorrectly with a bad
format S-19 file. We have been unable to FBULK the device to erase it.

Is there a simple sequence of commands to enter, to get FBULK to erase the
target device?

I have tried to modify the first six Flash Registers at address 100. If we
are lucky enough, it will come up in a state that lets us erase it.
When we get it loaded properly, with a decent little program, it is as usual
to erase it and try again.

I am currently trying to turn on the RTC interrupt, when I send my code into
the chip and it isn't right, I become stuck in this mode
Where, I cannot erase the chip. Can anyone specify what needs to be done
when the DP256 won't let us erase the whole thing???

Thank you very much.

Steven R. Gordon
Hardware Engineer
New Product Division

Moore Industries International
The Interface Solution Experts
16650 Schoenborn Street
North Hills, CA 91343-6196
Phone: (818) 891 - 2816
Fax: (818) 891 - 2816
Email: <mailto:>
Website: www.miinet.com <http://www.miinet.com/




Steve

Most likely your wrote the word at $ff0e and set
the sevice security. Get a free copy of unsecure_12
from P&E's web site at www.pemicro.com and
see if you can unsecure it.

Regards
Dave Perreault Steve Gordon wrote:

>Hello,
>
>So far, we HAVE been able to erase and program the DP256 using the D-Bug12
>Version 4.x.x.
>
>A problem is happening when the chip is programmed incorrectly with a bad
>format S-19 file. We have been unable to FBULK the device to erase it.
>
>Is there a simple sequence of commands to enter, to get FBULK to erase the
>target device?
>
>I have tried to modify the first six Flash Registers at address 100. If we
>are lucky enough, it will come up in a state that lets us erase it.
>When we get it loaded properly, with a decent little program, it is as usual
>to erase it and try again.
>
>I am currently trying to turn on the RTC interrupt, when I send my code into
>the chip and it isn't right, I become stuck in this mode
>Where, I cannot erase the chip. Can anyone specify what needs to be done
>when the DP256 won't let us erase the whole thing???
>
>Thank you very much.
>
>Steven R. Gordon
>Hardware Engineer
>New Product Division
>
>Moore Industries International
>The Interface Solution Experts
>16650 Schoenborn Street
>North Hills, CA 91343-6196
>Phone: (818) 891 - 2816
>Fax: (818) 891 - 2816
>Email: <mailto:>
>Website: www.miinet.com <http://www.miinet.com/ >-------------------- >
>">http://docs.yahoo.com/info/terms/


Steve,

>A problem is happening when the chip is programmed incorrectly with a bad
>format S-19 file. We have been unable to FBULK the device to erase it.

What do you mean by a "bad format S-19 file". Could you be more specific? The
FBULK command should allow the erasure of the target MCU Flash even if the S19
file contained data that programmed some of the Flash protection register
bytes. The only condition under which FBULK wouldn't work is if the S19 file
contained data that programmed the security byte to place the MCU in a secure
state. However, if this were the case, you would loose BDM communication & be
presented with the "Can't Communicate...." menu.

Send me the S-Record file that is causing the problem off list & I'll have a
look at it.

Regards,
Gordon

Steve Gordon wrote:

> Hello,
>
> So far, we HAVE been able to erase and program the DP256 using the D-Bug12
> Version 4.x.x.
>
> A problem is happening when the chip is programmed incorrectly with a bad
> format S-19 file. We have been unable to FBULK the device to erase it.
>
> Is there a simple sequence of commands to enter, to get FBULK to erase the
> target device?
>
> I have tried to modify the first six Flash Registers at address 100. If we
> are lucky enough, it will come up in a state that lets us erase it.
> When we get it loaded properly, with a decent little program, it is as usual
> to erase it and try again.
>
> I am currently trying to turn on the RTC interrupt, when I send my code into
> the chip and it isn't right, I become stuck in this mode
> Where, I cannot erase the chip. Can anyone specify what needs to be done
> when the DP256 won't let us erase the whole thing???
>
> Thank you very much.
>
> Steven R. Gordon
> Hardware Engineer
> New Product Division
>
> Moore Industries International
> The Interface Solution Experts
> 16650 Schoenborn Street
> North Hills, CA 91343-6196
> Phone: (818) 891 - 2816
> Fax: (818) 891 - 2816
> Email: <mailto:>
> Website: www.miinet.com <http://www.miinet.com/ >
> -------------------- >
> ">http://docs.yahoo.com/info/terms/

--
===============================================================
Gordon Doughman Ph: 937-438-6811
Motorola Semiconductor Fax: 937-434-7457
Field Applications Engineer Pager: 800-759-8352 Pin: 1304089
Suite 175
3131 Newmark Drive
Miamisburg, OH 45342

Check out my HC12 book at:
http://www.rtcgroup.com/books/