Unboxing the RedBearLab IoT pHat

Hello!

Been a while – I hope the winds of fortune have been blowing favorably in your various directions. Been rather busy with work myself, so I apologize for the long silence. As a reparation, today will be my first ever unboxing post!

In my never-ending search for cheap yet functional stuff, A few months ago I began following a certain project on Hackaday.io, which combined two of my favorite things at the time – the ESP8266 WiSoc and the Raspberry Pi (Zero). Essentially, the project was exploring a means of using the ESP8266 as a WiFi peripheral for the Pi with full OS support – so theoretically you’d hook up the ESP8266 (specifically the ESP07/12 models as I recall), load up whatever kernel module was needed, and you’d get a wlan0 device which you could use to do awesome. At the end, it ended up working and the board designs and everything needed are up there on Hackaday.io. However that guy ended up with a ~$20 board, which is like 4x the cost of a Pi Zero. Shortly after that, I discovered that RedBearLab were working on a WiFi/Bluetooth-LE peripheral for the Raspberry Pi boards, but most specifically the Zero. It was successfully Kickstarted and I ended up preordering one of them – they’re now generally available though. At ~$11 (during the pre-order) and offering both Bluetooth Classic/LE and WiFi, it didn’t seem to be a bad deal at all, especially when considering the fact that Pi Zeros’ USB ports are in short supply.

I picked up mine some two, three weeks later at the post office. Came in a little cardboard box like so:

20160908_203737

(Shown with the Raspberry Pi to show the relative size – Raspberry Pi not included!)

The IoT pHAT itself comes in a little foil-wrapped package like so:

20160908_204020

Here another shot with slightly better lighting:

20160908_204054

I got the version with headers pre-soldered, so here’s an up-close look at it:

20160908_204252

In this picture we can clearly see the AP6212A module, which provides the WiFi/BLE capability, as well as the 24C32F EEPROM chip (on the right) which contains “HAT” related information – as required by all Raspberry Pi HATs. There’s a little slide switch in the left side of the photo, which lets you switch from using the PCB antenna (immediately to the left of the RedBear logo silkscreen) or an external IPEX type (not included), which could be attached via the IPEX connector (directly opposite the slide switch, across the gap). The headers used won’t allow for HAT stacking, so that’s something to look out for.There are also mounting holes, which is kinda nice. I’d expect they’d match up with those on a Pi Zero, but I wouldn’t know about that…

Here’s a shot of the backside (underside?) of the board:

20160908_204413

Cool, looks like its passed FCC certification. Another thing to watch out for is the fact that this pHAT uses a significant number of available GPIOs (not sure which ones specifically, will look around and confirm), so if your application needs many GPIOs used here you may want to consider USB alternatives.

I have an A+ lying about, so here’s how they look together:

20160908_205024

 

My, what a beautiful couple!

I intend to follow this post up with a Getting Started / First Impressions post, so stay tuned! Also, let me know how I did in the comments Smile

See you (real) soon!

Comments

Post a Comment

Popular posts from this blog

Bitbanging SPI on the Raspberry Pi (via spi-gpio)

Image
Hello all and happy holidays to everyone! I’m taking a break off work for the holidays so I have a little bit of time on my hands. I will therefore regale you with tales of my exploits! From my last post, I talked about the somewhat “edge” case where you’d want to add (cheap) Ethernet to a Raspberry Pi, probably the A+ or Zero as the case may be. I haven’t figured out the fixed MAC thing just yet, but I’m working on it. Anyways, after some time, another edge-edge case came to me: The ENC28J60 takes up the only SPI peripheral available on the Pi, so what if you needed to use both the ENC28J60 AND some other SPI device? The Pi’s SPI peripheral has two chip selects, so it is theoretically possible to use the exact same bus while using the first chip select for the ENC28J60 (which it uses by default) and using the second chip select for the other device. However, it goes without saying that network communications require some serious computing firepower so it might cause a bit of a perfo
Read more

Getting Started with Logic Analyzers and Pulseview

Image
Hey all, Been a while. Hope you’ve been up to no good, hm? A couple of days ago, I had to do some low-level I2C work on a bare-metal ATMega328P. Digging out the datasheet, I cobbled a simple I2C driver together, the purpose of which was to permit me write a driver for the particular peripheral which would call the lower-level functions the driver provided (i.e things like i2c_start(), i2c_stop(), i2c_address(), etc etc). When I finished the I2C driver, I tested it out with an MMA8452Q I had lying about and it seemed to work just fine. Believing everything to be dandy, I went ahead and wrote the peripheral driver for the component I was working with. And that was when the funny stuff started. To cut that long story short, it wouldn’t work right when deployed to the hardware. At all. I was in a bit of a bind – the code looked great, no errors no nothing, so it was time to look at the hardware/wire-level end of things. Logic analyzers (in my limited understanding) are tools/instrume
Read more

Enabling SPI1 on the Raspberry Pi B+/Zero/2/3

Image
Me hearties, Let us plunder and pil.. Sorry, wrong blog. Ahem. Hey all, Its been a while. Been busy at work as usual, and haven’t really had much time to write much. As penance, I will post not one but two updates! This particular post is in relation to Raspberry Pi users specifically. I had earlier talked about the vagaries involved in emulating SPI over GPIO in order to get an additional SPI peripheral. It was a moderately involved process, but the rewards were great With the most recent release of the Raspbian Jessie distribution (2016-05-10), a number of improvements have been made to both the desktop parts and the “under-the-hood” parts, perhaps most significantly the kernel. This new release uses Kernel version 4.4, which now adds the ability to use the second hardware SPI peripheral, SPI1, on the Raspberry Pi. This is only available to devices with the 40-pin header (as seen from the title of this post) so users of the original model A and B will probably need to turn to
Read more