doc: fix: rephrase closeout

This commit is contained in:
2024-08-05 17:17:44 -04:00
parent e7308e362d
commit 9ee626c16f

View File

@@ -133,19 +133,23 @@
> "Sketch uses 40062 bytes (15%) of program storage space" ...
> ... and so on. Once you reach this point, you are well-prepared to
> install the LiBCM firmware to the board. So long as LiBCM is
> connected to your computer via its black USB cable, linked to the
> Arduino IDE in the Tools > Ports option (using the right baud rate),
> and as long as your system user is allowed to use `dialout` group
> resources, firmware installation should succeed, unless something
> has gone seriously wrong with LiBCM.
> connect to LiBCM and upload firmware to it -- you will do this using
> the arrow Upload arrow to the right of the compile (a.k.a. Verify)
> checkmark. So long as LiBCM is connected to your computer via its
> black USB cable, linked to the Arduino IDE in the Tools > Ports
> option (using the right baud rate), and as long as your system user
> is allowed to use `dialout` group resources, firmware installation
> should succeed, unless something has gone seriously wrong with
> LiBCM.
## Future
## Future Video?
> If there's demand for it, I may make a short video showing some of
> the things that may go wrong while connecting to LiBCM using a Linux
> machine. Linux provides a lot of easily-accessible interfaces to
> hardware that make it easy to tell how the computer is interacting
> with USB devices, and over the years I've found it really helpful to
> bisect issues down to hardware or software ones.
> If there's demand for it, I may make a short video showing the
> actual LiBCM firmware update process on Linux. In that video, I
> would also show you how you can use Linux to navigate some of the
> issues you may encounter while trying to update LiBCM. Unlike other
> operating systems, Linux provides easily-accessible interfaces to
> hardware, making it easier to tell how the computer is interacting
> with USB devices. Over the years, I've found Linux to be really
> helpful to bisect issues down to hardware or software ones.