Skip to content

fix(board): Update PSRAM configuration for RAK3112 to fix PSRAM error #11552

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

DanielCao0
Copy link
Contributor

@DanielCao0 DanielCao0 commented Jul 4, 2025

fix : quad_psram: psram id read error: 0x00ffffff, psram chip not found or not supported, or wrong psram line mode arduino

Configuration updates for rakwireless_rak3112:

  • Added a new psram_type property with the value opi to specify the type of PSRAM used.
  • Introduced a memory_type property that dynamically combines build.boot and build.psram_type for better memory type management.
  • Updated the menu.PSRAM.enabled description to "OPI PSRAM" for clarity.
  • Add wisblock pin define

@DanielCao0 DanielCao0 requested a review from P-R-O-C-H-Y as a code owner July 4, 2025 02:59
Copy link
Contributor

github-actions bot commented Jul 4, 2025

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello DanielCao0, we appreciate your contribution to this project!


📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 916caed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants