-
Notifications
You must be signed in to change notification settings - Fork 39
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
Ox64 flashing guide: clarifications regarding serial interfaces #78
Conversation
An attempt to make the wording consistent with the use of /dev/tty[DEVICE]-style notation. Also: * Converted one of the DevCube settings examples to a table * Removed kernel command line since NuttX ignores it anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls see comments inline
|
||
[source,console] | ||
---- | ||
$ minicom -b 2000000 -D /dev/ttyACM0 | ||
$ minicom -b 2000000 -D /dev/tty[DEVICE] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was not able to solve the clarification as you propose in this PR, but in genreal you did a great job. But regarding ttyACM0 and ttyACM1 is really important to make clear there are 2 ports linked to different cores of ox64, and how to open the two ports without guessing the command.
@@ -366,19 +381,19 @@ $ minicom -b 2000000 -D /dev/ttyACM1 | |||
|
|||
Re-apply power to the Ox64. | |||
|
|||
On the `ttyACM0` console you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error. | |||
On the main (D0) console you will see Linux booting up. When prompted, log in as `root` with no password. In case the SD card is missing or empty, you'll get a `Card did not respond to voltage select! : -110` error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
|
||
On the `ttyACM1` console you'll see following log, until the sytem is fully loaded. | ||
On the M0 console you'll see following messages until the sytem is fully loaded: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
|
||
=== Connecting the Ox64 to your WiFi network | ||
The simplest way to connect is to run the following command from the Linux console (i.e. `/dev/ttyACM0`): | ||
The simplest way to connect is to run the following command from the Linux console: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
Just a heads up: I won't have access to GitHub/email for the next couple of days. Feel free to pull the commit into your own repo and make changes from there (i.e. for a new PR) if you want to work on this in the meantime. |
I mean we can go back to using |
For more complex instructions, either option is fine in my opinion, as long as it is properly explained to the user who and where to identify the proper device. For simpler instructions (such as how to flash a microSD card for the PinePhone) or if sections are linked somewhere directly without the specific section containing a warning, people tend to jump directly to the command without reading the preface and using the command, leading to potential data loss. |
An attempt to make the wording consistent with the use of /dev/tty[DEVICE]-style notation.
Also: