From bbe13afc9c6ab075b43d2b1cab5482a7b9b96d2e Mon Sep 17 00:00:00 2001 From: Tanks Transfeld Date: Mon, 20 Mar 2023 15:20:19 +0100 Subject: [PATCH] Update embedded-workshop-book/src/uarte-implementation.md Co-authored-by: Jonathan Pallant --- embedded-workshop-book/src/uarte-implementation.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/embedded-workshop-book/src/uarte-implementation.md b/embedded-workshop-book/src/uarte-implementation.md index 0c4f31a..fae6264 100644 --- a/embedded-workshop-book/src/uarte-implementation.md +++ b/embedded-workshop-book/src/uarte-implementation.md @@ -32,8 +32,11 @@ use hal::uarte; ### Step 3: Add `struct Uarte` -✅ Add `struct Uarte` that serves as a wrapper for the `UARTE1` instance. -The struct has one field labelled `inner`, it contains the `UARTE1` instance: `hal::Uarte`. +✅ Add `struct Uarte` that serves as a wrapper for underlying HAL UART driver. + +The struct has one field labelled `inner` which is of type `hal::Uarte` but with the type parameter `T` being set to `hal::pac::UARTE1`. + +The main difference between using our `Uarte` object and the underlying HAL `Uarte` object is that *ours* will be pre-configured for the correct pins and baud rate, according to the layout of our nRF52840-DK board and the Virtual COM Port interface chip on the other end of the UART link.
Solution