jordan/rpi4-osdev
1
0
Fork 0
mirror of https://github.com/isometimes/rpi4-osdev synced 2024-09-19 21:32:58 +00:00
Code Issues Projects Releases Packages Wiki Activity

A few corrections

Browse source
This commit is contained in:
isometimes 2022-07-06 19:58:16 +01:00
parent 2b9e41259b
commit 0dbc5d32db
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
part14-spi-ethernet/README.md
View file

@ -51,7 +51,7 @@ void gpio_initOutputPinWithPullNone(unsigned int pin_number);
Specifically, `spi_init()` sets GPIO 7, 9, 10, and 11 to use the ALT0 function. Cross-referencing with the [BCM2711 ARM Peripherals document](https://datasheets.raspberrypi.com/bcm2711/bcm2711-peripherals.pdf), page 77, you'll see that this maps SPI0 to the GPIO header. GPIO 8 is mapped as an output pin, since we'll use this to signal to the ENC28J60 that we want to talk. In fact, the `spi_chip_select()` function takes a true/false (boolean) parameter which either sets or clears this pin. Specifically, `spi_init()` sets GPIO 7, 9, 10, and 11 to use the ALT0 function. Cross-referencing with the [BCM2711 ARM Peripherals document](https://datasheets.raspberrypi.com/bcm2711/bcm2711-peripherals.pdf), page 77, you'll see that this maps SPI0 to the GPIO header. GPIO 8 is mapped as an output pin, since we'll use this to signal to the ENC28J60 that we want to talk. In fact, the `spi_chip_select()` function takes a true/false (boolean) parameter which either sets or clears this pin.
Looking at the SPI0 register map on page 134, we see this reflected in our `REGS_SPI0` structure. This gives us handy access to the SPI0 peripheral's memory-mapped registers. Looking at the SPI0 register map on page 136, we see this reflected in our `REGS_SPI0` structure. This gives us handy access to the SPI0 peripheral's memory-mapped registers.
Our `spi_send_recv()` function then sets us up for some communcation: Our `spi_send_recv()` function then sets us up for some communcation:
@ -99,7 +99,7 @@ void ENC_SPI_SendWithoutSelection(unsigned char command) {
} }
``` ```
Perhaps the most confusing aspect is the chip selection. Through a bit of trial & error I discovered that when GPIO08 is clear, the device is selected, and when it's set, the device is deselected. If you can explain this to me, I'd love to hear from you - frankly, I was just pleased to get it working, so I moved on! Perhaps the most confusing aspect is the chip selection. Through a bit of trial & error I discovered that when GPIO08 is clear, the device is selected, and when it's set, the device is deselected. It turns out this is because the Chip Select pin on the ENC28J60 is active LOW and there's no invertor on the board (presumably to save costs), so GPIO08 must be LOW to enable the IC.
Some more timer functions Some more timer functions
------------------------- -------------------------

2
part14-spi-ethernet/kernel/arp.c
View file

@ -105,7 +105,7 @@ void SendArpPacket(uint8_t *targetIP, uint8_t *deviceMAC)
// The source of the packet will be the ENC28J60 MAC address // The source of the packet will be the ENC28J60 MAC address
memcpy(arpPacket.eth.SrcAddrs, deviceMAC, 6); memcpy(arpPacket.eth.SrcAddrs, deviceMAC, 6);
// The destination is broadcast - a MAC address of FF:FF:FF:FF:FF:FF */ // The destination is broadcast - a MAC address of FF:FF:FF:FF:FF:FF
memset(arpPacket.eth.DestAddrs, 0xFF, 6); memset(arpPacket.eth.DestAddrs, 0xFF, 6);
arpPacket.eth.type = ARPPACKET; arpPacket.eth.type = ARPPACKET;