samples: drivers: mbox: Disable UART Flow Control on nrf54h20 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. Signed-off-by: Sebastian Głąb <sebastian.glab@nordicsemi.no>
This commit is contained in:
parent
7cca59c81a
commit
4a9ca27060
@ -18,3 +18,7 @@
|
||||
&cpurad_bellboard {
|
||||
status = "okay";
|
||||
};
|
||||
|
||||
&uart136 {
|
||||
/delete-property/ hw-flow-control;
|
||||
};
|
||||
|
||||
@ -18,3 +18,7 @@
|
||||
&cpuppr_vevif {
|
||||
status = "okay";
|
||||
};
|
||||
|
||||
&uart135 {
|
||||
/delete-property/ hw-flow-control;
|
||||
};
|
||||
|
||||
@ -18,3 +18,7 @@
|
||||
&cpuflpr_vevif_tx {
|
||||
status = "okay";
|
||||
};
|
||||
|
||||
&uart30 {
|
||||
/delete-property/ hw-flow-control;
|
||||
};
|
||||
|
||||
@ -18,3 +18,7 @@
|
||||
&cpuflpr_vevif_tx {
|
||||
status = "okay";
|
||||
};
|
||||
|
||||
&uart30 {
|
||||
/delete-property/ hw-flow-control;
|
||||
};
|
||||
|
||||
Loading…
Reference in New Issue
Block a user