Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

Good morning, I have a bx24 which has gone from fully functional to functional without downloading capabilities. From one download to the next, I now recieve- "verify error, external eeprom" -on every download attempt of anything. The basicx still runs, from what I can tell. I just can't download anything new. Previously running is a program which writes to the internal eeprom, about 10Kb. There is a 0.1 second delay before each write; this is to make sure I don't get stuck in a fast loop while testing, and wear out eeprom locations via a programing mistake. So I don't THINK I have exceeded any write limits here. Are there any ideas as to what may have happened? Thank you for your time, Paul

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

if you look at the arcived about the bx-24, after many program changes and downloads it builds up a static-kind of a change in the eeprom. the only known cure is to plug it into a static foam block for 24 hours. the basic-x people are working on this. --- "Paul J. Csonka" <> wrote: > Good morning, > I have a bx24 which has gone from fully functional to functional > without downloading capabilities. > From one download to the next, I now recieve- > > "verify error, external eeprom" > > -on every download attempt of anything. > The basicx still runs, from what I can tell. I just can't > download anything new. > > Previously running is a program which writes to the internal > eeprom, about 10Kb. There is a 0.1 second delay before each write; > this > is to make sure I don't get stuck in a fast loop while testing, and > wear > out eeprom locations via a programing mistake. > So I don't THINK I have exceeded any write limits here. > > Are there any ideas as to what may have happened? > > Thank you for your time, > Paul > > > . > pened? > > Thank you for your time, > Paul > > > . ===== Tony Brenke North Tacoma, WA __________________________________________________

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I bought a second BX-24 because I was seeing so many communications failures when trying to download with the first one. The new BX-24 gives me the same error that you are seeing on about 95% of download attempts. If I use the Rescue function, I can download OK. On 2 Jan 2001, at 10:01, Paul J. Csonka wrote: > Good morning, > I have a bx24 which has gone from fully functional to functional > without downloading capabilities. > From one download to the next, I now recieve- > > "verify error, external eeprom" > > -on every download attempt of anything. > The basicx still runs, from what I can tell. I just can't > download anything new. > > Previously running is a program which writes to the internal > eeprom, about 10Kb. There is a 0.1 second delay before each write; > this is to make sure I don't get stuck in a fast loop while testing, > and wear out eeprom locations via a programing mistake. > So I don't THINK I have exceeded any write limits here. > > Are there any ideas as to what may have happened? > > Thank you for your time, > Paul --- Dave Houston http://Commander-X.com

______________________________
Stellaris® MCU Family: New Parts, New Package, New Price.


