Factory app parition not bootable.

docmur
Posts: 5
Joined: Sat Feb 17, 2018 10:16 pm

Factory app parition not bootable.

Postby docmur » Wed Mar 21, 2018 2:03 am

Hey Guys

I designed an ESP32 board based around the ESP-WROOM-32 module. When I upload the example blink code to my board and run make monitor, it works fine, but when I upload my own project, it flashes perfectly fine, but when I run make monitor I get:

I (296) esp_image: segment 6: paddr=0x000a9768 vaddr=0x400c0000 size=0x00000 ( 0) load
E (296) esp_image: Checksum failed. Calculated 0xa6 read 0x6
E (300) boot: Factory app partition is not bootable
E (306) boot: No bootable app partitions in the partition table
user code done

My project works on my ESP-WROOM32 dev board, what should I check to try and get my project to boot up and run?

Thanks
D

chegewara
Posts: 2172
Joined: Wed Jun 14, 2017 9:00 pm

Re: Factory app parition not bootable.

Postby chegewara » Wed Mar 21, 2018 6:42 am

I see two possible issues. One is that during flashing some error occured and there is error

Code: Select all

E (296) esp_image: Checksum failed. Calculated 0xa6 read 0x6
Try to flash your app one more time.

Another issue is that your app size is larger than partition size (but most likely it should have show more error messages with info about this issue).

It is also possible that some other issue occured that i cant predict because my lack of knowledge.

User avatar
Gfast2
Posts: 182
Joined: Fri Aug 11, 2017 1:52 am

Re: Factory app parition not bootable.

Postby Gfast2 » Wed Mar 21, 2018 3:04 pm

try "make size" to check your app size
try "make erase_flash" to format the whole flash.

Cheers

Gfast2

docmur
Posts: 5
Joined: Sat Feb 17, 2018 10:16 pm

Re: Factory app parition not bootable.

Postby docmur » Thu Mar 22, 2018 12:47 am

Thanks for the suggestions:

Make Size returns:

Total sizes:
DRAM .data size: 11092 bytes
DRAM .bss size: 26944 bytes
Used static DRAM: 38036 bytes ( 142700 available, 21.0% used)
Used static IRAM: 71832 bytes ( 59240 available, 54.8% used)
Flash code: 465497 bytes
Flash rodata: 80080 bytes
Total image size:~ 628501 bytes (.bin may be padded larger)

and running make erase_flash then make flash didn't seem to help. Should I try using a custom partition table as the first reply pointed to?

Thanks
D

docmur
Posts: 5
Joined: Sat Feb 17, 2018 10:16 pm

Re: Factory app parition not bootable.

Postby docmur » Thu Mar 22, 2018 2:44 am

Hey Guys

I updated the toolchain and grabbed an updated version of esp-idf, I'm still running into the same issue, here is a full listing from terminal.

Code: Select all

