EmbeddedRelated.com
Forums
Memfault Beyond the Launch

changing bprot

Started by angel_prints_198 July 9, 2004
hi! i'm using an hc11a1 chip... i want to write to its internal
eeprom but apparently, writing to eeprom isn't allowed. i checked
the config register & it appears to be 0d... the bprot register on
the other hand is ff... i tried changing it to 00 but i get
errors... does anyone know how i can change bprot? thanks!!!



--- In , "angel_prints_198"
<angel_prints_198@y...> wrote:
> hi! i'm using an hc11a1 chip... i want to write to its internal
> eeprom but apparently, writing to eeprom isn't allowed. i checked
> the config register & it appears to be 0d... the bprot register on
> the other hand is ff... i tried changing it to 00 but i get
> errors... does anyone know how i can change bprot? thanks!!!

Without pulling the manuals right now and from memory:

1. The chip has to HAVE EEPROM - I think some versions don't.

2. It has to be enabled in CONFIG - the CONFIG register programming is
different than other programming (it will not read back at the same
value programmed) so read the manual for your programmer.

3. The charge pump settings may have to be changed, depending on your
clock speed.

Some of the configuration registers are time limited and have to be
set within 64 (?) cycles of reset - that wont happen with an EVM or
EVB unless you do a straight run in the USER map.

4. After you have completed initializatin properly, a write to EEPROM
consists of manipulating the bits in the program register in the
proper sequence with the right timing. There is an example in the
manual as I recall.



--- In , "angel_prints_198"
<angel_prints_198@y...> wrote:
> hi! i'm using an hc11a1 chip... i want to write to its internal
> eeprom but apparently, writing to eeprom isn't allowed. i checked
> the config register & it appears to be 0d... the bprot register on
> the other hand is ff... i tried changing it to 00 but i get
> errors... does anyone know how i can change bprot? thanks!!!

I have discussed this issue privately with "angel_prints_198" and
according to what she told me, the device in quesiton is a (Toshiba-
manufactured) A1, which DOES have a 512-byte EEPROM. The CONFIG
register has successfully been re-programmed (using JBug11) to $0D,
enabling the onchip EEPROM.

As noted in the message above, the BPROT register (does the A1 have
a BPROT register?) reads back as $FF, and cannot be changed using
JBug. Attempts to write to the EEPROM (using JBug) fail. JBug does
allow reading/writing of other registers in the IO space. The
hardware (MODA/MODB and RS232) settings appear to be correct, as
well as the JBug configuration as described to me.

I'm stumped. Does anyone else here have any suggestions?


Mark --

See below --

Bob smith --- Avoid computer viruses, Practice safe hex ---

-- Specializing in small, cost effective
embedded control systems --

http://www.smithmachineworks.com/embedprod.html Robert L. (Bob) Smith
Smith Machine Works, Inc.
9900 Lumlay Road
Richmond, VA 23236 804/745-2608
----- Original Message -----
From: "Mark Schultz" <>
To: <>
Sent: Friday, July 09, 2004 8:12 AM
Subject: [m68HC11] Re: changing bprot > --- In , "angel_prints_198"
> <angel_prints_198@y...> wrote:
> > hi! i'm using an hc11a1 chip... i want to write to its internal
> > eeprom but apparently, writing to eeprom isn't allowed. i checked
> > the config register & it appears to be 0d... the bprot register on
> > the other hand is ff... i tried changing it to 00 but i get
> > errors... does anyone know how i can change bprot? thanks!!!
>
> I have discussed this issue privately with "angel_prints_198" and
> according to what she told me, the device in quesiton is a (Toshiba-
> manufactured) A1, which DOES have a 512-byte EEPROM. The CONFIG
> register has successfully been re-programmed (using JBug11) to $0D,
> enabling the onchip EEPROM.

Ah, now the details come out. This provides several strong clues!

If it DOES have a 512-byte EEPROM, but the CONFIG register was NOT
programmed to $0D, this is a strong indication that Toshiba did not intend
for the EEPROM to be used. (failed in factory test, etc.).

You ask a VERY valid question, does the device even HAVE a BPROT register??

