-
Notifications
You must be signed in to change notification settings - Fork 68
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
Unsupported board in build Zephyr applications #21
Comments
I have been trying to debug this issue but haven't got any success. I am attaching a few more details about the problem to have a clearer understanding of the scenario.
Following is the command prompt output for the reference, kirank@CSTLinux1:~/zephyrproject/zephyr/samples/basic/blinky$ west build -b swervolf_nexys -- -DBOARD_ROOT=$SWERVOLF_ROOT/zephyr -DSOC_ROOT=$SWERVOLF_ROOT/zephyr -DDTS_ROOT=$SWERVOLF_ROOT/zephyr /home/kirank/swervolf/fusesoc_libraries/swervolf//zephyr/soc/riscv/swervolf/dts_fixup.h Use of these files is deprecated; use the devicetree.h API instead. -- Configuring done I do not understand the cause of the above error and it will be great to hear from you. Thanks, |
Thanks for the detailed debugging. I'm not sure exactly why you get this error, but I think it could be because your Zephyr version is too new. A while ago I updated the SwerVolf BSP to work with Zephyr 2.2, but I haven't tried newer versions. Could you try to see if Zephyr 2.2 works for you? If that works, I can look into supporting newer Zephyr versions when I can find the time. |
Hi olofk, Thanks for your feedback. As you suggested I tried Zephyr 2.2 with SweRVolf but unfortunately that too isn't working for me. I am getting the exact output as I was getting before except the only difference now that Zephyr-sdk version is 0.11.2 instead of 0.11.3. Is there can be any problem with the Linux environment setting or libraries installed to work with Zephyr application? |
Hi olofk, I tried going around and building different examples for swervolf_nexys board. I was able to build different examples such as hello_world, minimal etc. using Zephyr application which gurranted Zephyr application is working properly. For 'blinky' example, instead of swervolf_nexys board we tried building it with arm's reel_board and it got build successfully. After the inspection of configuration files related to both swervolf_nexys and reel_board we found some differences in their devicetree files. For reel_board we found there was configuration done for 'led0' in its devicetree files but it was missing from devicetree files of swervolf_board. I think the error I posted here also points to the same thing i.e. missing board configuration of 'led0' for swervolf_nexys board. It would be great to hear your thoughts on this and how should I configure the swervolf_nexys board for 'led0' if it missing. Thanks, |
I finally got around to take a look at this and it turned out to be far more complicated than I had expected. Zephyr has basically deprecated the generic GPIO driver that I was using, so it looks like the only way now is to create a dedicated GPIO driver for SweRVolf, but then it must also be accepted into the Zephyr code base before we can use it. We could of course create a fork of Zephyr as well, but that will increase maintenance a lot. So for now we will have to live without the LED infrastructure or stay on Zephyr 2.1 which I believe still works |
Zephyr support was updated to 2.4 earlier this year. Could you please let me know if this issue remains |
I am getting an error while building Zephyr application.
The error states that "Unsupported board: led0 devicetree alias not defined".
According to this error, the swervolf_nexys board is not supported by Zephyr application but in the command line, we are giving the same board.
Any feedback will be really appreciated.
Thanks,
Kiran Khunte
The text was updated successfully, but these errors were encountered: