-
Notifications
You must be signed in to change notification settings - Fork 2k
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
test files required to compile #20680
Comments
maribu
added a commit
to maribu/RIOT
that referenced
this issue
May 22, 2024
The board white list was needed as temporary workaround during the KConfig migration. As the migration was aborted, the workaround should no longer be needed. Partially fixes RIOT-OS#20680
maribu
added a commit
to maribu/RIOT
that referenced
this issue
May 24, 2024
The board white list was needed as temporary workaround during the KConfig migration. As the migration was aborted, the workaround should no longer be needed. Partially fixes RIOT-OS#20680
1 task
Fixed. Thanks for reporting the issue ❤️ |
ant9000
pushed a commit
to ant9000/RIOT
that referenced
this issue
Aug 23, 2024
The board white list was needed as temporary workaround during the KConfig migration. As the migration was aborted, the workaround should no longer be needed. Partially fixes RIOT-OS#20680
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Related to my PR #20668, I noticed that the board was not always flashed correctly and didn't seem to respond most of the time. For your information all the tests were done using the default example. Usually on this example you should see RIOT outputs and be able to type your commands however the boards seemed locked in a state where it was not printing anything and where it was not responding to the commands typed (so basically it was not initialized or flashed correctly).
As the code in my PR, for the arduino nano 33 BLE sense, was based on the already existing code of the arduino nano 33 BLE, I tried to look for extra common configuration somewhere else than in the board directory and found out that there was only some tests that were defining the board as one that provides a net interface. I saw, using the
dependency-debug
target, that the dependencies were not the same and that the original arduino nano 33 BLE had more dependencies than the board I added when it should have been the opposite.I added my new board in the following files (that seemed to be the only locations where there was an actual usage of the arduino-nano-33-ble) :
Here you can find a zip containing the output of the command with and without the board included in the mentioned files :
debug_dependencies-output-files.zip
For your information, this issue is not specifically related to my new board as some tests were made using the old one and the native board which also depends on the tests directory.
I don't think that it is normal that the compilation step needs some elements in the tests directory as they should not be related.
Versions
Operating System Environment
Installed compiler toolchains
riscv64-unknown-elf-gcc: missing
riscv32-esp-elf-gcc: missing
xtensa-esp32-elf-gcc: missing
xtensa-esp32s2-elf-gcc: missing
xtensa-esp32s3-elf-gcc: missing
xtensa-esp8266-elf-gcc: missing
clang: Ubuntu clang version 14.0.0-1ubuntu1.1
Installed compiler libs
riscv64-unknown-elf-newlib: missing
riscv32-esp-elf-newlib: missing
xtensa-esp32-elf-newlib: missing
xtensa-esp32s2-elf-newlib: missing
xtensa-esp32s3-elf-newlib: missing
xtensa-esp8266-elf-newlib: missing
avr-libc: missing (missing)
Installed development tools
The text was updated successfully, but these errors were encountered: