-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chipKIT Uno32 max upload size 64000 in boards.txt #19
Comments
What are the correct sizes? Also, has this accounted for the On Fri, May 13, 2011 at 12:33 PM, nkcelectronics
President |
The EEPROM on the Arduino Uno is 1K, so that should be the reserved memory for EEPROM. Is EEPROM emulated on the PIC32? If the data is not stored, what happens with sketches that use the EEPROM? Shouldn't the boards include a small EEPROM chip? If you need to reserve EEPROM, then available upload size should be 127000 (127K), not 64000 as defined now |
The first proto of the uno32 was a 64k chip, I did not remember to Mark On 5/13/11 12:33 PM, nkcelectronics wrote:
|
I think the linker now reservers 16k of memory for eeprom. Should that be subtracted as well? |
Rick I had specifically asked Jason to NOT modify the linker script to deal If he is to modify it, it MUST be 4K, the bootloader knows to leave the Mark On 5/13/11 1:43 PM, ricklon wrote:
|
In the Arduino with the AVR chip it is the Flash size - bootloader size, because EEPROM is integrated. In the chipKIT, the bootloader is in a separate 12K, so if the linker reserves 16K for EEPROM, then the available size for uploads should be 128000 - 16000 = 112000. Why the linker reserves 16K for EEPROM, if the microcontroller doesn't have any? This parameter is important because it is reported by the Arduino IDE after compiling the sketch (for users to verify if they are running out of space or not) |
There was some conflict between Gene and Mark's requests. Gene requested that the MAX32 linker script reserve 16K for eeprom emulation so that they could implement wear leveling in order to emulate 4k of eeprom. This is because flash endurance is lower than eeprom endurance. He requested that the UNO32 reserve only 4K. His email may have gotten buried in the noise because nobody else responded to it... |
If reserved space for Uno32 is 4K, then available size in boards.txt should be 124000. Now is 112000 (128K - 16K). |
Why the max upload size is set to 64000 instead of 128000 in boards.txt for the Uno32 board?
The text was updated successfully, but these errors were encountered: