#CONNECT RPI TO MAC ETHERNET CABLE HOW TO#
#CONNECT RPI TO MAC ETHERNET CABLE DRIVERS#
#CONNECT RPI TO MAC ETHERNET CABLE DOWNLOAD#

It turned out I had got my footprint for the crystal wrong, shorted both of the oscillator pins of the IC to the can and connected both ends of the crystal to ground. Probing with an oscilloscope showed both pins at about 1.1V DC. Power supply was straight from my bench PSU so again unlikely.

#CONNECT RPI TO MAC ETHERNET CABLE DOWNLOAD#

I double checked my soldering with decent magnification and it looked fine.The Eagle footprint was download from Farnell / element14 so was reasonably confident with that. Due to the simplicity of the connections between the Pi and the ENC28J60, this pointed at bad soldering, incorrect power supply, wrong pinout or something wrong with the crystal. I did not get any flashing LEDs, and got errors in the next step, Setup on the Pi, with a non responsive device. If an Ethernet cable (connected to a router) is plugged in, the orange LED on the Ethernet connector should turn on and the green LED should flash, indicating network activity. I began by connecting the board (no Pi connected) to a 3.3V supply and it drew approximately 120mA which matched with a cheap Chinese breakout board for the same chip. I have highlighted these on the BOM (attached also) I don't have much space and having a second monitor around for longer than necessary would be a pain. I assembled the Ethernet portion of the board first as I wanted to use SSH to access the Pi. Luckily, I have an Atten hot air station which managed these no problem. This was achieved but does mean that fairly small parts are used (SSOP IC) and the crystals have pads only on the bottom, meaning soldering these with a soldering may be a bit of an endeavour. The PCB was laid out, mainly trying to fit all those parts in the small footprint of the Pi Zero and keeping all the high speed data buses away from each other. It's also an easier way to test the functionality of the WM8731. R16, R17) are also not required for the WSPRpi as it only needs audio input but I added footprints for them as everything else was already in place. Strictly, the audio output filter components (C11, C12. They were put there in case the I2C bus required the external pull-up resistors but it works fine without. This produces the following schematic, I have attached the schematic as well: There is little more to this design than the datasheet use circuit for both, put onto the same PCB.

#CONNECT RPI TO MAC ETHERNET CABLE DRIVERS#

Both of these parts were chosen as they had kernel drivers built in to the Raspbian distro, making using them relatively simple. This is based around two main ICs, the Wolfson / Cirrus Logic WM8731 audio codec and the Microchip ENC28J60 SPI to Ethernet adapter. If a connection to the Internet is present, it will also upload the spots to the WSPR database automatically. This is why the Ethernet connection was still useful, even with the Pi Zero W being released when I was waiting for the PCBs to be delivered as often a wired LAN is run between the operators laptops but no wireless connection is available. I say network connection as the WSPRpi may be used on DXpeditions without Internet connection so will provide a web server showing the received stations.

The two most important features for the Pi to be able to receive WSPR signals are an audio input and an network connection.

#CONNECT RPI TO MAC ETHERNET CABLE HOW TO#

Explanation of which can be found here: WSPRpi part 0: Introduction and what is WSPR? If you are not interested in how I intend to use it and just want to see how to add Ethernet or a soundcard to a Pi Zero, skip to the Design section.įor people interested in the use in the WSPRpi project: If you are here to see how to add Ethernet / soundcard functionality to the Pi Zero, this is a part to be used in my automated amateur radio WSPR transceiver.

Connect rpi to mac ethernet cable