-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
wifi: Radio test combo 5340 #11710
wifi: Radio test combo 5340 #11710
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
4b4161d
to
41d70ef
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
Add a Kconfig option to choose to build for a combo build for nRF700x radio test. As we intend use the define in this file, it cannot be defined under samples/wifi/radio_test. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Wi-Fi radio test combo build is disabled by default and if enabled has to pull in the peripheral radio test child image to CPUNET for nRF5340. This is controlled by used of CPUNET configuration, but due to the mismatch in choosing different Kconfig options RPMSG child image vs. Peripheral radio test image, the partition manager is enabled because radio test sample is enabled, but no child image is enabled as CPUNET is disabled. Fix this by using the newly add macro that takes care of all dependencies. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
Use newly introduced combo build. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
This helps us catch issues with combo builds on RF5340, primarily for storing FW patches in external flash. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
41d70ef
to
e3ec117
Compare
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
This is to demonstrate the twister failure, once we solve the issue then fix will be updated.