THE PREMISE: As a society, we need an open source device for reading. Books are among the most important documents of our culture, yet the most popular and widespread devices we have for reading – the Kobo, the Nook, the Kindle and even the iPad – are closed devices, operating as small moving parts in a set of giant closed platforms whose owners ‘interests are not always aligned with readers’.
The Open Book aims to be a simple device that anyone with a soldering iron can build for themselves. The Open Book should be comprehensible: the reader should be able to look at it and understand, at least in broad strokes, how it works. It should be extensible, so that a reader with different needs can write code and add accessories that make the book work for them. It should be global, supporting readers of books in all the languages of the world. Most of all, it should be open, so that anyone can take this design as a starting point and use it to build a better book.
A Note to Visitors
The most important thing I can reiterate in this README is thatThis Is A Work In Progress!The eBook Wing is a first crack at the hardware, to validate things like the e-paper and audio driving circuitry, and to serve as a testbed for the software that will eventually drive the final product. The Wing is just an accessory board, and it requires aFeather M4 Expressto do the heavy lifting. Moreover, the software required to actually be an eBook is in its infancy; I can put a few Arduino sketches up here, but the long-term goal involves building open source eBook software in CircuitPython, and that’s still a ways out.
The goal is to take the lessons learned on the Wing, and apply them to the final product, The Open Book, which will contain its own microcontroller and power circuitry, so that it can be a standalone Feather that you can use as-is or extend with other wings. I’m hoping to accomplish that by the end of the year. If you want to help bring this idea into the world, feel free to fork this and open a pull request! My general road map looks something like this:
- Hardware: Build Feather Wing to validate peripheral hardware design
- Software: NativeGNU Unifont supportin CircuitPython (support all characters of all languages RTL text layout, accents, diacritics)
- Software: CircuitPython menu system for listing and selecting books on SD card
- Software: CircuitPython interface for reading a book, storing user’s place on SD card
- Hardware: Open Book Feather with SAMD 51 processor, Flash memory, shift register for buttons, indicator LED , etc.
- Board support: UF2 Bootloader for Open Book
- Board support: CircuitPython board definition for Open Book
- Secondary goal: Arduino core for Open Book
The E-Book Feather Wing
The Feather ecosystem seemed like the ideal place to start building this. An eBook reader is an inherently portable device, and all Feather mainboards support LiPo battery operation and charging via USB. All Feather boards work with the Arduino IDE, which is super accessible for anyone to hack on, and newer boards also support CircuitPython, which lowers the bar to entry even further.
The BOM
You’ll also need toorder the board from OSH Park; It’s $ 66. 80 for three.
Note that you can omit some of these things; the headphone jack might not be necessary for your use case, and I’m unclear whether the SRAM chip is going to be 100% useful; in the end it’s your book, make it with whatever bits you want
Going Forward
Immediate goals as of 9 / 2019: I’m writing a native module for CircuitPython that reads the GNU Unifont from the Wing’s flash chip, and uses that data for super fast text rendering of pixels out to a bitmap. Plus other Unicode features like bidirectional text, RTL mirroring, accents and diacritics, etc. When that’s done, the book should be able to display text in all the languages of the world, in CircuitPython.
After that, the goal will be to start writing the user interface in Python, while simultaneously making progress toward a final PCB layout for the Open Book.
GIPHY App Key not set. Please check settings