jordan/rpi4-osdev
1
0
Fork 0
mirror of https://github.com/isometimes/rpi4-osdev synced 2024-11-08 19:30:39 +00:00
Code Issues Projects Releases Packages Wiki Activity

Updated documentation to reference building on Mac too

Browse source
This commit is contained in:
Adam Greenwood-Byrne 2021-02-12 20:33:01 +00:00
parent 9e713872dc
commit f9839e2233
3 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
part2-building/README.md
View file

@ -48,7 +48,7 @@ Makefiles on other platforms
If you're using clang on Mac OS X, the file already named _Makefile_ in the repo will be the one you need. Ensure the LLVMPATH is correctly set, of course. It doesn't look much different to the Arm gcc one, so the above explanation mostly applies.
Similarly, if you're using Arm gcc natively on Windows, [part8-breakout-ble](../part8-breakout-ble) has a _Makefile.gcc.windows_ just as an example.
Similarly, if you're using Arm gcc natively on Windows, part8-breakout-ble has a _Makefile.gcc.windows_ just as an example.
Building
--------

4
part3-helloworld/README.md
View file

@ -34,6 +34,8 @@ Here's what my machine looks like:
Make a note of the COMx number in brackets after the Prolific entry - in my case, that's **COM5**.
The same cable will work on a Mac without the need to install any drivers. I'd recommend installing [Serial Tools](https://apps.apple.com/gb/app/serialtools/id611021963?mt=12) as an alternative to PuTTY before you read ahead. There's a good article on how to use it [here](https://www.w7ay.net/site/Applications/Serial%20Tools/).
Now we need to look at the RPi4 to identify how to connect the other end of the cable. You'll be looking for the **GPIO pins**, all 40 of them, which are just above the Raspberry Pi copyright notice.
The diagram below shows where you need to make connections. The BLACK connecter hooks over Ground (Pin 6), the WHITE over TXD (GPIO 14/Pin 8) and the GREEN over RXD (GPIO 15/Pin 10). As we are powering the RPi4 using a dedicated power supply, make sure you **don't connect the RED connector**.
@ -58,6 +60,8 @@ Setting up PuTTY
* Save these settings by typing a name e.g. "Raspberry Pi 4" in the textbox under "Saved Sessions" and clicking Save
* You can now start the connection by double-clicking on "Raspberry Pi 4" - if you do, all you will see for now is an empty black window
If you're using a different terminal emulator, you'll need to use the same settings as above following the application vendor's instructions on how to use the software.
A quick config.txt change
-------------------------

2
part4-miniuart/README.md
View file

@ -60,7 +60,7 @@ Some extra code
I don't want this tutorial to just be an explanation so, in the code, you'll see I've added some more functionality to _io.c_ and made use of it in our kernel. Have a read through and see if you can understand what's going on. Refer to the documentation again if you need to.
We can now read from our UART too! If you build the kernel and power on the RPi4 just like before, it'll say hello to the world again. But, after that, you can type into the PuTTY window and the RPi4 sends the characters right back to you.
We can now read from our UART too! If you build the kernel and power on the RPi4 just like before, it'll say hello to the world again. But, after that, you can type into the terminal emulator (e.g. PuTTY) window and the RPi4 sends the characters right back to you.
_Now we're communicating in two directions!_