-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot open newly created project's tree #59
Comments
I've just installed eclipse to use this plugin on an up-to date fedora 37 OS and I see the same error as reported here. I followed the instructions line for line in the readme. Happy to help test some ideas or provide logs, just tell me what to do. Thanks. |
I confirm the same issue. Project created with: and this is the dialog message: Same situation if I generate a new project using the "Empty Zephyr Application" option. Zephyr source + Zephyr SDK installed as explained in the official Getting Started Guide Zephyr plugin version: 0.2.99.202203292124 Please help because there are many people with the same issue since several months. |
Iv got the same issue. is anyone actually looking at this ? |
any updates here? I've got the same issue too |
I created a new Zephyr Application, with
zephyr-demo
as the project's name, following the given procedureFile > New Project > C/C++ Project > Zephyr > Zephyr Application
All the paths (Zephyr base, Zephyr SDK, ...) are set correctly and do not contain spaces.
The project is created without problems (and its files are visible in OS' file explorer), but, when I try to navigate through project files in Eclipse's left panel, the IDE shows this error message:
The toolchain should automatically be found inside the SDK folder (in my case is
arm-zephyr-eabi
), but that doesn't happen for some reason. I'm struggling to find a solution.OS: Windows 10
Eclipse version: 2022-12
Plugin version: latest (v0.2.99-20220329)
Chosen board: nucleo_f401re
Chosen toolchain: arm-zephyr-eabi
The text was updated successfully, but these errors were encountered: