Lpc2000

At 07:42 PM 1/25/06 -0500, Tom Walsh wrote:
>Guillermo Prandi wrote:
> >Hi. Are Flash write errors normal, i.e. a known issue? When
> >programming my LPC2138 using the isp21lpc utility, every now and then
> >I get a write error; a second attempt always succeed. This happens
> >roughly once every 100 programming attempts. I thought it could have
> >been a problem with my serial cable or some other hardware problem,
> >but now I added an IAP function to my test program and I am getting
> >errors too (i.e., saved data differs from the source data, although
> >the IAP copy ram to flash command returns CMD_SUCCESS). I checked
> >everything and I think I covered the normal requisites:
> >
> >
> >
>
>There seems to be something goofy going on with those utils.  I tried
>using the lpc21isp (version 1.24) package on Linux, but it would
>sometimes error out at random locations.  Not sure why.
>
>I finally had to write an ISP loader for an LPC2138 to program an
>LPC2106.  This loader source I then took an hung some RS232 routines
>onto it so I could also up load into the LPC2138 from Linux.  So far, my
>loader works flawlessly.

I had some similar occurrences with the Philips utility as well.  They seem 
to have disappeared about the time I started using the automatic 
downloading and a good cabling setup on the last few centimeters.  I've not 
had a similar problem with the lpc21isp program and I've not tried 
IAP.  Mind you the write errors I was seeing were not verify errors but the 
protocol appearing to simply stop and it was rare enough that I couldn't be 
certain as to its source.

A quick question to verify my understanding of what you are seeing 
Guillermo, is your verification source the same buffer you just used to 
program via IAP or do you refresh it from elsewhere before you do the compare?

Just a little more grist for the mill.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,   be 
they legal, genetic, or physical.  If you don't believe me, try to chew a 
radio signal. "  -- Kelvin Throop, III
http://www.aeolusdevelopment.com/