samples: drivers: mbox: Disable UART Flow Control on nrf54h20 #75309
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
FYI @nordic-piks , @anangl , @jaz1-nordic |
nordic-piks
approved these changes
Jul 2, 2024
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
2646b3a
to
5fe13c1
Compare
nordic-piks
approved these changes
Jul 2, 2024
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
5fe13c1
to
c5cc868
Compare
|
Dear reviewers, please find some time to do the review. |
jaz1-nordic
previously approved these changes
Jul 11, 2024
nordic-segl
added a commit
to nordic-segl/sdk-zephyr
that referenced
this pull request
Jul 15, 2024
…rf54h20 Nrf54h20dk has UART Flow Control enabled by default on all cores. It's a source of problem when mbox sample is run in Twister. Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core. As a result, remote core stucks on printing boot banner. Twister fails sample due to the timeout while waiting for messages from remote to host. Disable Flow Control on remote core when mbox sample is executed on nrf54h20. Upstream PR: zephyrproject-rtos/zephyr#75309 Signed-off-by: Sebastian Głąb <[email protected]>
rlubos
pushed a commit
to nrfconnect/sdk-zephyr
that referenced
this pull request
Jul 15, 2024
…rf54h20 Nrf54h20dk has UART Flow Control enabled by default on all cores. It's a source of problem when mbox sample is run in Twister. Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core. As a result, remote core stucks on printing boot banner. Twister fails sample due to the timeout while waiting for messages from remote to host. Disable Flow Control on remote core when mbox sample is executed on nrf54h20. Upstream PR: zephyrproject-rtos/zephyr#75309 Signed-off-by: Sebastian Głąb <[email protected]>
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
c5cc868
to
867bb00
Compare
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
867bb00
to
1c82233
Compare
nordic-segl
added a commit
to nordic-segl/sdk-zephyr
that referenced
this pull request
Jul 18, 2024
…rf54h20 and nrf54l15 Nrf54h20dk and nrf54l15 have UART Flow Control enabled by default on all cores. It's a source of problem when mbox sample is run in Twister. Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core. As a result, remote core stucks on printing boot banner. Twister fails sample due to the timeout while waiting for messages from remote to host. Disable Flow Control on remote core when mbox sample is executed on nrf54h20 or nrf54l15. Upstream PR: zephyrproject-rtos/zephyr#75309 Signed-off-by: Sebastian Głąb <[email protected]>
rlubos
pushed a commit
to nrfconnect/sdk-zephyr
that referenced
this pull request
Jul 18, 2024
…rf54h20 and nrf54l15 Nrf54h20dk and nrf54l15 have UART Flow Control enabled by default on all cores. It's a source of problem when mbox sample is run in Twister. Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core. As a result, remote core stucks on printing boot banner. Twister fails sample due to the timeout while waiting for messages from remote to host. Disable Flow Control on remote core when mbox sample is executed on nrf54h20 or nrf54l15. Upstream PR: zephyrproject-rtos/zephyr#75309 Signed-off-by: Sebastian Głąb <[email protected]>
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
1c82233
to
920dc23
Compare
carlocaione
approved these changes
Aug 8, 2024
…54l15 Nrf54h20dk and nrf54l15 have UART Flow Control enabled by default on all cores. It's a source of problem when mbox sample is run in Twister. Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core. As a result, remote core stucks on printing boot banner. Twister fails sample due to the timeout while waiting for messages from remote to host. Disable Flow Control on remote core when mbox sample is executed on nrf54h20 or nrf54l15. Signed-off-by: Sebastian Głąb <[email protected]>
nordic-segl
force-pushed
the
NRFX-NONE_Improve-mbox-on-nrf54h20
branch
from
920dc23
to
9623a53
Compare
|
rebased on main@ad3e941ad3ed9e3e2f9032b0151558a948e99fb9 |
jaz1-nordic
approved these changes
Aug 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nrf54h20dk has UART Flow Control enabled by default on all cores.
It's a source of problem when mbox sample is run in Twister.
Twister opens serial port only on host core, thus nobody confirms reception of logs from remote core.
As a result, remote core stucks on printing boot banner.
Twister fails sample due to the timeout while waiting for messages from remote to host.
Disable Flow Control on remote core when mbox sample is executed on nrf54h20.