Action Item #562
Port to Pi Zero
|Status:||Closed||Start date:||16 Jan 2017|
|Severity:||01 - Critical|
The Zero is the gumstick sized board and would be a replacement for the B+ used in the PiBox Player with the projector. It's the same processor and runs the same builds as the B+ (re: HW=rpi).
I'm using a USB stackable hub with the Zero. The overall footprint is still smaller than the B+ simply because the stack is about as tall as the B+ w/ its eth port but shorter in length and width.
#1 Updated by Hammel about 2 years ago
- Description updated (diff)
- % Done changed from 0 to 10
- Power is a USB mini-A and there are no headers to power like I'm doing with the B+. But there are holes for the headers so I could add them easily enough.
- There is no audio-out on the Zero. I'd need a wifi dongle for that. There is one slot open for that. If I do that then I'll probably need a cable from the dongle to the external port on the player box otherwise I'll have to jam the dongle up against the current opening, and anchor the boards with something (a case?).
- Uses a mini-HDMI port. Need mini-to-mini HDMI cable for use with the projector, preferrably very short one.
#4 Updated by Hammel over 1 year ago
- Status changed from In Progress to Closed
- % Done changed from 10 to 100
There is no software port required for this. The rpi2 build of the core platform works just fine with the Zero.
Closing this issue. We can reference it in closed state if needed but any hardware differences we can simply google and search for hats for components like the audio output.
- Project changed from PiBox to Xeon
- Category deleted (
00 - Basic Build Issues)
- Status changed from Closed to In Progress
- Target version deleted (
- % Done changed from 100 to 50
- Severity changed from 05 - Very Low to 01 - Critical
Re-opening issue because the current RPi2 build does not boot on the Zero. This may be due to the switch to device tree overlays since the last time I tried the Zero.
One possible fix is to use "device_tree=" (no value set) in config.txt to force the old behavior before device tree's were used. This may force the firmware to just use the kernel to determine what hardware to support.
Hmm. Starting to look like the Zero may not be compatible with the 2/3: https://www.raspberrypi.org/documentation/linux/kernel/configuring.md
So I wonder how I got it to work the first time. Build with HW=rpi, possibly?