Difference between revisions of "PINE64 PineNote (pine64-pinenote)"

From postmarketOS
Jump to navigation Jump to search
 
(2 intermediate revisions by one other user not shown)
Line 62: Line 62:
 
The device is only flashable using the rkusb bootloader mode. This can be done with the opensource rkdeveloptool utility.
 
The device is only flashable using the rkusb bootloader mode. This can be done with the opensource rkdeveloptool utility.
  
To trigger the bootloader hold a magnet on the backcover of the pinenote while powering it on.  
+
To trigger the bootloader hold a magnet on the backcover of the pinenote while powering it on.
 +
 
 +
When it's booted correctly into bootloader mode it should show up in the device list of rkdeveloptool:
 +
 
 +
<source lang="shell-session">
 +
$ rkdeveloptool ld
 +
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=100    Loader
 +
</source>
 +
 
 +
It's possible to overwrite the eMMC with the LBA write command:
 +
 
 +
<source lang="shell-session">
 +
$ rkdeveloptool wl 0 rootfs.img
 +
The 0 is the offset in blocks from the start of the eMMC, can be used to flash a partition if you know the offset
 +
</source>
 +
 
 +
== Recover from a broken bootloader ==
 +
 
 +
If uboot image is overwritten the rockusb mode won't work anymore. The device might boot into maskrom mode in which case it should show up in `rkdeveloptool list` as maskrom.
 +
If the uboot image is partially overwritten but still recognized by the maskrom it won't stay in maskrom mode and you'd have to open the back of the device and short TP1301 and TP1302 while powering up. This will make eMMC reads fail so maskrom always runs.
 +
 
 +
Once the device is in maskrom mode the only thing you can do is push a new loader into ram and start that.
 +
 
 +
<source lang="shell-session">
 +
$ rkdeveloptool list
 +
here it lists maskrom now
 +
 
 +
The .bin file is build by u-boot and might have a slightly different version
 +
$ rkdeveloptool db rk356x_spl_loader_v1.04.108.bin
 +
$ rkdeveloptool ptt
 +
now it's able to read flash and list the partitions
 +
</source>
  
 
== Installation ==
 
== Installation ==
Line 69: Line 100:
 
== See also ==
 
== See also ==
 
* [https://wiki.pine64.org/wiki/PineNote PINE64 wiki page]
 
* [https://wiki.pine64.org/wiki/PineNote PINE64 wiki page]
 +
* [https://gitlab.com/pine64-org/quartz-bsp/rkdeveloptool fork of rkdeveloptool with many improvements] this will be the version supported on the pinenote.

Latest revision as of 01:42, 4 September 2021

PINE64 PineNote
The PineNote showing a pdf
The PineNote showing a pdf
Manufacturer PINE64
Name PineNote
Codename pine64-pinenote
Released 2021
Category testing
Original software Unknown
Hardware
Chipset Rockchip RK3566
CPU 4x 2Ghz Cortex-A55
GPU Mali G52 2EE
Display 1404x1872 e-paper
Storage 128 GB
Memory 4GB
Architecture aarch64
Features
USB Networking
Flashing
Touchscreen
Display
WiFi
Xwayland
FDE
Mainline
Battery
3D Acceleration
Accelerometer
Audio
Bluetooth
Camera
GPS
Mobile data
SMS
Calls
USB OTG
NFC
Ir TX


Contributors

  • MartijnBraam

Users owning this device


How to enter flash mode

The device is only flashable using the rkusb bootloader mode. This can be done with the opensource rkdeveloptool utility.

To trigger the bootloader hold a magnet on the backcover of the pinenote while powering it on.

When it's booted correctly into bootloader mode it should show up in the device list of rkdeveloptool:

$ rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=100    Loader

It's possible to overwrite the eMMC with the LBA write command:

$ rkdeveloptool wl 0 rootfs.img
The 0 is the offset in blocks from the start of the eMMC, can be used to flash a partition if you know the offset

Recover from a broken bootloader

If uboot image is overwritten the rockusb mode won't work anymore. The device might boot into maskrom mode in which case it should show up in `rkdeveloptool list` as maskrom. If the uboot image is partially overwritten but still recognized by the maskrom it won't stay in maskrom mode and you'd have to open the back of the device and short TP1301 and TP1302 while powering up. This will make eMMC reads fail so maskrom always runs.

Once the device is in maskrom mode the only thing you can do is push a new loader into ram and start that.

$ rkdeveloptool list
here it lists maskrom now

The .bin file is build by u-boot and might have a slightly different version
$ rkdeveloptool db rk356x_spl_loader_v1.04.108.bin
$ rkdeveloptool ptt
now it's able to read flash and list the partitions

Installation

Todo

See also