If you follow me on twitter (@gstixguru), you might know that I recently ordered an RPi CM3. Lots of people have been contacting us to find out how well our Pi Compute boards support the new, faster module, so I found a bit of time to play around with it. I'd worked with the original CM on our dev board for my GPS and RTK project a year ago with great success, and was looking forward to getting back to the Pi Compute boards.
As always, my first step was to flash a brand new image onto the CM's eMMC. I downloaded the latest Raspbian Jessie Lite ISO and mounted my CM on a Gumstix Pi FastFlash. Next, I ran rpiboot, plugged the board into my USB hub and CROSSED MY FINGERS!
|RPi CM3 on a FastFlash getting flashed. Pardon the clutter.|
So what happened next? Exactly what should: the eMMC was mounted to my file system like any unpartitioned flash drive would be. So I dd'ed the image, moved the module over to the Gumstix Pi Compute Dev Board and got ready to Pi.
At first, all I wanted was proof of life. That and I was sure the default wpa supplicant and network interfaces config would not get me on the WiFi network. So I screen'ed in and powered up the board. And yes, the console came to life, spewing forth those familiar Linux startup messages. No kernel panic, no errors, no problem. So far so good. Raspbian Lite was up and running. Oh, all the things I should test: GPIOs, I2C, SPI.... BORING!
Let's start with USB (Oh, and get the WiFi up and running while we're at it; screen is not my friend and SSH makes me smile:). The WiFi dongle goes into the port and lsusb shows a list of devices. And there it is.
Bus 001 Device 002: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Beautiful. I fix up /etc/network/interfaces and add the office WiFi network to wpa_supplicant.config and shut it down. Time to set this asside and get back to my other tasks.
Before ditching the USB console connection, I have to go into raspi-config and enable the SSH host, and reconfigure the daemon:
sudo rm /etc/ssh/ssh_host_*sudo dpkg-reconfigure openssh_server
After a restart, ssh works fine.
Let's got straight up the food chain to the camera! That's what I want to see! I want to get that Sony IMX219 taking stills and recording videos. I want to see those LVDS signals in action. The CSI-2 camera connector is by far my favorite feature of the dev board. So while I was in raspi-config, I made sure to enable the camera as well.
|Here's my Frankenberry Pi camera rig, ready to go, I hope.|
And did it work? See for yourself:
|Me and my clipboard.|
I also took a few minutes and got the USB-Ethernet board fired up, and yes, everything works great.
I am very happy. Stay tuned! I have a Raspberry Pi DSI display around here somewhere and I want to get that up and running too.