-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
lib: at_host: Write AT response to correct UART device #20382
base: main
Are you sure you want to change the base?
lib: at_host: Write AT response to correct UART device #20382
Conversation
efada76
to
ce35d19
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 0f81d3e085de3fc73ed59f88b34b66c5c8a35768 more detailssdk-nrf:
Github labels
List of changed files detected by CI (2)
Outputs:ToolchainVersion: 342151af73 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
Use preprocessor macro to get the uart device to use. Signed-off-by: Andreas Moltumyr <[email protected]>
Ensure that AT responses are written to the correct UART device when CONFIG_LOG_BACKEND_UART is enabled and ncs,at-host-uart is not uart0 (default). Co-authored-by: Fredrik Flornes Ellertsen <[email protected]> Signed-off-by: Andreas Moltumyr <[email protected]>
ce35d19
to
0f81d3e
Compare
If for instance trying to use
uart3
for the AT host whileCONFIG_LOG_BACKEND_UART
is enabled, AT responses all ended up in the log, not on the chosen AT host UART device.This builds on PR #20242 by @fellerts, where a fix for this issue was first posted.