-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Link error in SPI when building for riscv (IDFGH-8720) #10161
Comments
Could you please try adding |
Hey @igrr! I've tried that (on a clean build folder to be sure) and the error is the same... |
Interesting, could you please check that the missing symbol is present in the object file?
(not sure what's the equivalent of pipe & grep on Windows, sorry — the point is to see if the symbol name is present in riscv32-esp-elf-nm output) |
I believe the equivalent would be: WIth and without newlib in the |
I see, then we are on to something. If the symbol is missing from the object file, then it explains why it is not found. Could you please attach or upload somewhere:
|
If the build is done by https://github.com/nanoframework/nf-interpreter/tree/main/CMake, then I think I might know where the issue is: your toolchain file https://github.com/nanoframework/nf-interpreter/blob/main/CMake/toolchain.riscv32-esp-elf.cmake doesn't specify correct compiler flags for ESP32-C3. There should be no The files above can be used to confirm whether that's indeed the cause. |
Thanks for looking into that! |
And yes, |
Please check if adding |
Here are the requested files:
|
@igrr brilliant!! That was it. It's building fine now!🥳 |
Nice! Looking forward to the NanoFramework release for C3! |
Answers checklist.
General issue report
I'm working on adding a build of .NET nanoFramework for ESP32_C3.
All good so far except that I'm running into an issue with SPI.
I'm suspecting this is because we are calling SPI API from C++ code.
It's worth mentioning that the exact same code builds fine when builing for ESP32 and ESP32_S2.
I've searched around and found other reports of similiar issues with riscv.
Adding them here, for reference in case that's usefull:
telegramdesktop/tdesktop#17449
advancedtelematic/aktualizr#1427
Thanks!
The text was updated successfully, but these errors were encountered: