Closed rpiper closed 1 month ago
Thanks for the issue. What version of zephyr are you using?
I think I have it fixed in v1.0.21.
I am not sure about the environment variable issue. If you call the west update from the GUI/command palette, that should set the ZEPHYR_BASE variable.
I included a new command to try to debug the issue. Can you run Zephyr IDE: Debug Internal Shell
and see if there is a ZEPHYR_BASE variable present?
Thanks for the issue. What version of zephyr are you using?
I am using Zephyr 3.5.0
I think I have it fixed in v1.0.21.
I am not sure about the environment variable issue. If you call the west update from the GUI/command palette, that should set the ZEPHYR_BASE variable.
I included a new command to try to debug the issue. Can you run
Zephyr IDE: Debug Internal Shell
and see if there is a ZEPHYR_BASE variable present?
Thanks, v1.0.21 fixed the board selection, and it works now even without me manually defining ZEPHYR_BASE.
How do I go about running Zephyr IDE: Debug Internal Shell
to see if there is a ZEPHYR_BASE variable present? Is there a button in the extension UI, or is there a command I have to enter?
open the command pallet and run it from there. ctrl-p -> Zephyr IDE: Debug Internal Shell
Looks good to me
ZEPHYR_BASE=C:\patriot\zephyr
ZEPHYR_SDK_INSTALL_DIR=C:\Users\rpiper\.zephyr_ide\toolchains
Fixed in v1.0.21
After upgrading to 1.0.20, I'm getting this error about ZEPHYR_BASE not being defined.![image](https://github.com/mylonics/zephyr-ide/assets/10685846/fba3f9b3-d32f-4ab3-8cd1-c19ffc2dd008)
I added the Environment Variable ZEPHYR_BASE with the path the zephyr directory. I didn't need this environment variable before 1.0.20, but instead used the Kconfig extension to set the zephyr base on a per-repository basis in the workspace settings like this:
"kconfig.zephyr.base": "c:\workspace\zephyr",
After ZEPHYR_BASE was added to Environment Variables, now I get a different python error.![image](https://github.com/mylonics/zephyr-ide/assets/10685846/3f143348-a1ae-4f7f-bbeb-3ca4bc445463)
This same board was working prior to 1.0.20, so I think it is the new board_list.py that is causing the issues.