Hi WiFive -

I'm using a WROVER. There's no PSRAM entry in my sdkconfig file.

Thanks...

As stated above, when I alter the UART settings in menuconfig, I get the bootloader and early startup messages successfully redirected to UART1. Based on this, can I assume that my menuconfig settings are correct, and I should see the hello world output, or is there possibly more at play here? Thanks.

WiFive wrote: ↑

Mon Nov 11, 2019 11:25 pm

Does the shortcut exist in your start menu?

No, it isn't. Shouldn't the setup program create it for me?

Not to be too pesky, but...BTT. I'm pretty much out of ideas on this one.

Hi all - I've been trying to get my build environment right for a few days now. In an attempt to start from scratch, I've deleted my existing IDF directory, my toolchain directory and anything else I could think of. When I try to install release/V4.0 using the Windows setup tool, I get this error at...

Hi all - Earlier this week, I began experimenting with V4.0 of the IDF. It was causing some strange behavior (explained below) so I went back to V3.3, only to discover that the problem seems to persist. I then tried running a hello world example, and the problem occurs there, so at least it's not my...

Hi Angus - Here's the top of my app_main(): extern "C" void app_main() { vTaskDelay(portMAX_DELAY); ... (Obviously the delay was added as a test; program problem still exists.) Here's the relevant passage from my sdkconfig file: CONFIG_ESP32_XTAL_FREQ_40=y # CONFIG_ESP32_XTAL_FREQ_26 is not set # CO...

Hi Angus - Here's the top of my app_main(): extern "C" void app_main() { vTaskDelay(portMAX_DELAY); ... Here's the relevant passage from my sdkconfig file: CONFIG_ESP32_XTAL_FREQ_40=y # CONFIG_ESP32_XTAL_FREQ_26 is not set # CONFIG_ESP32_XTAL_FREQ_AUTO is not set CONFIG_ESP32_XTAL_FREQ=40 Thanks...

$ make Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: crosstool-ng-1.22.0-80-g6c4433a5 I can't figure out WHERE that crosstool is coming from. Anyone? It's derived by parsing the full output of "xtensa-esp32-elf-gcc --version". If you're using MSYS2, try checking ...

Update: I ignored the build warnings when building with V4.0 and flashed using make flash: behavior is not identical to that when building with cmake, but very similar: gibberish output to the console port. None of it is printing, but it's at least the right number of characters, so it's probably so...