Difference between revisions of "User:Aarondabomb/PineNote Documentation"
Jump to navigation
Jump to search
| Line 42: | Line 42: | ||
=== USB === | === USB === | ||
=== Stylus === | === Stylus === | ||
== Software == | |||
=== Stock Partition Layout === | |||
As output by the [https://github.com/rockchip-linux/rkdeveloptool rkdeveloptool] <code>ppt</code> (print partition) command: | |||
<pre> | |||
**********Partition Info(GPT)********** | |||
NO LBA Name | |||
00 00004000 uboot | |||
01 00006000 trust | |||
02 00008000 waveform | |||
03 00009000 misc | |||
04 0000B000 dtbo | |||
05 0000D000 vbmeta | |||
06 0000D800 boot | |||
07 00021800 security | |||
08 00023800 recovery | |||
09 00063800 backup | |||
10 00123800 cache | |||
11 00323800 metadata | |||
12 0032B800 super | |||
13 0093F800 logo | |||
14 00947800 device | |||
15 00967800 userdata | |||
</pre> | |||
In order, the partitions are: | |||
* <code>uboot</code>: holds the [https://en.wikipedia.org/wiki/Das_U-Boot Das U-Boot] open-source bootloader for embedded systems | |||
* <code>trust</code>: holds secrets such as keys; while such secrets are usually stored in NV-RAM or in a TPM, they can also be stored in a partition encrypted by a key held in a TPM | |||
* <code>waveform</code>: holds files specifying the voltage waveforms applied to the charged particles in the e-ink screen to manipulate them into displaying a desired image | |||
* <code>misc</code>: stores miscellaneous files needed by the firmware | |||
* <code>dtbo</code>: stores [https://en.wikipedia.org/wiki/Devicetree device tree] binary files, a description of the hardware configuration of the device | |||
* <code>vbmeta</code>: stores data needed for the verified boot process | |||
For backup, the stock partition images are available for download [https://pwarren.id.au/pinenote/partitions/ here]. | |||
== Bootloader == | |||
Without modifying the bootloader, u-boot will automatically load android. Under these circumstances, an alternative OS may be loaded by manually inputting commands to the u-boot terminal, which must be accessed by sending an interrupt signal (ctrl+c) to the device via UART during boot. Thus modifying u-boot is not, strictly speaking, necessary but will be desirable for most users wishing to use linux as their primary OS in a dual boot arrangement. | |||
There exists more than one approach to avoid having to do this each time the device is restarted. Two of these are detailed below. | |||
=== Option 1: Build U-boot from Scratch === | |||
reference: https://github.com/JoshuaMulliken/pinenote_uboot | |||
=== Option 2: Extract and Modify Existing U-boot Image === | |||
reference: https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f | |||