Skip to content

optiboot_x: How are different entry conditions specified for the precompiled hex? #971

Answered by SpenceKonde
xieliwei asked this question in Q&A
Discussion options

You must be logged in to vote

Changes checked in. Can anyone test some of the bootloaders and make sure I didn't break anything? I see no red flags in the assembly listings, except that almost every byte is different indicating that I did something that caused the compiler to make a decision with wide-ranging consequences for the form of the emitted hex file

boot_opt.h removed because it was unused, because boot.h was unused, because boot.h only applies to classic AVRs

Replies: 3 comments 4 replies

Comment options

You must be logged in to vote
2 replies
@xieliwei
Comment options

@xieliwei
Comment options

Comment options

You must be logged in to vote
2 replies
@xieliwei
Comment options

@SpenceKonde
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by xieliwei
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants