October 22 firmware self-compilation

All ESP8266 boards running MicroPython.
Official boards are the Adafruit Huzzah and Feather boards.
Target audience: MicroPython users with an ESP8266 board.
Post Reply
cpr
Posts: 11
Joined: Thu Mar 03, 2016 4:56 pm
Location: LDK, OWL @ .de

October 22 firmware self-compilation

Post by cpr » Sat Oct 22, 2016 7:18 am

Hi there,

this is how I got it to work with the vagrant file from https://learn.adafruit.com/building-and ... h-firmware .

I followed it today and yesterday with _some_ success. There is a switch in pfalcons esp-open-sdk to SDK v2.0 https://github.com/pfalcon/esp-open-sdk ... d5eb785391
Also see http://forum.micropython.org/viewtopic. ... 689#p14850

I got .text' will not fit in regioniram1_0_seg'
which I could not solve with esptool.py --port /dev/ttyUSB0 --baud 115200 write_flash --flash_size=8m -fm dio 0x00000 /home/cpr/ESP8266/esp8266-micropython-vagrant/firmware-combined.bin 0x3fc000 /home/cpr/ESP8266/esp8266-micropython-vagrant/esp_init_data_default.bin --verify and writing that esp_init_data_default.bin to its address as per https://nodemcu.readthedocs.io/en/maste ... x-firmware

BUT the trick was to flash the latest micropython port!
I just downloaded the latest daily build from https://micropython.org/download#esp8266 , flashed that and re-flashed my self-compiled version.

That made it work for a first-timer ESP flasher.

User avatar
yeti
Posts: 8
Joined: Fri Jul 03, 2015 1:10 am

Re: October 22 firmware self-compilation

Post by yeti » Sat Oct 22, 2016 9:52 am

cpr wrote:I just downloaded the latest daily build from https://micropython.org/download#esp8266 , flashed that and re-flashed my self-compiled version.

That made it work for a first-timer ESP flasher.
How/why did that fix the '.text will not fit in region iram1_0_seg' problem?
I have a natural instinct for science. — D.J. Trump
"Don't we all wait for SOMETHING-ELSE-1.0?" — yeti
"Stay OmmmMMMmmmPtimistic!" — yeti

Post Reply