MTC4BT not booting

[Martin List-Petersen]

Hi,

I tried to get started with Mattzobricks, but I’ve ran into a few stumbling blocks.

First of all, PlatformIO refuses the code.

It is looking for a [my_common] section in platformio.ini to even compile the code.

I took the [common] section and copied that into a [my_common] section. After that, it compiles. This is PlatformIO Core 6.1.9, Home 3.4.4

I am using the AZDelivery ESP32 NodeMCU for this.

When the board boots after flashing it with MTC4BT, all it says is:
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:2
load:0x3fff0030,len:7672
load:0x40078000,len:16432
load:0x40080400,len:3704
entry 0x4008067c
I (27) boot: ESP-IDF qa-test-v4.3.3-20220423 2nd stage bootloader
I (27) boot: compile time 11:11:52
I (28) boot: chip revision: 3
I (31) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (38) boot.esp32: SPI Speed : 40MHz
I (43) boot.esp32: SPI Mode : DIO
I (48) boot.esp32: SPI Flash Size : 4MB
I (52) boot: Enabling RNG early entropy source…
I (58) boot: Partition Table:
I (61) boot: ## Label Usage Type ST Offset Length
I (68) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (76) boot: 1 otadata OTA data 01 00 00010000 00002000
I (83) boot: 2 nvs WiFi data 01 02 00012000 0000e000
I (91) boot: 3 at_customize unknown 40 00 00020000 000e0000
I (98) boot: 4 ota_0 OTA app 00 10 00100000 00180000
I (106) boot: 5 ota_1 OTA app 00 11 00280000 00180000
I (113) boot: End of partition table
I (118) boot_comm: chip revision: 3, min. application chip revision: 0
I (125) esp_image: segment 0: paddr=00100020 vaddr=3f400020 size=295d8h (169432) map
I (195) esp_image: segment 1: paddr=00129600 vaddr=3ffbdb60 size=04474h ( 17524) load
I (202) esp_image: segment 2: paddr=0012da7c vaddr=40080000 size=0259ch ( 9628) load
I (206) esp_image: segment 3: paddr=00130020 vaddr=400d0020 size=111630h (111979 2) map
I (614) esp_image: segment 4: paddr=00241658 vaddr=4008259c size=1b568h (111976) load
I (660) esp_image: segment 5: paddr=0025cbc8 vaddr=400c0000 size=00064h ( 100) load
I (661) esp_image: segment 6: paddr=0025cc34 vaddr=50000000 size=00010h ( 16) load
I (681) boot: Loaded app from partition at offset 0x100000
I (681) boot: Disabling RNG early entropy source…
module_name:WROOM-32
max tx power=78,ret=0
2.4.0

And that’s the end of it.

Any suggestions, what’s gone wrong here ?

/M

[Martin List-Petersen]

Nevermind. I figured out, where I went wrong: I only uploaded the configuration, but not the actual image to the ESP32.

The issue with PlatformIO requiring the [my_common] section still applies though.

[Hilbert B]

Hi Martin,

There should be my_platformio.ini.example I assume you renamed/copied it to my_platformio.ini

And I see that there is missing a [my_common] section, we added this because we saw that platformio wasn’t merging variables as expected. This section could be empty:
[my_common]
build_flags =

(I did not test this) or otherwise you can try
[my_common]
build_flags = -DFOO

This makes sure the section is defined, the -DFOO does not influence the build, just makes platformio happy.

I openend a ticket, not sure how fast we pick this one up, because of summer and being more outside, than behind the screen 😉

Hilbert

[Thorsten]

You only have to Change 2 things.
1. the folder data_example in data
there, fill out the two files

2. in platform.ini under monitor_speed place this: upload_com_port = COM5
for me its COM5 it coud be whatever you have.

Then click the Platformio Icon on the left side ind vscode.
for me its then az-delivery-devkit-v4, in General click Build,
After that, “Upload and Monitor”
After that, under Platform, “UploadFilesystem Image”.

Thats all

[Author]

Posts