esp-open-rtos: ESP-12F stuck.

Hi everyone, thanks for your work firstly.

I have a ESP-12F module. I flashed some of the examples to try out but it always stops at

rBoot v1.4.0 - richardaburton@gmail.com
Flash Size:   32 Mbit
Flash Mode:   QIO
Flash Speed:  40 MHz
rBoot Option: Big flash
rBoot Option: RTC data

Booting rom 0.

I have changed parameters.mk for 4 MB flash size. I did not change common.mk by the way.

Thanks

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (11 by maintainers)

Most upvoted comments

Submitted a PR for rboot https://github.com/raburton/rboot/pull/37 and a PR to update esp-open-rtos to the current rboot master https://github.com/SuperHouse/esp-open-rtos/pull/617 and a little more support in esp-open-rtos https://github.com/SuperHouse/esp-open-rtos/pull/616

Could I ask which flash tool is causing the problems, and does the current esptool not work for some configurations? Just not clear from the discussion why the modified config.bin is even necessary?

ourairquality on Apr 25, 2018

@chenli2015 Even with following your instruction, it not working 😕 Do I do something wrong?

apiel on Apr 27, 2018

What do you means? How can I do this?

Thanks for your help 😉

On Tue, 24 Apr 2018, 03:19 chenli2015, notifications@github.com wrote:

@apiel https://github.com/apiel Please try my config.bin setting: e1 01 00 00 00 01 00 00 00 00 20 00 …(all 0s) Not flash blank_config at 0x1000

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SuperHouse/esp-open-rtos/issues/588#issuecomment-383772028, or mute the thread https://github.com/notifications/unsubscribe-auth/AFmeLm-w6z_qbQ3CSHhVwCpnBnUgdzY0ks5trn2NgaJpZM4SjYwS .

apiel on Apr 24, 2018

@apiel Please try my config.bin setting: e1 01 00 00 00 01 00 00 00 00 20 00 …(all 0s) Not flash blank_config at 0x1000

chenli2015 on Apr 24, 2018

I tried to do exactly what is mentioned by @chenli2015 without success

I flash it with: esptool.py -p /dev/ttyUSB0 --baud 115200 write_flash -fs 32m -fm dio -ff 40m 0x0 …/…/bootloader/firmware/rboot.bin 0x1000 …/…/bootloader/firmware_prebuilt/blank_config.bin 0x2000 ./firmware/blink.bin

Any more idea?

apiel on Apr 23, 2018

I meet the same problem with default rboot.bin. But I use espressif’s official download tool. After several hours debug, the problem seems to be resolved!

I add some code to rboot.c to support new flash size flag for 5 and 6, so rboot could recognize the flash size.
And then print the boot rom address which is got from the config.bin section of the flash, so we could determine if the boot rom address is correct.
rebuild the bootloader.
flash bootloader.bin, config.bin, you-app.bin with the following config: flash size 32M, spi mode dio, …
resolved!

rboot.c at line 281: // print and get flash size ets_printf("Flash Size: "); flag = header->flags2 >> 4; if (flag == 0) { ets_printf(“4 Mbit\r\n”); flashsize = 0x80000; } else if (flag == 1) { ets_printf(“2 Mbit\r\n”); flashsize = 0x40000; } else if (flag == 2) { ets_printf(“8 Mbit\r\n”); flashsize = 0x100000; } else if (flag == 3 || flag == 5) { ets_printf(“16 Mbit\r\n”); #ifdef BOOT_BIG_FLASH flashsize = 0x200000; #else flashsize = 0x100000; // limit to 8Mbit #endif } else if (flag == 4 || flag == 6) { ets_printf(“32 Mbit\r\n”); #ifdef BOOT_BIG_FLASH flashsize = 0x400000; #else flashsize = 0x100000; // limit to 8Mbit #endif } else { ets_printf(“unknown\r\n”); // assume at least 4mbit flashsize = 0x80000; }

line 451: ets_printf(“Rom %d at %x is bad.\r\n”, romToBoot, romconf->roms[romToBoot]); line 490: ets_printf(“Booting rom %d from %x, run at ram %x.\r\n”, romToBoot, romconf->roms[romToBoot], runAddr);

config.bin setting: e1 01 00 00 00 01 00 00 00 00 20 00 …(all 0s)

chenli2015 on Mar 18, 2018