-
Notifications
You must be signed in to change notification settings - Fork 0
Boot ROM Loader
When the Boot ROM loader loads an eboot.bin
with multiple segments, the segment(s) preceding the last segment may need to be align filled to 16 bytes. Otherwise, a message similar to ho 0 tail 12 room 4
will appear in the boot message log.
This can be done through the eboot.ld
file. Add something like:
.text : ALIGN(4)
{
...
. = ALIGN (16); /* Ensure 16-byte alignment to keep Boot ROM loader happy with multi-segment eboot */
} >iram1_0_seg :iram1_0_phdr
That said, while this will get rid of messages like ho 0 tail 12 room 4
in the boot message log. It is not clear to me, that it is an issue that needs to be fixed. I cannot find any details on that log message. And, I have found boot message logs posted where it occurs and the boot is considered a success.
In reading through some posts I found some boot message logs that did not have the ho 0 tail 12 room 4
message and each segment was not 16 byte filled. At least for the one, I saw the sum of all the segments together was 16-bytes aligned.
They added a multi-segment boot loader in the Arduino ESP8266 pre 3.0 core, so this does not appear to be an issue or real concern
- Keeping the Lights On - how to manage GPIO state across reboots and crashes
- Boot fails when SPI Bus used
- GPIO Drive Strength and Ringing
- LDO Regulators WIP
- ESP8266 Power Considerations This is only a rough outline, needs a lot of development.
- Upgrading Flash Chips, QIO, and DIO
- Dodgy Extra 2K of DRAM or CONT - WIP
- WDTracks - Print last call before WDT
- 5V Tolerant I/O?
Arduino IDE specific
Misc.
- Exception Causes
- ESP8266 will not boot
- Stacks sys and cont
- WIP Boot ROM and SDK Notes
- Multi-segment Boot ROM Loader, notes
- Cache_Read_Enable How to turn off and on instruction cache execution.