The following is documentation for a proposed Pine64 product by the community and is not an official Pine64 product. This content is the result of initial discussions about this device documented in the forum.
Join us for discussion in IRC.
The aim of this project is to create a Pine64 open source USB flash drive (hence the name PineFlash), that can act as the basis of future projects in this area. An open source flash device would allow the community to address storage information security (CIA). Additionally, issues such as speed and compatibility can also be addressed.
|Read speed||12Mbit/s (Full speed USB 1.x)||480Mbit/s (High speed USB 2.0)|
|Write speed||12Mbit/s (Full speed USB 1.x)||480Mbit/s (High speed USB 2.0)|
This is intended to document the project direction towards a manufacturing-viable device.
TODO Plan out hardware steps.
- USB 1.x speed mass storage device, no real storage. Get the controller presenting itself as a mass storage device. Data read and written will just be placeholder data to prove that the USB communication is working correctly.
- Single flash chip selected for storage - quad-SPI. Prove out that we can select a single flash chip, store data to it and read it back. This proves our understanding of the quad-SPI interface and implement some basic interface for communicating with a single flash chip.
- Multiple flash chips selected for storage - quad-SPI. Prove that we can communicate with multiple flash chips via quad-SPI.
This is the documentation of the initial prototype design.
The initial prototype is to be a 'hat' for the community driven Nutcracker project, specifically the BL602. The controller is RISC-V (as the final controller is planned to be) and supports quad-SPI.
TODO The proposed schematic for the device.
TODO The bill of materials used in the schematic.
TODO The PCB design for the device.
The work on the BL602 is to be on-top of the documented work by Lupyuen.
TODO Document the prototype's software stack.
- TinyUSB - An open source software stack for slave USB devices
TODO Figure out exactly how the prototype will be tested to ensure robustness and performance.
This is a list of suggested features collated and attributed (where possible). This list is not meant to encapsulate every possible idea or suggestion, just a series of plausible ones that can be considered within the scope of this project.