Closed n07-5l4y3r closed 4 years ago
This...does not make any sense at all.
NodeMCU ESP32 built with Docker provided by frightanic.com
branch: dev-esp32
commit: f4887bf134235c05e6c9b2efad370e6d5018f91a
SSL: true
modules: -
built on nodemcu-build.com provided by frightanic.com
branch: dev-esp32
commit: dd3b217df201fde00fcf84be1d485d555d433bed
SSL: false
modules: file,gpio,node,pulsecnt,tmr,uart
build 2020-09-15-17-10-55 powered by Lua 5.1.4 on ESP-IDF v3.3-beta1-1391-g9e70825d1 on SDK IDF
You either flash the firmware from the cloud builder - what you did according to the screen shot - or the one you built yourself with Docker - which you also seem to have done. I don't understand how you could get a mix therefore? And what's with ChilliPeppr?
Here's what I would do:
If all is well then continue by building a new firmware with the modules you really need and repeat.
The firmware used in those screenshots is one from the cloud-builder. I havent attempted building it myself.
The script in the end shall have just one ability: counting a single channel and returning this measurement through rs232.
Therefore no WiFi connection is needed as USB/Serial via UART is enough for this case.
So I obviously need the pulsecnt
module: which seems undefined according this screen tho, which right now is my only problem.
And what's with ChilliPeppr? Thats just the "IDE" im using for uploading/executing the script.
So again what I did so far:
pulsecnt == nil
I am requesting a build without pulsecnt right now which will prolly execute and run just as good but obviously will also not have the pulse counter module. (next comment upcomming)
As promised (and expected):
Next Comment will be the exact same but with the "Pulse Counter" module.
same problem sadly 😞
I'm a little less confused now. This hit me out of the blue, sorry.
The weird boot message appears to be a bug - never seen anything like that. I'm tracking this at https://github.com/marcelstoer/nodemcu-custom-build/issues/39.
The missing pulse counter module is related to an upstream change in the firmware Kconfig that wasn't properly reflected in the cloud builder. This is already fixed.
So today I tryed my best to get the Pulse Counter working on my ESP32 but encountered some quite unique issues.
Output Log:
Full Log
I also find it interesting that the chip is doing something with wifi but the firmware shouldn't include this module. (Re-Requesting build's also didn't do the trick) ``` node.restart() > node.restart() ets Jun 8 2016 00:22:57 rst:0xc (SW_CPU_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:0x3fff0018,len:4 load:0x3fff001c,len:6736 ho 0 tail 12 room 4 load:0x40078000,len:11116 load:0x40080400,len:5940 entry 0x40080700 [0;32mI (73) boot: Chip Revision: 1[0m [0;32mI (73) boot_comm: chip revision: 1, min. bootloader chip revision: 0[0m [0;32mI (41) boot: ESP-IDF v3.3-beta2-887-g9e70825d1 2nd stage bootloader[0m [0;32mI (41) boot: compile time 17:12:49[0m [0;32mI (41) boot: Enabling RNG early entropy source...[0m [0;32mI (48) boot: SPI Speed : 40MHz[0m [0;32mI (52) boot: SPI Mode : DIO[0m [0;32mI (56) boot: SPI Flash Size : 4MB[0m [0;32mI (60) boot: Partition Table:[0m [0;32mI (64) boot: ## Label Usage Type ST Offset Length[0m [0;32mI (71) boot: 0 nvs WiFi data 01 02 00009000 00006000[0m [0;32mI (78) boot: 1 phy_init RF data 01 01 0000f000 00001000[0m [0;32mI (86) boot: 2 factory factory app 00 00 00010000 00180000[0m [0;32mI (93) boot: 3 lfs unknown c2 01 00190000 00010000[0m [0;32mI (101) boot: 4 nodemcuspiffs unknown c2 00 001a0000 00070000[0m [0;32mI (108) boot: End of partition table[0m [0;32mI (113) boot_comm: chip revision: 1, min. application chip revision: 0[0m [0;32mI (120) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x24c30 (150576) map[0m [0;32mI (180) esp_image: segment 1: paddr=0x00034c58 vaddr=0x3ffb0000 size=0x035e8 ( 13800) load[0m [0;32mI (185) esp_image: segment 2: paddr=0x00038248 vaddr=0x40080000 size=0x00400 ( 1024) load[0m [0;32mI (187) esp_image: segment 3: paddr=0x00038650 vaddr=0x40080400 size=0x079c0 ( 31168) load[0m [0;32mI (207) esp_image: segment 4: paddr=0x00040018 vaddr=0x400d0018 size=0xa0478 (656504) map[0m [0;32mI (430) esp_image: segment 5: paddr=0x000e0498 vaddr=0x40087dc0 size=0x0d5bc ( 54716) load[0m [0;32mI (451) esp_image: segment 6: paddr=0x000eda5c vaddr=0x400c0000 size=0x00064 ( 100) load[0m [0;32mI (465) boot: Loaded app from partition at offset 0x10000[0m [0;32mI (465) boot: Disabling RNG early entropy source...[0m [0;32mI (465) cpu_start: Pro cpu up.[0m [0;32mI (469) cpu_start: Application information:[0m [0;32mI (474) cpu_start: Project name: NodeMCU[0m [0;32mI (479) cpu_start: App version: dd3b217-dirty[0m [0;32mI (484) cpu_start: Compile time: Sep 15 2020 17:12:52[0m [0;32mI (490) cpu_start: ELF file SHA256: 8de9dabc96a3e962...[0m [0;32mI (496) cpu_start: ESP-IDF: v3.3-beta2-887-g9e70825d1[0m [0;32mI (503) cpu_start: Starting app cpu, entry point is 0x400812e8[0m [0;32mI (489) cpu_start: App cpu up.[0m [0;32mI (513) heap_init: Initializing. RAM available for dynamic allocation:[0m [0;32mI (520) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM[0m [0;32mI (526) heap_init: At 3FFB9CC8 len 00026338 (152 KiB): DRAM[0m [0;32mI (533) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM[0m [0;32mI (539) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM[0m [0;32mI (545) heap_init: At 4009537C len 0000AC84 (43 KiB): IRAM[0m [0;32mI (551) cpu_start: Pro cpu start user code[0m [0;32mI (234) cpu_start: Starting scheduler on PRO CPU.[0m [0;32mI (0) cpu_start: Starting scheduler on APP CPU.[0m Mounting flash filesystem... No LFS image loaded I (395) wifi:wifi driver task: 3ffc4430, prio:23, stack:3584, core=0 [0;32mI (395) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE[0m [0;32mI (395) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE[0m I (425) wifi:wifi firmware version: 44aa95c I (425) wifi:config NVS flash: enabled I (425) wifi:config nano formating: disabled I (425) wifi:Init dynamic tx buffer num: 32 I (435) wifi:Init data frame dynamic rx buffer num: 32 I (435) wifi:Init management frame dynamic rx buffer num: 32 I (445) wifi:Init management short buffer num: 32 I (445) wifi:Init static rx buffer size: 1600 I (455) wifi:Init static rx buffer num: 10 I (455) wifi:Init dynamic rx buffer num: 32 NodeMCU ESP32 built with Docker provided by frightanic.com branch: dev-esp32 commit: f4887bf134235c05e6c9b2efad370e6d5018f91a SSL: true modules: - built on nodemcu-build.com provided by frightanic.com branch: dev-esp32 commit: dd3b217df201fde00fcf84be1d485d555d433bed SSL: false modules: file,gpio,node,pulsecnt,tmr,uart build 2020-09-15-17-10-55 powered by Lua 5.1.4 on ESP-IDF v3.3-beta1-1391-g9e70825d1 on SDK IDF Hello World! file romtable: 0x3f4042a4 gpio romtable: 0x3f404530 node romtable: 0x3f403fe8 pulsecnt nil tmr romtable: 0x3f404b34 uart romtable: 0x3f409064 ```Code in question:
Firmware used:
Tool-Chain used: https://nodemcu-build.com/index.php http://chilipeppr.com/esp32 https://github.com/marcelstoer/nodemcu-pyflasher/releases/download/v4.0/NodeMCU-PyFlasher-4.0-x64.exe
Flash Log:
I am unsure how to act further therefore im opening this issue (which is btw my first so please excuse me for the bad writeup)