The fact that it reads back $FF (instead of the normal value of $1F) when
other I/O registers read normally is a VERY strong indication that BPORT is
not implemented or is faulty (which is possibly why EEPROM was disabled in
the first place).

Trying to further pursue this problem in a Motorola context is foolish. You
are going to have to find the Toshiba equivalent of the Technical Data
Manual for its A series devices to pursue this question.

Ms. Angel Printer has already lost too much blood and time over this issue.
She should go buy a known good E1 device (try DigiKey) and get on with life.

Best wishes, Bob Smith

>
> As noted in the message above, the BPROT register (does the A1 have
> a BPROT register?) reads back as $FF, and cannot be changed using
> JBug. Attempts to write to the EEPROM (using JBug) fail. JBug does
> allow reading/writing of other registers in the IO space. The
> hardware (MODA/MODB and RS232) settings appear to be correct, as
> well as the JBug configuration as described to me.
>
> I'm stumped. Does anyone else here have any suggestions? >
> --
------
> Yahoo! Groups Links
>
> a.. To


Mark --

There is something about this thread that has been bothering me for the last
several postings.

After reviewing my old lab notes and procedures, I have confirmed that when
I update the BPROT register prior to programming the EEPROM in my E9
devices,

I allways use the (R)egister command, not the (M)emory(M)odify command.

I.e., R BPROT to enable EEPROM, but leave CONFIG protected.

Could her problems be as simple as this?

Also, see John Beatty's recent posting re: possible communications problems
in Ver 4 Jbug11.

Best wishes, Bob Smith

--- Avoid computer viruses, Practice safe hex ---

-- Specializing in small, cost effective
embedded control systems --

http://www.smithmachineworks.com/embedprod.html Robert L. (Bob) Smith
Smith Machine Works, Inc.
9900 Lumlay Road
Richmond, VA 23236 804/745-2608
----- Original Message -----
From: "Mark Schultz" <>
To: <>
Sent: Friday, July 09, 2004 8:12 AM
Subject: [m68HC11] Re: changing bprot > --- In , "angel_prints_198"
> <angel_prints_198@y...> wrote:
> > hi! i'm using an hc11a1 chip... i want to write to its internal
> > eeprom but apparently, writing to eeprom isn't allowed. i checked
> > the config register & it appears to be 0d... the bprot register on
> > the other hand is ff... i tried changing it to 00 but i get
> > errors... does anyone know how i can change bprot? thanks!!!
>
> I have discussed this issue privately with "angel_prints_198" and
> according to what she told me, the device in quesiton is a (Toshiba-
> manufactured) A1, which DOES have a 512-byte EEPROM. The CONFIG
> register has successfully been re-programmed (using JBug11) to $0D,
> enabling the onchip EEPROM.
>
> As noted in the message above, the BPROT register (does the A1 have
> a BPROT register?) reads back as $FF, and cannot be changed using
> JBug. Attempts to write to the EEPROM (using JBug) fail. JBug does
> allow reading/writing of other registers in the IO space. The
> hardware (MODA/MODB and RS232) settings appear to be correct, as
> well as the JBug configuration as described to me.
>
> I'm stumped. Does anyone else here have any suggestions? >
> --
------
> Yahoo! Groups Links
>
> a.. To



----- Original Message -----
From: "angel_prints_198" <>
To: < > hi! i'm using an hc11a1 chip... i want to write to its internal
> eeprom but apparently, writing to eeprom isn't allowed. i checked
> the config register & it appears to be 0d... the bprot register on
> the other hand is ff... i tried changing it to 00 but i get
> errors... does anyone know how i can change bprot? thanks!!!

I think one of the differences between the A and E series is the introduction of
the BPROT register. I know for sure the MC68HC11A8 didn't have a BPROT (it is
mentioned in Mot's HC11 general manual).



--- In , "Bob Smith" <bobsmith5@v...> wrote:
> After reviewing my old lab notes and procedures, I have confirmed
> that when I update the BPROT register prior to programming the
> EEPROM in my E9 devices, I allways use the (R)egister command, not
> the (M)emory(M)odify command.
>
> I.e., R BPROT to enable EEPROM, but leave CONFIG protected.
>
> Could her problems be as simple as this?

