Pages: 1 [2]   Go Down
Author Topic: Memory overrun blows Arduino chip?  (Read 2487 times)
0 Members and 1 Guest are viewing this topic.
Dallas, TX USA
Offline Offline
Edison Member
*
Karma: 48
Posts: 2351
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

Oh the bootloader is gone.
Its been while since i've tested it and I haven't tested it on 1.0.1 but the IDE used to check
the code size and if it was larger than the size specified in the boards.txt file (upload.maximum.size) it wouldn't upload
the image.
The issue was (at least it used to work this way) was that if you used ISP, you could gain the  bootloader
space but the space is still "reserved" by the IDE as it always uses the size in upload.maximum.size
to check the image size against
before uploading because it doesn't know if the programmer being used is using ISP or a bootloader.

--- bill
Logged

Valencia, Spain
Online Online
Faraday Member
**
Karma: 121
Posts: 4601
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

Oh the bootloader is gone.
Its been while since i've tested it and I haven't tested it on 1.0.1 but the IDE used to check
the code size and if it was larger than the size specified in the boards.txt file (upload.maximum.size) it wouldn't upload
the image.
The issue was (at least it used to work this way) was that if you used ISP, you could gain the  bootloader
space but the space is still "reserved" by the IDE as it always uses the size in upload.maximum.size
to check the image size against
before uploading because it doesn't know if the programmer being used is using ISP or a bootloader.

Are the fuses normally set to protect the bootloader?
Logged

No, I don't answer questions sent in private messages...

SF Bay Area (USA)
Offline Offline
Tesla Member
***
Karma: 107
Posts: 6383
Strongly opinionated, but not official!
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

All ISP programming starts with a "Chip Erase" command that will wipe out the bootloader as well as an previous sketch.

I had a chip go dead that was recovered by re-installing the bootloader with a real STK-500.  I don't recall what it had been running...

So I think we're still at the stage where "people think that this has happened", "it shouldn't be possible for it to happen", and "no one has identified a probable cause or demonstration sketch."

It is interesting that it doesn't seem to happen as often as it used to.  All that's changed is the chip, the bootloader, the core libraries, and the IDE...  :-)
Logged

Brisbane, Australia
Offline Offline
Edison Member
*
Karma: 29
Posts: 1074
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

All that's changed is the chip, the bootloader, the core libraries, and the IDE...  :-)
That cracked me up, thanks smiley

Conversely to the apparent frequency of reports, the user base would have expanded significantly at the same time too...

Geoff
Logged

"There is no problem so bad you can't make it worse"
- retired astronaut Chris Hadfield

Pages: 1 [2]   Go Up
Jump to: