PAUL James | 9 May 17:30
Favicon

[PIC]: Memory Map Question

All,

I have a question for the PIC community that has me stumped at the
moment.  Here is the scenario.
I am using an ispPro programmer from Basic Micro.  It works well, and we
have used it for a long time.
We have a 16F76 in one of our systems.  I erased the program memory, and
reprogrammed it with different code.
At the end of the programming cycle, I get an error that the programmer
can't verify location $4000.  
The top of the address space is $3FFF or at least I thought it was.  I
looked at the datasheet, but didn't find anything
about address $4000.  I thought it might be a system location that is
only availabe to the device programmer at program time.

Does anybody know what is significant about this location?  When I do a
read, I see location $4000 is $80.  When I erase it, it still says $80.
It should be $FF if it is truly erased I think.  If I reprogram it with
the old firmware, I still get the error.  It's like the bit is stuck
high.  It can't be
programmed low.

Anyway, if anyone has any insight, let me know.   I would appreciate it.

 

 
Thanks and Regards,

 
(Continue reading)

RE: [PIC]: Memory Map Question


> -----Original Message-----
> From: piclist-bounces <at> mit.edu [mailto:piclist-bounces <at> mit.edu] On
Behalf
> Of PAUL James
> Sent: 09 May 2008 16:34
> To: Microcontroller discussion list - Public.
> Subject: [PIC]: Memory Map Question
> 
> All,
> 
> I have a question for the PIC community that has me stumped at the
> moment.  Here is the scenario.
> I am using an ispPro programmer from Basic Micro.  It works well, and
we
> have used it for a long time.
> We have a 16F76 in one of our systems.  I erased the program memory,
and
> reprogrammed it with different code.
> At the end of the programming cycle, I get an error that the
programmer
> can't verify location $4000.
> The top of the address space is $3FFF or at least I thought it was.  I
> looked at the datasheet, but didn't find anything
> about address $4000.  I thought it might be a system location that is
> only availabe to the device programmer at program time.
> 
> Does anybody know what is significant about this location?  When I do
a
> read, I see location $4000 is $80.  When I erase it, it still says
(Continue reading)

PAUL James | 9 May 18:00
Favicon

RE: [PIC]: Memory Map Question


Michael,

No, because the firmware file I am attempting to program is the file we
read from the unit.
We just went in and modified a few bytes to patch a particular portion
of the program.  But 
The patch we made was at the beginning of the file, not anywhere near
the end of the file which
Goes up to $4015.   It seems to me that this address just about has to
be some processor specific
Setup information location, and not a program space location.  Something
like maybe the CONFIG 
Register or maybe the OSCILLATOR control register or some such.  At
least that's my guess.

Thanks for the repsonse, and if you have any futher ideas or
suggestions, please pass them along.
I'll take all the help I can get.

	
Thanks and Regards,

	
Jim  

-----Original Message-----
From: piclist-bounces <at> mit.edu [mailto:piclist-bounces <at> mit.edu] On Behalf
Of Michael Rigby-Jones
Sent: Friday, May 09, 2008 10:49 AM
(Continue reading)

Jan-Erik Soderholm | 9 May 19:53
Picon

Re: [PIC]: Memory Map Question

PAUL James wrote:
> Michael,
> 
> No, because the firmware file I am attempting to program is the file we
> read from the unit.
> We just went in and modified a few bytes to patch a particular portion
> of the program.  But 
> The patch we made was at the beginning of the file, not anywhere near
> the end of the file which
> Goes up to $4015.   It seems to me that this address just about has to
> be some processor specific
> Setup information location, and not a program space location.  Something
> like maybe the CONFIG ...

Well, if it *is*, it should be clear from the data sheet.
The CONFIG addresses are as fare as I know always documented.

[Downloading datashet...]
Yup, CONFIG bits are between h'2000' and h'2007', which
probably are adressed as h'4000' to h'4015' in the HEX file...

Jan-Erik.

> Register or maybe the OSCILLATOR control register or some such.  At
> least that's my guess.
> 
> Thanks for the repsonse, and if you have any futher ideas or
> suggestions, please pass them along.
> I'll take all the help I can get.
> 
(Continue reading)

Timothy Weber | 9 May 20:50
Favicon

Re: [PIC]: Memory Map Question

Jan-Erik Soderholm wrote:
> Yup, CONFIG bits are between h'2000' and h'2007', which
> probably are adressed as h'4000' to h'4015' in the HEX file...

Is it possible those are the first bytes to be compared, and you had 
code protection set on?
-- 
Timothy J. Weber
http://timothyweber.org
--

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

PAUL James | 9 May 21:11
Favicon

RE: [PIC]: Memory Map Question


Tim,

No.  Code protect is not on now, and it wasn't on before.
Thanks for the response though.

					Regards,

					  Jim 

-----Original Message-----
From: piclist-bounces <at> mit.edu [mailto:piclist-bounces <at> mit.edu] On Behalf
Of Timothy Weber
Sent: Friday, May 09, 2008 1:51 PM
To: Microcontroller discussion list - Public.
Subject: Re: [PIC]: Memory Map Question

Jan-Erik Soderholm wrote:
> Yup, CONFIG bits are between h'2000' and h'2007', which probably are 
> adressed as h'4000' to h'4015' in the HEX file...

Is it possible those are the first bytes to be compared, and you had
code protection set on?
--
Timothy J. Weber
http://timothyweber.org
--
http://www.piclist.com PIC/SX FAQ & list archive View/change your
membership options at http://mailman.mit.edu/mailman/listinfo/piclist

(Continue reading)


Gmane