Another step forward! I find that the line to update PATH must be placed AFTER export.sh has run, or else Linux boot hangs due to complaint about tool path. But the following works in my ~/.profile:
Code: Select all
# IDF v4.0-beta2, 2019r2 toolchain applied
# DOES NOT WORK HERE: export PATH="$HOME/Esp_Idf_Versions/4_0_beta2/tools_r2/xtensa-esp32-elf/bin:$PATH"
export IDF_TOOLS_PATH=~/Esp_Idf_Versions/4_0_beta2/tools
export IDF_NVS_GEN=$HOME/Esp_Idf_Versions/4_0_beta2/esp-idf/components/nvs_flash/nvs_partition_generator/nvs_partition_gen.py
. $HOME/Esp_Idf_Versions/4_0_beta2/esp-idf/export.sh
export PATH="$HOME/Esp_Idf_Versions/4_0_beta2/tools_r2/xtensa-esp32-elf/bin:$PATH"
When I check the gcc version, I get this.
Code: Select all
refact_oct2019$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG esp-2019r2) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
And now, my software is provisioning and running successfully with Azure. No cert/key errors. And able to use SPIRAM. Thanks for sticking with me to get this all figured out!
IMPORTANT REQUEST FOR GOING FORWARD:
I want to permanently change to use 4.0 IDF (from 3.3.1) as soon as I can for my project. But in order to do so, I would want 2019r2 toolchain included automatically when using install.sh/export.sh. It should not require manual patching.
Do you think this will be the case by the time 4.0 is officially RELEASED?
Thanks!