Bob - I don't think so - I had her try both MM BPROT and R BPROT=0,
with similar results (BPROT remains = FF).

WRT Tony's comment about the A8 - This device does not have internal
EEPROM, as far as I know, hence the absence of BPROT. I did see the
comment in the HC11 Ref regarding the A8's lack of a BPROT register,
along with the caveat that not all HC11 devices have a BPROT.

I looked around a bit for Toshiba reference material on their A1
variant, without success. I could not even find any data on the
Mot/Freescale site regarding the A1.

I'm inclined to agree with Bob that "Angel Printer" ;) should try to
get a E-series device if at all possible. However, this may not be
an option for her.



As far as I can deduce from my old copy of the 'Pink
Book', the A8 and A1 both have 512 bytes of EEPROM.
The A0 had no EEPROM. The BPROT register was
introduced with the E series devices as an extra
safety measure against accidental EEPROM or CONFIG
writing. I presume also that Mot only ever made A8
dies and that those whose mask ROM didn't work or was
corrupted became A1's, and those whose EEPROM didn't
work either became A0's. John Beatty --- Mark Schultz <> wrote: (snipped)

> --- In , "Bob Smith"
>
> WRT Tony's comment about the A8 - This device does
> not have internal
> EEPROM, as far as I know, hence the absence of
> BPROT. I did see the
> comment in the HC11 Ref regarding the A8's lack of a
> BPROT register,
> along with the caveat that not all HC11 devices have
> a BPROT.
>
___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com



I agree with John.

My old Pink Book cleary shows in Table 1-1 that the A1 and A8 both had
EEPROM, but the A0 did not.

It also clearly states in Paragraph 4.3.4, "There is no BPROT register in
the MC68HC11A8"! And there is a similar statement in the White Book.

And since the A0 and A1 are identical to the A8 except with certain memory
resources "disabled", I conclude that they also have no BPROT register.
Finally, this is confirmed by the fact that the register reads back $FF
which is the normal response when reading a location that is not implemented
on HC11s.

Incidently, I recall a discussion with a Motorola factory engineer several
years ago that confirmed that all A0's and A1's are made from the same die
as the A8's and simply have certain memory resources disabled because they
are flawed, OR, more likely, because the mask ROMs had been programmed with
bad code. It other words the A1s are a way of disposing of unloved and
orphaned A8s.

Mark, I _may_ have an old, used E1 laying around. I could get it out and
test it and the BPROT register with JBUG11 if you could find a way of
getting it to Angel Prints.

Bob Smith

--- Avoid computer viruses, Practice safe hex ---

-- Specializing in small, cost effective
embedded control systems --

http://www.smithmachineworks.com/embedprod.html Robert L. (Bob) Smith
Smith Machine Works, Inc.
9900 Lumlay Road
Richmond, VA 23236 804/745-2608
----- Original Message -----
From: "John Beatty" <>
To: <>
Sent: Sunday, July 11, 2004 4:38 AM
Subject: Re: [m68HC11] Re: changing bprot > As far as I can deduce from my old copy of the 'Pink
> Book', the A8 and A1 both have 512 bytes of EEPROM.
> The A0 had no EEPROM. The BPROT register was
> introduced with the E series devices as an extra
> safety measure against accidental EEPROM or CONFIG
> writing. I presume also that Mot only ever made A8
> dies and that those whose mask ROM didn't work or was
> corrupted became A1's, and those whose EEPROM didn't
> work either became A0's. > John Beatty > --- Mark Schultz <> wrote: (snipped)
>
> > --- In , "Bob Smith"
> >
> > WRT Tony's comment about the A8 - This device does
> > not have internal
> > EEPROM, as far as I know, hence the absence of
> > BPROT. I did see the
> > comment in the HC11 Ref regarding the A8's lack of a
> > BPROT register,
> > along with the caveat that not all HC11 devices have
> > a BPROT.
> >
> ___________________________________________________________ALL-NEW Yahoo!
Messenger - sooooo many all-new ways to express yourself
http://uk.messenger.yahoo.com
>
> --
------
> Yahoo! Groups Links
>
> a.. To




Memfault Beyond the Launch