Skip to content

Conversation

@HalfSweet
Copy link
Contributor

@HalfSweet HalfSweet commented Nov 5, 2025

  • declare n16r8 (default) and a128r8 revisions in board.yml
  • add revision.cmake to validate BOARD_REVISION and keep n16r8 as fallback

@github-actions
Copy link

github-actions bot commented Nov 5, 2025

Hello @HalfSweet, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

Copy link
Member

@gmarull gmarull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please split changed into independent commits

Comment on lines +3 to +9
if(NOT DEFINED BOARD_REVISION)
set(BOARD_REVISION "n16r8")
else()
if(NOT BOARD_REVISION IN_LIST BOARD_REVISIONS)
message(FATAL_ERROR "${BOARD_REVISION} is not a valid revision for sf32lb52_devkit_lcd. Accepted revisions: ${BOARD_REVISIONS}")
endif()
endif()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nordicjm looks like this should not be needed?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is needed for custom board revisions

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doesn't build system complain if one provides an invalid board revision?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not with custom, custom basically means the revision.cmake file defines the revisions, the ones in board.yml will just be listed by the list boards python script

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there anything else I need to modify here? I've noticed similar wording in some other board variants.
For example: https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/arduino/uno_r4/revision.cmake

Comment on lines +3 to +9
if(NOT DEFINED BOARD_REVISION)
set(BOARD_REVISION "n16r8")
else()
if(NOT BOARD_REVISION IN_LIST BOARD_REVISIONS)
message(FATAL_ERROR "${BOARD_REVISION} is not a valid revision for sf32lb52_devkit_lcd. Accepted revisions: ${BOARD_REVISIONS}")
endif()
endif()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is needed for custom board revisions

default: "n16r8"
revisions:
- name: "n16r8"
- name: "a128r8"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this variant boot now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, currently the bootrom transfers code to SRAM for execution.

Of course, this isn't a perfect solution. In future updates, I'll add memc drivers to support PSRAM and integrate MCUBoot adaptation to enable running larger code sizes from NAND storage

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this variant have the NOR defined in board dts files?

- declare n16r8 (default) and a128r8 revisions in board.yml
- add revision.cmake to validate BOARD_REVISION and keep n16r8 as fallback

Signed-off-by: Haoran Jiang <[email protected]>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 6, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants