![]() Once everything is installed add the alias to the end of ~/.zshrcĪlias get_idf='. This guide for tag v4.3.2 is pretty good. ![]() ![]() Like I mentioned before esp-idf can be built for arm64 but a specific cryptoauthlib library doesn’t have arm64 support yet. Add this to the end of your ~/.zshrc Step 2 Install esp-idf for x86 Note: I use nvm and pyenv so that is referenced in the excerpt above. # export LDFLAGS="-L/usr/local/opt/ /lib" # For compilers to find "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm" # This loads nvm bash_completionĮxport PATH="/usr/local/opt/ /bin:$PATH"Įxport PATH="$HOME/.pyenv_i386/bin:$PATH" "/opt/homebrew/opt/nvm/nvm.sh" # This loads nvm # export LDFLAGS="-L/opt/homebrew/opt/ /lib" # For compilers to find Įxport PATH="$HOME/.pyenv_arm64/bin:$PATH" Once they’re both installed, it’s a good idea to reference different packages when different architectures are invoked.Įval "$(/opt/homebrew/bin/brew shellenv)"Įxport PATH="/opt/homebrew/opt/ /bin:$PATH" The good thing is, by default on i386, the brew installation is on /usr/local/bin/ and on arm64 it goes under /opt/homebrew/bin/ so nothing conflicts. Now, let’s install Mac homebrew for both arch types. Obviously, when you are working with arm64 you’ll want to work with compatible packages. In this case, once the command is executed, I see either i386 or arm64. If you check the output of the arch command, it tells us exactly what architecture the terminal is running on. I use ZSH with oh-my-zsh so the command becomes arch -x86_64 zsh. The best way, I’ve found, is to use an entire x86 terminal. I like to have both versions (arm64 & x86) on my machine because I prefer to do other development (React-Native etc.) on the much faster arm64 environment. Start by installing x86 Mac homebrew for dependencies. Step 1 Setup multiple versions of Mac Homebrew But fortunately we can still install x86 packages on Apple Macs using Rosetta2. ![]() I opened a new feature request with Microchip but don’t have high hopes this will be addressed soon. The esp-idf system itself can be installed on arm64 (Apple Silicon), however the library for Microchip ATECC608A cannot be built for arm64. So here’re the steps I took to use ESP32 on CLion on Apple Macbook Pro M1. I prefer a good understanding of the toolchain I am working with and good use of the terminal. The latter is a grea tool but feels clunky especially since it’s a extension built for VSCode. The official AWS Edukit tutorials rely on a toolchain package called PlatformIO. I’ve been using M5Stack Core 2 for AWS development kit to create a device for my door while simultaneously learning how to prepare for scale using AWS IoT. I prefer working with JetBrains IDEs and I like where I can just use the shortcuts to work with the device directly. I’ve been trying to get a better toolchain + build system going for ESP32 boards. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |