Skip to content

Conversation

@Sivasubramanian678
Copy link
Contributor

This adds the config and overlay files to enable building the toolchain needed for the acp7_0 board in Zephyr.

@Sivasubramanian678
Copy link
Contributor Author

Sivasubramanian678 commented May 3, 2025

@stephanosio , Could you please review the pull request? . Please let me know if anything needs to be taken care from side.
Toolchain is not getting generated in CI tests, could you please check. We are blocked to proceed with the development work

@Sivasubramanian678 Sivasubramanian678 marked this pull request as draft May 6, 2025 13:39
@Sivasubramanian678
Copy link
Contributor Author

@nashif ,@dbaluta ,@stephanosio , Could anyone please review the pull request? . Please let me know if anything needs to be taken care from side.Toolchain is not getting generated in CI tests, could you please check. We are blocked to proceed with the development work

1 similar comment
@Sivasubramanian678
Copy link
Contributor Author

@nashif ,@dbaluta ,@stephanosio , Could anyone please review the pull request? . Please let me know if anything needs to be taken care from side.Toolchain is not getting generated in CI tests, could you please check. We are blocked to proceed with the development work

@Sivasubramanian678
Copy link
Contributor Author

Gentle reminder. We are blocked to proceed with the development work @nashif ,@stephanosio , Could anyone please review the pull request? . Please let me know if anything needs to be taken care from side. Toolchain is not getting generated in CI tests, could you please check.

1 similar comment
@Sivasubramanian678
Copy link
Contributor Author

Gentle reminder. We are blocked to proceed with the development work @nashif ,@stephanosio , Could anyone please review the pull request? . Please let me know if anything needs to be taken care from side. Toolchain is not getting generated in CI tests, could you please check.

.gitmodules Outdated
[submodule "gcc"]
path = gcc
url = https://github.com/zephyrproject-rtos/gcc.git
url = https://github.com/Sivasubramanian678/gcc.git
Copy link
Member

Choose a reason for hiding this comment

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

you should not be changing the submodule repo, instead, submit a Pr if needed to the gcc tree under the zephyr project and then point to the commit once it is merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We followed the process mentioned in the https://github.com/zephyrproject-rtos/sdk-ng#workflow-to-test-patches-with-zephyr-sdk.
Is there any change in the process?
Do we need to submit the PR for GCC fork or sdk-ng? Do we need to wait for the merge in GCC fork to submit PR in sdk-ng?
Could you please let us know the steps so that we can work accordingly

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gentle reminder. We followed the process mentioned in the https://github.com/zephyrproject-rtos/sdk-ng#workflow-to-test-patches-with-zephyr-sdk.
Is there any change in the process?
Do we need to submit the PR for GCC fork or sdk-ng? Do we need to wait for the merge in GCC fork to submit PR in sdk-ng?
Could you please let us know the steps so that we can work accordingly

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Gentle reminder. We followed the process mentioned in the https://github.com/zephyrproject-rtos/sdk-ng#workflow-to-test-patches-with-zephyr-sdk.
Is there any change in the process?
Do we need to submit the PR for GCC fork or sdk-ng? Do we need to wait for the merge in GCC fork to submit PR in sdk-ng?
Could you please let us know the steps so that we can work accordingly

Copy link
Member

Choose a reason for hiding this comment

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

there is no change to this process. This process works when you have a toolchain already in the SDK, not with a new one like here.

Also, you need to update the overlays, picolibc needs an overlay now, your change still does not provide one.

@nashif
Copy link
Member

nashif commented May 25, 2025

there is a conflict that needs to be resolved.



#ifdef XTENSA_CONFIG_INSTANTIATE
XTENSA_CONFIG_INSTANTIATE(rmap,16)
Copy link
Member

@nashif nashif May 26, 2025

Choose a reason for hiding this comment

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

please see b7a0a3d for how this should look like, use xtensa_rmap here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nashif Thank you for informing me of the changes that need to be made. I have implemented them on my side. Could you please review the pull request? Let me know if there is anything else that needs to be addressed.

@nashif
Copy link
Member

nashif commented May 26, 2025

you probably want to take this out of draft, I think it is almost there.

@Sivasubramanian678 Sivasubramanian678 marked this pull request as ready for review May 27, 2025 05:10
@Sivasubramanian678
Copy link
Contributor Author

Yes now it is opened for review

@nashif
Copy link
Member

nashif commented May 27, 2025

needs rebase

This adds the config and overlay files to enable building the
toolchain needed for the acp7_0 board in Zephyr.

Signed-off-by: Sivasubramanian <[email protected]>
@Sivasubramanian678
Copy link
Contributor Author

Sivasubramanian678 commented May 29, 2025

@nashif The rebase is complete and it is ready for review.

@nashif nashif merged commit 43ef499 into zephyrproject-rtos:main May 30, 2025
46 checks passed
@Sivasubramanian678
Copy link
Contributor Author

Please let us know when this toolchain will be included with the latest release?

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.

2 participants