(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

My new BX-24 did it on the first attempted download. I don't think it has anything to do with the number of downloads. On 2 Jan 2001, at 10:26, Tony Brenke wrote: > if you look at the arcived about the bx-24, after many program changes > and downloads it builds up a static-kind of a change in the eeprom. > > the only known cure is to plug it into a static foam block for 24 > hours. > > the basic-x people are working on this. > > --- "Paul J. Csonka" <> wrote: > > Good morning, > > > > > > I have a bx24 which has gone from fully functional to functional > > without downloading capabilities. From one download to the next, I > > now recieve- > > > > "verify error, external eeprom" > > > > -on every download attempt of anything. > > The basicx still runs, from what I can tell. I just can't > > download anything new. > > > > Previously running is a program which writes to the internal > > eeprom, about 10Kb. There is a 0.1 second delay before each write; > > this is to make sure I don't get stuck in a fast loop while testing, > > and wear out eeprom locations via a programing mistake. So I don't > > THINK I have exceeded any write limits here. > > > > Are there any ideas as to what may have happened? > > > > Thank you for your time, > > Paul > > > > > > > > > > . > > pened? > > > > Thank you for your time, > > Paul > > > > > > > > > > . > > ===== > Tony Brenke > North Tacoma, WA > > __________________________________________________ --- Dave Houston http://Commander-X.com

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi Tony, I have looked at the archives and tried the various suggestions; before I even did so, I had left the bx24 in static foam overnight. I still have no communications, but perhaps it needs more time in the foam... Thank you for your help, Paul On Tue, 2 Jan 2001, Tony Brenke wrote: > if you look at the arcived about the bx-24, after many program changes > and downloads it builds up a static-kind of a change in the eeprom. > > the only known cure is to plug it into a static foam block for 24 > hours. > > the basic-x people are working on this. > > --- "Paul J. Csonka" <> wrote: > > Good morning, > > > > > > I have a bx24 which has gone from fully functional to functional > > without downloading capabilities. > > From one download to the next, I now recieve- > > > > "verify error, external eeprom" > > > > -on every download attempt of anything. > > The basicx still runs, from what I can tell. I just can't > > download anything new. > > > > Previously running is a program which writes to the internal > > eeprom, about 10Kb. There is a 0.1 second delay before each write; > > this > > is to make sure I don't get stuck in a fast loop while testing, and > > wear > > out eeprom locations via a programing mistake. > > So I don't THINK I have exceeded any write limits here. > > > > Are there any ideas as to what may have happened? > > > > Thank you for your time, > > Paul > > > > > > > > > > . > > pened? > > > > Thank you for your time, > > Paul > > > > > > > > > > . > > ===== > Tony Brenke > North Tacoma, WA > > __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi Dave, I have tried the rescue function several times, with no success yet. Thanks for your help, Paul On Tue, 2 Jan 2001, Dave Houston wrote: > I bought a second BX-24 because I was seeing so many communications > failures when trying to download with the first one. The new BX-24 > gives me the same error that you are seeing on about 95% of download > attempts. If I use the Rescue function, I can download OK. > > On 2 Jan 2001, at 10:01, Paul J. Csonka wrote: > > > Good morning, > > > > > > I have a bx24 which has gone from fully functional to functional > > without downloading capabilities. > > From one download to the next, I now recieve- > > > > "verify error, external eeprom" > > > > -on every download attempt of anything. > > The basicx still runs, from what I can tell. I just can't > > download anything new. > > > > Previously running is a program which writes to the internal > > eeprom, about 10Kb. There is a 0.1 second delay before each write; > > this is to make sure I don't get stuck in a fast loop while testing, > > and wear out eeprom locations via a programing mistake. > > So I don't THINK I have exceeded any write limits here. > > > > Are there any ideas as to what may have happened? > > > > Thank you for your time, > > Paul > > > > > > > > --- > Dave Houston > http://Commander-X.com

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

you were talking about saving data to the eeprom. what kind of data and how often were you doing this. if you were saving data in a fast loop you could have used the 100,000 writes (about) in a short amount of time. I sugest you use the eeprom data save only for data you have to have and can't do without. you might verywell have exceded the limit of your eeprom writes. --- "Paul J. Csonka" <> wrote: > Hi Tony, > > I have looked at the archives and tried the various > suggestions; before I even did so, I had left the bx24 in static foam > overnight. > I still have no communications, but perhaps it needs more time in > the foam... > > Thank you for your help, > Paul > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > if you look at the arcived about the bx-24, after many program > changes > > and downloads it builds up a static-kind of a change in the eeprom. > > > > the only known cure is to plug it into a static foam block for 24 > > hours. > > > > the basic-x people are working on this. > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > Good morning, > > > > > > > > > I have a bx24 which has gone from fully functional to functional > > > without downloading capabilities. > > > From one download to the next, I now recieve- > > > > > > "verify error, external eeprom" > > > > > > -on every download attempt of anything. > > > The basicx still runs, from what I can tell. I just can't > > > download anything new. > > > > > > Previously running is a program which writes to the internal > > > eeprom, about 10Kb. There is a 0.1 second delay before each > write; > > > this > > > is to make sure I don't get stuck in a fast loop while testing, > and > > > wear > > > out eeprom locations via a programing mistake. > > > So I don't THINK I have exceeded any write limits here. > > > > > > Are there any ideas as to what may have happened? > > > > > > Thank you for your time, > > > Paul > > > > > > > > > > > > > > > . > > > pened? > > > > > > Thank you for your time, > > > Paul > > > > > > > > > > > > > > > . > > > > > > > > > ===== > > Tony Brenke > > North Tacoma, WA > > > > __________________________________________________ > > > > > ===== Tony Brenke North Tacoma, WA __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi Tony, The eeprom was used to create a 100*100 grid. Stored was either a 1 or a 0. Frequency: clear the 10Kb to 0 about every five minutes. At the start of the program is a 0.5s pause, to counter a quick loop upon reset with low battery power, etc. After clearing, I write to about 20 locations, with a 0.1s pause right before each, again to counter any errors in my programing which may result in a loop. The eeprom locations were well beyond the end of the program, 22700 to 32700, with the program being only 3Kb. Yes, eeprom is a last resort (usually). Here I use it to simplify design; the eeprom simulates ram, to be added later. I hope this is what you are asking... Thank you for your halp, Paul On Tue, 2 Jan 2001, Tony Brenke wrote: > you were talking about saving data to the eeprom. > > what kind of data and how often were you doing this. > if you were saving data in a fast loop you could have used the 100,000 > writes (about) in a short amount of time. > > I sugest you use the eeprom data save only for data you have to have > and can't do without. > > you might verywell have exceded the limit of your eeprom writes. > > --- "Paul J. Csonka" <> wrote: > > Hi Tony, > > > > I have looked at the archives and tried the various > > suggestions; before I even did so, I had left the bx24 in static foam > > overnight. > > I still have no communications, but perhaps it needs more time in > > the foam... > > > > Thank you for your help, > > Paul > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > if you look at the arcived about the bx-24, after many program > > changes > > > and downloads it builds up a static-kind of a change in the eeprom. > > > > > > the only known cure is to plug it into a static foam block for 24 > > > hours. > > > > > > the basic-x people are working on this. > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > Good morning, > > > > > > > > > > > > I have a bx24 which has gone from fully functional to functional > > > > without downloading capabilities. > > > > From one download to the next, I now recieve- > > > > > > > > "verify error, external eeprom" > > > > > > > > -on every download attempt of anything. > > > > The basicx still runs, from what I can tell. I just can't > > > > download anything new. > > > > > > > > Previously running is a program which writes to the internal > > > > eeprom, about 10Kb. There is a 0.1 second delay before each > > write; > > > > this > > > > is to make sure I don't get stuck in a fast loop while testing, > > and > > > > wear > > > > out eeprom locations via a programing mistake. > > > > So I don't THINK I have exceeded any write limits here. > > > > > > > > Are there any ideas as to what may have happened? > > > > > > > > Thank you for your time, > > > > Paul > > > > > > > > > > > > > > > > > > > > . > > > > pened? > > > > > > > > Thank you for your time, > > > > Paul > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > ===== > > > Tony Brenke > > > North Tacoma, WA > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > ===== > Tony Brenke > North Tacoma, WA > > __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

yes this is what I was asking. what you have more than likly done is ended the usable life of that eeprom. just a guess on my part(some quick math) 10k of data with .1 Second delay between each and .5 second delay at the begining...... 40 seconds to write 10k w/delay 100,000 cycle life. a guess of about 41 minutes of run time total before you ran out of the "extream use" 100K writes. if it is a bx-01 replace the eeprom and go again. if it is a bx-24......... --- "Paul J. Csonka" <> wrote: > Hi Tony, > > The eeprom was used to create a 100*100 grid. Stored was either a > 1 or a 0. > Frequency: clear the 10Kb to 0 about every five minutes. At the > start of the program is a 0.5s pause, to counter a quick loop upon > reset > with low battery power, etc. > After clearing, I write to about 20 locations, with a 0.1s pause > right before each, again to counter any errors in my programing which > may > result in a loop. > The eeprom locations were well beyond the end of the program, > 22700 to 32700, with the program being only 3Kb. > > Yes, eeprom is a last resort (usually). Here I use it to simplify > design; the eeprom simulates ram, to be added later. > > I hope this is what you are asking... > > Thank you for your halp, > Paul > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > you were talking about saving data to the eeprom. > > > > what kind of data and how often were you doing this. > > if you were saving data in a fast loop you could have used the > 100,000 > > writes (about) in a short amount of time. > > > > I sugest you use the eeprom data save only for data you have to > have > > and can't do without. > > > > you might verywell have exceded the limit of your eeprom writes. > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > Hi Tony, > > > > > > I have looked at the archives and tried the various > > > suggestions; before I even did so, I had left the bx24 in static > foam > > > overnight. > > > I still have no communications, but perhaps it needs more time > in > > > the foam... > > > > > > Thank you for your help, > > > Paul > > > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > > > if you look at the arcived about the bx-24, after many program > > > changes > > > > and downloads it builds up a static-kind of a change in the > eeprom. > > > > > > > > the only known cure is to plug it into a static foam block for > 24 > > > > hours. > > > > > > > > the basic-x people are working on this. > > > > > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > > Good morning, > > > > > > > > > > > > > > > I have a bx24 which has gone from fully functional to > functional > > > > > without downloading capabilities. > > > > > From one download to the next, I now recieve- > > > > > > > > > > "verify error, external eeprom" > > > > > > > > > > -on every download attempt of anything. > > > > > The basicx still runs, from what I can tell. I just can't > > > > > download anything new. > > > > > > > > > > Previously running is a program which writes to the internal > > > > > eeprom, about 10Kb. There is a 0.1 second delay before each > > > write; > > > > > this > > > > > is to make sure I don't get stuck in a fast loop while > testing, > > > and > > > > > wear > > > > > out eeprom locations via a programing mistake. > > > > > So I don't THINK I have exceeded any write limits here. > > > > > > > > > > Are there any ideas as to what may have happened? > > > > > > > > > > Thank you for your time, > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > pened? > > > > > > > > > > Thank you for your time, > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > ===== > > > > Tony Brenke > > > > North Tacoma, WA > > > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ===== > > Tony Brenke > > North Tacoma, WA > > > > __________________________________________________ > > > > > ===== Tony Brenke North Tacoma, WA __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi Tony, Thanks for your reply. I had thought I would be well under the 100k limit because of the following: The writes (clearing to zeros, writing with 0.1s delay) occured only once every ten minutes. I know the ten minutes is there, since the bx24 was turned off for these breaks. 1)ten minutes rest 2)clear 10kb to zero (one write per address, for 10000 locations) 3)twenty locations written to once 4) repeat step one I repeated this process about 15 times. Here are two more things I am not clear on: -When writing once to 100*100 points ("clearing"), the process did not take under a minute (40 seconds as you mention). It took quite a bit longer (maybe three minutes). -Since this is a bx24, I presume I can just solder a new eeprom in place of the old. Is this true? Thank you for your help, Paul On Tue, 2 Jan 2001, Tony Brenke wrote: > yes this is what I was asking. > what you have more than likly done is ended the usable life of that > eeprom. > > just a guess on my part(some quick math) > 10k of data with .1 Second delay between each and .5 second delay at > the begining...... > > 40 seconds to write 10k w/delay > 100,000 cycle life. > a guess of about 41 minutes of run time total before you ran out of the > "extream use" 100K writes. > > if it is a bx-01 replace the eeprom and go again. > if it is a bx-24......... > > --- "Paul J. Csonka" <> wrote: > > Hi Tony, > > > > The eeprom was used to create a 100*100 grid. Stored was either a > > 1 or a 0. > > Frequency: clear the 10Kb to 0 about every five minutes. At the > > start of the program is a 0.5s pause, to counter a quick loop upon > > reset > > with low battery power, etc. > > After clearing, I write to about 20 locations, with a 0.1s pause > > right before each, again to counter any errors in my programing which > > may > > result in a loop. > > The eeprom locations were well beyond the end of the program, > > 22700 to 32700, with the program being only 3Kb. > > > > Yes, eeprom is a last resort (usually). Here I use it to simplify > > design; the eeprom simulates ram, to be added later. > > > > I hope this is what you are asking... > > > > Thank you for your halp, > > Paul > > > > > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > you were talking about saving data to the eeprom. > > > > > > what kind of data and how often were you doing this. > > > if you were saving data in a fast loop you could have used the > > 100,000 > > > writes (about) in a short amount of time. > > > > > > I sugest you use the eeprom data save only for data you have to > > have > > > and can't do without. > > > > > > you might verywell have exceded the limit of your eeprom writes. > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > Hi Tony, > > > > > > > > I have looked at the archives and tried the various > > > > suggestions; before I even did so, I had left the bx24 in static > > foam > > > > overnight. > > > > I still have no communications, but perhaps it needs more time > > in > > > > the foam... > > > > > > > > Thank you for your help, > > > > Paul > > > > > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > > > > > if you look at the arcived about the bx-24, after many program > > > > changes > > > > > and downloads it builds up a static-kind of a change in the > > eeprom. > > > > > > > > > > the only known cure is to plug it into a static foam block for > > 24 > > > > > hours. > > > > > > > > > > the basic-x people are working on this. > > > > > > > > > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > > > Good morning, > > > > > > > > > > > > > > > > > > I have a bx24 which has gone from fully functional to > > functional > > > > > > without downloading capabilities. > > > > > > From one download to the next, I now recieve- > > > > > > > > > > > > "verify error, external eeprom" > > > > > > > > > > > > -on every download attempt of anything. > > > > > > The basicx still runs, from what I can tell. I just can't > > > > > > download anything new. > > > > > > > > > > > > Previously running is a program which writes to the internal > > > > > > eeprom, about 10Kb. There is a 0.1 second delay before each > > > > write; > > > > > > this > > > > > > is to make sure I don't get stuck in a fast loop while > > testing, > > > > and > > > > > > wear > > > > > > out eeprom locations via a programing mistake. > > > > > > So I don't THINK I have exceeded any write limits here. > > > > > > > > > > > > Are there any ideas as to what may have happened? > > > > > > > > > > > > Thank you for your time, > > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > pened? > > > > > > > > > > > > Thank you for your time, > > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > ===== > > > > > Tony Brenke > > > > > North Tacoma, WA > > > > > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ===== > > > Tony Brenke > > > North Tacoma, WA > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > ===== > Tony Brenke > North Tacoma, WA > > __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