esptool.py v2.3.1
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)...
esptool.py v2.3.1
Connecting....
Chip is ESP32D0WDQ6 (revision 0)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 8MB
Compressed 18624 bytes to 10984...
Wrote 18624 bytes (10984 compressed) at 0x00001000 in 1.0 seconds (effective 152.6 kbit/s)...
Hash of data verified.
Compressed 634304 bytes to 396178...
Wrote 634304 bytes (396178 compressed) at 0x00010000 in 35.2 seconds (effective 144.1 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 1508.2 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ent 1: p�ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:5028
load:0x40078000,len:0
load:0x40078000,len:13500
entry 0x40078f5c
I (29) boot: ESP-IDF v3.1-dev-562-g84788230-dirty 2nd stage bootloader
I (29) boot: compile time 22:40:48
I (39) boot: Enabling RNG early entropy source...
I (39) boot: SPI Speed      : 80MHz
I (39) boot: SPI Mode       : DIO
I (43) boot: SPI Flash Size : 8MB
I (47) boot: Partition Table:
I (51) boot: ## Label            Usage          Type ST Offset   Length
I (58) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (66) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (73) boot:  2 factory          factory app      00 00 00010000 00100000
I (81) boot: End of partition table
I (85) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x13be0 ( 80864) map
I (117) esp_image: segment 1: paddr=0x00023c08 vaddr=0x3ffb0000 size=0x02bc0 ( 11200) load
I (121) esp_image: segment 2: paddr=0x000267d0 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at /home/andrew/ESP/esp-idf/components/freertos/./xtensa_vectors.S:1685

I (124) esp_image: segment 3: paddr=0x00026bd8 vaddr=0x40080400 size=0x09438 ( 37944) load
I (146) esp_image: segment 4: paddr=0x00030018 vaddr=0x400d0018 size=0x75b8c (482188) map
0x400d0018: _stext at ??:?

I (285) esp_image: segment 5: paddr=0x000a5bac vaddr=0x40089838 size=0x051e4 ( 20964) load
0x40089838: xQueueGenericSend at /home/andrew/ESP/esp-idf/components/freertos/./queue.c:2037

I (293) esp_image: segment 6: paddr=0x000aad98 vaddr=0x400c0000 size=0x00000 (     0) load
E (293) esp_image: Checksum failed. Calculated 0x72 read 0xe
E (298) boot: Factory app partition is not bootable
E (304) boot: No bootable app partitions in the partition table
Hopefully this helps, I also tried to the hello world example and I'm running into the same issue.

Thanks
D

Daniel
Posts: 28
Joined: Tue Jan 09, 2018 12:55 pm

Re: Factory app parition not bootable.

Postby Daniel » Thu Mar 22, 2018 3:39 am

docmur wrote:Hey Guys

I updated the toolchain and grabbed an updated version of esp-idf, I'm still running into the same issue, here is a full listing from terminal.

Code: Select all

esptool.py v2.3.1
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)...
esptool.py v2.3.1
Connecting....
Chip is ESP32D0WDQ6 (revision 0)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 8MB
Compressed 18624 bytes to 10984...
Wrote 18624 bytes (10984 compressed) at 0x00001000 in 1.0 seconds (effective 152.6 kbit/s)...
Hash of data verified.
Compressed 634304 bytes to 396178...
Wrote 634304 bytes (396178 compressed) at 0x00010000 in 35.2 seconds (effective 144.1 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 1508.2 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ent 1: p�ets Jun  8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:5028
load:0x40078000,len:0
load:0x40078000,len:13500
entry 0x40078f5c
I (29) boot: ESP-IDF v3.1-dev-562-g84788230-dirty 2nd stage bootloader
I (29) boot: compile time 22:40:48
I (39) boot: Enabling RNG early entropy source...
I (39) boot: SPI Speed      : 80MHz
I (39) boot: SPI Mode       : DIO
I (43) boot: SPI Flash Size : 8MB
I (47) boot: Partition Table:
I (51) boot: ## Label            Usage          Type ST Offset   Length
I (58) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (66) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (73) boot:  2 factory          factory app      00 00 00010000 00100000
I (81) boot: End of partition table
I (85) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x13be0 ( 80864) map
I (117) esp_image: segment 1: paddr=0x00023c08 vaddr=0x3ffb0000 size=0x02bc0 ( 11200) load
I (121) esp_image: segment 2: paddr=0x000267d0 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at /home/andrew/ESP/esp-idf/components/freertos/./xtensa_vectors.S:1685

I (124) esp_image: segment 3: paddr=0x00026bd8 vaddr=0x40080400 size=0x09438 ( 37944) load
I (146) esp_image: segment 4: paddr=0x00030018 vaddr=0x400d0018 size=0x75b8c (482188) map
0x400d0018: _stext at ??:?

I (285) esp_image: segment 5: paddr=0x000a5bac vaddr=0x40089838 size=0x051e4 ( 20964) load
0x40089838: xQueueGenericSend at /home/andrew/ESP/esp-idf/components/freertos/./queue.c:2037

I (293) esp_image: segment 6: paddr=0x000aad98 vaddr=0x400c0000 size=0x00000 (     0) load
E (293) esp_image: Checksum failed. Calculated 0x72 read 0xe
E (298) boot: Factory app partition is not bootable
E (304) boot: No bootable app partitions in the partition table
Hopefully this helps, I also tried to the hello world example and I'm running into the same issue.

Thanks
D


Hi,Maybe you should change another wire or another power,because it can not work normally.

ESP_Angus
Posts: 2344
Joined: Sun May 08, 2016 4:11 am

Re: Factory app parition not bootable.

Postby ESP_Angus » Thu Mar 22, 2018 6:25 am

The log output and all of the flashing offets look correct. Also, the fact you can run the same project on a development board points to a hardware issue.

Check the GPIOs that your design is using and that none of these overlap with GPIOs connected to the module's internal SPI flash pins (GPIOs 6-11 inclusive, there's a note in the ESP-WROOM32 datasheet about this.)

Try turning down the SPI flash frequency in menuconfig (Serial Flasher Settings) from 80MHz to 40MHz,see if this makes any difference.

docmur
Posts: 5
Joined: Sat Feb 17, 2018 10:16 pm

Re: Factory app parition not bootable.

Postby docmur » Sun Mar 25, 2018 1:00 am

Amazingly, it was a solder problem on the TX line. I installed a 0 Ohm resistor across RX and TX, and apparently the one side of the TX resistor was iffy, not sure how and it was generating the issue. I swapped the resistor and we're back in the game :)

Thanks for everyone's help!

Who is online

Users browsing this forum: No registered users and 91 guests