Replies: 1 comment 1 reply
-
Agreed that something looks off there. It almost looks like you have two builds happening at the same time, interleaved in your log output... This bit is particularly suspicious: Project build complete. To flash, run this command:
/home/tve/.espressif/python_env/idf4.4_py3.10_env/bin/python ../../../../../../../../esp-idf/components/esptool_py/esptool/esptool.py -p (PORT) -b 460800 --before default_reset --after hard_reset --chip esp32 write_flash --flash_mode dio --flash_size detect --flash_freq 80m 0x1000 build/bootloader/bootloader.bin 0x8000 build/partition_table/partition-table.bin 0x10000 build/xs_esp32.bin
or run 'idf.py -p (PORT) flash'
Executing action: flash
Serial port /dev/ttyUSB0
Connecting....
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting.......
Detecting chip type...[ 0%] Built target _project_elf_src
[ 0%] Built target memory_ld That's showing that the build has completed and it wants to flash, but then it just keeps on building. Odd. I'll take a look |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Caution: I'm still new here... 🤪
I installed the moddable SDK
I installed ESP-IDF
I ran the Hello World example on a NodeMCU: Yay! 🚀
I looked at the build log and ... it seems to me like the flash image is built twice? (As if it didn't already take long enough.) I see two times:
I haven't done a raw esp-idf build in a while, so maybe there's something obvious I'm missing...
The full build output (long) is attached (I ran
mcconfig -d -m -p esp32/nodemcu
).log.txt
Beta Was this translation helpful? Give feedback.
All reactions