Skip to content

update hal_nxp to mcux sdk 25.09.00 #97158

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update hal_nxp to mcux sdk 25.09.00 #97158

wants to merge 1 commit into from
+28 −29

Conversation

ZhaoxiangJin
Copy link
Contributor

update hal_nxp to mcux sdk 25.09.00

@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 8, 2025 •
edited
Loading

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
hal_nxp zephyrproject-rtos/hal_nxp@4377ecf zephyrproject-rtos/hal_nxp#612 zephyrproject-rtos/hal_nxp#612/files

⛔ DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@github-actions github-actions bot added manifest manifest-hal_nxp DNM (manifest) This PR should not be merged (controlled by action-manifest) labels Oct 8, 2025
@ZhaoxiangJin ZhaoxiangJin force-pushed the update-hal-nxp-to-mcux-sdk-25-09-00 branch 2 times, most recently from bf0dc45 to af05737 Compare October 8, 2025 11:44
@dleach02 dleach02 self-assigned this Oct 9, 2025
@dleach02 dleach02 requested a review from hakehuang October 9, 2025 00:26
@dleach02
Copy link
Member

dleach02 commented Oct 9, 2025

@ZhaoxiangJin I think your commits probably need to be squashed into one. Because the HAL change pulls in a part number change it likely causes a bisect problem if you have a separate commit to change the part numbers in the Zephyr side.

@ZhaoxiangJin
Copy link
Contributor Author

@ZhaoxiangJin I think your commits probably need to be squashed into one. Because the HAL change pulls in a part number change it likely causes a bisect problem if you have a separate commit to change the part numbers in the Zephyr side.

yes, i will squash them

@ZhaoxiangJin ZhaoxiangJin force-pushed the update-hal-nxp-to-mcux-sdk-25-09-00 branch 2 times, most recently from a343f95 to bb24800 Compare October 9, 2025 04:20
@ZhaoxiangJin
west: update hal_nxp to mcux sdk 25.09.00
2a90804 
1. update hal_nxp to mcux sdk 25.09.00
2. Updated imxrt7xx part numbers to align with SDK.
3. Fixed typo in member of dsi_transfer_t structure. The sendDscCmd
and dscCmd shall be sendDcsCmd and dcsCmd.
4. Remove the call to the function 'CLOCK_OSC_GateOscRc400M'. This
function has been removed from the SDK.

Signed-off-by: Zhaoxiang Jin <[email protected]>
@ZhaoxiangJin ZhaoxiangJin force-pushed the update-hal-nxp-to-mcux-sdk-25-09-00 branch from bb24800 to 2a90804 Compare October 9, 2025 05:49
@sonarqubecloud SonarQubeCloud
Copy link

sonarqubecloud bot commented Oct 9, 2025

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@ZhaoxiangJin
Copy link
Contributor Author

Hi @hakehuang, there is a CI issue unrelated to this PR. This issue also occurs in #95630. Other than that, all other tests are passing. Could you please help with regression testing? Thanks.

@hakehuang
Copy link
Contributor

Hi @hakehuang, there is a CI issue unrelated to this PR. This issue also occurs in #95630. Other than that, all other tests are passing. Could you please help with regression testing? Thanks.

@ZhaoxiangJin , I kick a regression on this PR, and is it possible to provide a hal updating notes? It will be helpful to check the test plan.

@ZhaoxiangJin
Copy link
Contributor Author

Hi @hakehuang, there is a CI issue unrelated to this PR. This issue also occurs in #95630. Other than that, all other tests are passing. Could you please help with regression testing? Thanks.

@ZhaoxiangJin , I kick a regression on this PR, and is it possible to provide a hal updating notes? It will be helpful to check the test plan.

Hi @hakehuang, each time update brings a lot of changes to HAL NXP, such as large-scale device and driver updates. Some information will be recorded in README, however, it seems difficult to use notes to record the specific driver/device updates.

@dleach02
Copy link
Member

dleach02 commented Oct 9, 2025 •
edited
Loading

@ZhaoxiangJin, @hakehuang the README is not intended for recording what changes have occurred. Since our HAL is constructed from multiple sources, it is meant to record where the update is coming from. We also list any patches we maintain on top of those sources.

@ZhaoxiangJin
Copy link
Contributor Author

@ZhaoxiangJin, @hakehuang the README is not intended for recording what changes have occurred. Since our HAL is constructed from multiple sources, it is meant to record where the update is coming from. We also list any patches we maintain on top of those sources.

Yes, I know. What I don't know is what Hake needs. I just pointed out that Hake can get some information from the README. I have no intention of adding more information to the README. If Hake needs, we can further discuss how to add update notes to improve the test plan.

@hakehuang
Copy link
Contributor

hakehuang commented Oct 10, 2025 •
edited
Loading

board regression test pass, no issues found on v4.2.0-5336-g2a90804d52ce

@hakehuang
Copy link
Contributor

Yes, I know. What I don't know is what Hake needs. I just pointed out that Hake can get some information from the README. I have no intention of adding more information to the README. If Hake needs, we can further discuss how to add update notes to improve the test plan.

HAL changes shall be limited and clearly documented. and I need judge the test plan based on this.

@ZhaoxiangJin ZhaoxiangJin marked this pull request as ready for review October 10, 2025 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hakehuang hakehuang Awaiting requested review from hakehuang

@axelnxp axelnxp Awaiting requested review from axelnxp

@bperseghetti bperseghetti Awaiting requested review from bperseghetti

@butok butok Awaiting requested review from butok

@dbaluta dbaluta Awaiting requested review from dbaluta

@decsny decsny Awaiting requested review from decsny

@DerekSnell DerekSnell Awaiting requested review from DerekSnell

@dleach02 dleach02 Awaiting requested review from dleach02

@EmilioCBen EmilioCBen Awaiting requested review from EmilioCBen

@iuliana-prodan iuliana-prodan Awaiting requested review from iuliana-prodan

@JiafeiPan JiafeiPan Awaiting requested review from JiafeiPan

@manuargue manuargue Awaiting requested review from manuargue

@MaochenWang1 MaochenWang1 Awaiting requested review from MaochenWang1

@mmahadevan108 mmahadevan108 Awaiting requested review from mmahadevan108

@PetervdPerk-NXP PetervdPerk-NXP Awaiting requested review from PetervdPerk-NXP

At least 2 approving reviews are required to merge this pull request.

Assignees

@dleach02 dleach02

Labels
area: Boards/SoCs area: MIPI-DSI DNM (manifest) This PR should not be merged (controlled by action-manifest) manifest manifest-hal_nxp platform: NXP MCU platform: NXP Xtensa platform: NXP NXP
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ZhaoxiangJin @dleach02 @hakehuang @zephyrbot