AVR C Runtime Library - Bugs: bug #45701, redundant stack initialization in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #45701: redundant stack initialization in crt1.o
Submitter: | None | ||
Submitted: | Wed 05 Aug 2015 04:03:13 PM UTC | ||
Category: | Library | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | Startup code |
Status: | None | Percent Complete: | 0% |
Assigned to: | None | Originator Email: | -email is unavailable- |
Open/Closed: | Open | Release: | 1.8.0 |
Fixed Release: | None |
Mon 18 Jul 2016 07:14:15 PM UTC, comment #2: |
Anonymous |
Mon 11 Jul 2016 07:16:05 PM UTC, comment #1: The current startup code allows a custom value for SP init by defining symbol __stack , for example: -Wl,--defsym,__stack=0x123 or by defining that symbol in a custom linker description file.
|
Georg-Johann Lay <gjlayde> |
Wed 05 Aug 2015 04:03:13 PM UTC, original submission:
It appears crt1.o always initializes the stack and clears SREG, even for modern AVRs that don't require it.
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Acutally a bootloader just jumping to 0x0 would not only be uncommon, it would be shitty coding. All the bootloaders I have written ensure the registers are in their reset state before jumping to the start of the application code. Another option is to use a WDT reset like Optiboot.