ok, for the 100K of writes: each time the bx is programed (code downloaded) is one. your clear/write cycle is worth 2 one to clear all and another to write your data. each memory location/address on the eeprom has a 100k write limit. if you are only writing to the first 200 bytes, after the 100001 write you can start to expect faliers after that on the first 200. (math oops) acording to the doc's the eeprom is writen to in about 4mS/byte. so 4mS per 10k of data should take about 40 seconds to clear. so 4mS per "20 locations" should take about .08 seconds. add to that the time it takes for the code to do a loop (this depends on the way it is programed) About .01mS per line of code(acording to the docs) that is how I cam up with the idea of a 40 seconds write time. what I forgot to add was the 40 second "clear" write time. so about 40.08 seconds. time to clear = 40 seconds time to write 20 = .08 code run time .00001 seconds per line (average) --- "Paul J. Csonka" <> wrote: > Hi Tony, > > Thanks for your reply. > I had thought I would be well under the 100k limit because of the > following: > The writes (clearing to zeros, writing with 0.1s delay) occured > only once every ten minutes. I know the ten minutes is there, since > the > bx24 was turned off for these breaks. > 1)ten minutes rest > 2)clear 10kb to zero (one write per address, for 10000 locations) > 3)twenty locations written to once > 4) repeat step one > I repeated this process about 15 times. > > Here are two more things I am not clear on: > -When writing once to 100*100 points ("clearing"), the process did > not take under a minute (40 seconds as you mention). It took quite a > bit > longer (maybe three minutes). > -Since this is a bx24, I presume I can just solder a new eeprom in > place of the old. Is this true? > Thank you for your help, > Paul > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > yes this is what I was asking. > > what you have more than likly done is ended the usable life of that > > eeprom. > > > > just a guess on my part(some quick math) > > 10k of data with .1 Second delay between each and .5 second delay > at > > the begining...... > > > > 40 seconds to write 10k w/delay > > 100,000 cycle life. > > a guess of about 41 minutes of run time total before you ran out of > the > > "extream use" 100K writes. > > > > if it is a bx-01 replace the eeprom and go again. > > if it is a bx-24......... > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > Hi Tony, > > > > > > The eeprom was used to create a 100*100 grid. Stored was either > a > > > 1 or a 0. > > > Frequency: clear the 10Kb to 0 about every five minutes. At the > > > start of the program is a 0.5s pause, to counter a quick loop > upon > > > reset > > > with low battery power, etc. > > > After clearing, I write to about 20 locations, with a 0.1s pause > > > right before each, again to counter any errors in my programing > which > > > may > > > result in a loop. > > > The eeprom locations were well beyond the end of the program, > > > 22700 to 32700, with the program being only 3Kb. > > > > > > Yes, eeprom is a last resort (usually). Here I use it to > simplify > > > design; the eeprom simulates ram, to be added later. > > > > > > I hope this is what you are asking... > > > > > > Thank you for your halp, > > > Paul > > > > > > > > > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > > > you were talking about saving data to the eeprom. > > > > > > > > what kind of data and how often were you doing this. > > > > if you were saving data in a fast loop you could have used the > > > 100,000 > > > > writes (about) in a short amount of time. > > > > > > > > I sugest you use the eeprom data save only for data you have to > > > have > > > > and can't do without. > > > > > > > > you might verywell have exceded the limit of your eeprom > writes. > > > > > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > > Hi Tony, > > > > > > > > > > I have looked at the archives and tried the various > > > > > suggestions; before I even did so, I had left the bx24 in > static > > > foam > > > > > overnight. > > > > > I still have no communications, but perhaps it needs more > time > > > in > > > > > the foam... > > > > > > > > > > Thank you for your help, > > > > > Paul > > > > > > > > > > On Tue, 2 Jan 2001, Tony Brenke wrote: > > > > > > > > > > > if you look at the arcived about the bx-24, after many > program > > > > > changes > > > > > > and downloads it builds up a static-kind of a change in the > > > eeprom. > > > > > > > > > > > > the only known cure is to plug it into a static foam block > for > > > 24 > > > > > > hours. > > > > > > > > > > > > the basic-x people are working on this. > > > > > > > > > > > > > > > > > > > > > > > > --- "Paul J. Csonka" <> wrote: > > > > > > > Good morning, > > > > > > > > > > > > > > > > > > > > > I have a bx24 which has gone from fully functional to > > > functional > > > > > > > without downloading capabilities. > > > > > > > From one download to the next, I now recieve- > > > > > > > > > > > > > > "verify error, external eeprom" > > > > > > > > > > > > > > -on every download attempt of anything. > > > > > > > The basicx still runs, from what I can tell. I just > can't > > > > > > > download anything new. > > > > > > > > > > > > > > Previously running is a program which writes to the > internal > > > > > > > eeprom, about 10Kb. There is a 0.1 second delay before > each > > > > > write; > > > > > > > this > > > > > > > is to make sure I don't get stuck in a fast loop while > > > testing, > > > > > and > > > > > > > wear > > > > > > > out eeprom locations via a programing mistake. > > > > > > > So I don't THINK I have exceeded any write limits here. > > > > > > > > > > > > > > Are there any ideas as to what may have happened? > > > > > > > > > > > > > > Thank you for your time, > > > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > pened? > > > > > > > > > > > > > > Thank you for your time, > > > > > > > Paul > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > > > > > ===== > > > > > > Tony Brenke > > > > > > North Tacoma, WA > > > > > > > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ===== > > > > Tony Brenke > > > > North Tacoma, WA > > > > > > > > __________________________________________________ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ===== > > Tony Brenke > > North Tacoma, WA > > > > __________________________________________________ > > > > > > . > > > > > > > > > > > ===== > > Tony Brenke > > North Tacoma, WA > > > > __________________________________________________ > > > > > > . ===== Tony Brenke North Tacoma, WA __________________________________________________

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )