-
Notifications
You must be signed in to change notification settings - Fork 8
Failed to build for ESP Wrover Kit #79
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
Comments
Hi @artisdom . Thank you for the notification. The problem is caused by older hal and newer compiler. BTW: Are you still using Wrover-kit or you need just ESP32 target? I'm just wondering, since it's not manufactured anymore. Let me know, so that I can update examples to match the HW. |
Hi @georgik, thanks for the quick response, since our team have a few Wrover-kit already, so we're using it do prototyping quite often, will have a look at esp32-conways-game-of-life-rs as suggested. :) |
Thanks @artisdom for the feedback, that is valuable insight. I will try to add Wrover-kit version correction. |
@artisdom I've added wrover-kit to Conway's repo: https://github.com/georgik/esp32-conways-game-of-life-rs/tree/main/esp32-wrover-kit Limitation: The resolution in the example is set to: 320x100 It seems that there is an issue with PSRAM initialization, because I'm getting only IRAM, which is limited on ESP32 with Rust no_std thanks to the hole in the middle of memory caused by placement of WiFi, this is not an issue in later chips. Some details: If you spot a problem, let me know. Because with old Spooky we had PSRAM working without problem. Please, keep in mind that for Bevy ECS based examples, you'll need 1.85, which requires explicit specification of version, since it was still not marked as latest:
Once this is resolved, I will get back to Spooky Maze repo and do the upgrade to esp-hal. Yet, this repo is slightly more complex, since it has interaction with more peripherals and each board is using different way of controlling the app. Hopefull Bevy could help to simplify it. |
Ou, I see the issue. The allocation does not happen on heap, but on stack. Yay. Should be replaced by alloc and then we can have the whole screen buffer. |
Solved by introducing Heap Based framebuffer. |
Awesome work, very much appreciated, |
And happy to report back, the code in "esp32-conways-game-of-life-rs" repo is running smoothly on my Wrover Kit now. :) |
Small update. I'm working on esp-hal 1.0.0 - with Bevy 0.16 on branch https://github.com/georgik/esp32-spooky-maze-game/tree/feature/bevy |
Had a quick search with the error,
error[E0787]: the `asm!` macro is not allowed in naked functions
Found this:
PacktPublishing/Asynchronous-Programming-in-Rust#31
rust-lang/rust#128651
looks like the "asm!" macro is not allowed in naked functions, and need to be updated to use "naked_asm!" macro.
Guessing the fix would include updating the "esp-display-interface-spi-dma" package, so it can use newer version of "esp-hal" to avoid this error ?
https://github.com/esp-rs/xtensa-lx-rt
https://github.com/esp-rs/xtensa-lx
https://github.com/esp-rs/esp-hal/
https://github.com/georgik/esp-display-interface-spi-dma
The text was updated successfully, but these errors were encountered: