Skip to content
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.

Sign up for GitHub

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

Jump to bottom

run-avrdude burns bootloader twice #11

Closed
will127534 opened this issue Feb 15, 2016 · 1 comment
Closed

run-avrdude burns bootloader twice #11

will127534 opened this issue Feb 15, 2016 · 1 comment

Comments

@will127534
Copy link

as title,the hex file upload by Arduino IDE already combine the bootloader with code
so don't need to burn bootloader first, also avrdude doesn't clear the chip fist.

So the parameter for avrdude can change to
avrdude -c linuxgpio -C /etc/avrdude.conf -p m32u4 -e -v -Uflash:w:$1 $2
@blogic
Copy link
Contributor

blogic commented Feb 17, 2016

please send a documented PR with the appropriate patch

@blogic blogic closed this as completed Feb 17, 2016
pablosun added a commit to pablosun/linkit-smart-7688-feed that referenced this issue Feb 18, 2016
@pablosun
Fix sketch upload script
472282e 
The sketch upload script (run-avrdude) burns bootloader and the combined binary file. The hex file upload by Arduino IDE already combine the bootloader with code so don't need to burn bootloader first, also avrdude doesn't clear the chip fist and in some cases this will cause verification fail.

So the parameter for avrdude can simply change to `avrdude -c linuxgpio -C /etc/avrdude.conf -p m32u4 -e -v -Uflash:w:$1 $2`

This is follow-up of  MediaTek-Labs#11.
@pablosun pablosun mentioned this issue Feb 18, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@blogic @will127534