-
-
Notifications
You must be signed in to change notification settings - Fork 799
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
avrdude verification error when uploading to Panstamp AVR #247
Comments
Could I ask you to try extra_script with this content: from os.path import join
from SCons.Script import DefaultEnvironment
env = DefaultEnvironment()
env.Replace(
MYUPLOADERFLAGS=[
"-v",
"-p", "$BOARD_MCU",
"-C",
'"%s"' % join("$PIOPACKAGES_DIR", "tool-avrdude", "avrdude.conf"),
"-c", "$UPLOAD_PROTOCOL",
"-b", "$UPLOAD_SPEED"
],
UPLOADHEXCMD='"$UPLOADER" $MYUPLOADERFLAGS -U flash:w:$SOURCES:i'
) Has it helped you? |
Wow, that was fast, thank you 😄 I had to add |
Have you tried this project with original Arduino IDE with panStamp core? See https://github.com/panStamp/panstamp/wiki/Installing-panStamp-cores-and-libraries-for-Arduino |
Thanks for the suggestion. Meanwhile, I managed to install the IDE and get
the firmware compiling which required quite some changes to source files
(which in fact helped reminding me several times why I prefer PlatformIO so
much over the arduino IDE). In the end, the code compiled and the binary
file was even larger compared to that compiled with platformio (Even though
I'm quite positive I'm compiling in the same set of features). There is no
error output regarding the size of the binary but the IDE does state a
warning that due to the large size, stability problems are to be expected.
I didn't upload this to the panstamp yet to check the upload process and if
it is running afterwards, and it may take some more time before I can get
my hands on the hardware and do so. But I'll keep you updated.
What I did learn trying to find out about related problems and possible
solutions, it that there are various bootloaders around with varying size
and that the bootloader lives in the upper memory region. Maybe in my
panstamp it starts at address 0x7000? Which would mean that the topmost 4k
are reserved for the bootloader? I'll have to read some more.
|
Have you resolved this issue? |
I just hooked up the board to arduino IDE and I get the very same error
So clearly it is not a problem of PIO per se. Thank you for your support in figuring this out! |
@gandy92 thanks for the report! We've released 2.2.1 today 😄 Don't forget to upgrade. |
Thanks for the heads up, I will update and try it out right after having removed that other IDE 😉 |
I am working on a firmware that makes use almost all of Panstamp AVR resources. I have a working set of features that compiles with the result
and uploads with the message:
This firmware successfully runs on the Panstamp AVR board.
However, when I compile in one more feature, I get:
which IMHO suggests that it should fit in the Panstamp memory.
However, when I try to upload this, I get:
This result does not depend on the additional feature per se, I can deactivate other features and get working uploads as long as I do not exceed a certain program or data memory size. Every time the upload fails, the error occurs at byte 0x7000.
Is it possible the memory sizes are not correctly configured for the Panstamp AVR board? Or is there something wrong with the upload process?
I was having this problem for some time now and just updated to PIO 2.2.0 to verify the problem is still there.
The text was updated successfully, but these errors were encountered: