Difference between revisions of "PineNote Development/Booting Linux"

From PINE64
Jump to navigation Jump to search
(→‎Steps to patch U-Boot: Not suited as list)
m (Add note that this page only refers to batch 1)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{Note|This page is only relevant for the first batch of PineNotes, sold in 2021/2022! Batch 2 (2024) PineNote come with linux pre-flashed!}}
To boot Linux, the stock U-Boot has to be patched.  
To boot Linux, the stock U-Boot has to be patched.  


Line 12: Line 14:
  $ chmod o+x pinenote-uboot-envtool.py
  $ chmod o+x pinenote-uboot-envtool.py


2. Write your U-Boot partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>
2. Write your U-Boot partition to an image file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>


3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
Line 22: Line 24:
# Open <code>boot-menu.patch</code> to get a feel for how that works
# Open <code>boot-menu.patch</code> to get a feel for how that works


5. The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.
5. The boot-menu.patch makes assumptions about where your Linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.


6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>
6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>


{{Info|Note: Might fail with the following error: <code>patch: **** unexpected end of file in patch at line 27</code>. In that case applying the patch manually is the solution.}}
{{Info|Note: Might fail with the following error: "''patch: **** unexpected end of file in patch at line 27''". In that case applying the patch manually is the solution.}}


7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>
7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>
Line 32: Line 34:
8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>
8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>


9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.  
9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to Android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.  


10. Reboot into Linux
10. Reboot into Linux
Line 40: Line 42:
# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]
# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]
[[Category:PineNote]]

Latest revision as of 10:42, 26 November 2024

This page is only relevant for the first batch of PineNotes, sold in 2021/2022! Batch 2 (2024) PineNote come with linux pre-flashed!

To boot Linux, the stock U-Boot has to be patched.

Here the method from charasyn is used, based of work from Dorian as credited in the script. We'll use the script to pull the U-Boot environment out of the stock U-Boot partition. We'll then apply the patch, recreate the image, add a configuration file, and flash the new image to the PineNote.

Steps to patch U-Boot

1. Get the patch and the Python tool:

$ mkdir pinenote-uboot && cd pinenote-uboot
$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch
$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py
$ chmod o+x pinenote-uboot-envtool.py

2. Write your U-Boot partition to an image file: dd if=/dev/mmcblk0p1 of=~/uboot.img

3. Extract the environment: ./pinenote-uboot-envtool.py extract uboot.img uboot.env

4. Poke around the files (or skip this if you don't like to learn...):

  1. Open uboot.env -- see, it's just text at this point!
  1. Open boot-menu.patch to get a feel for how that works

5. The boot-menu.patch makes assumptions about where your Linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.

6. Apply boot-menu.patch: patch uboot.env boot-menu.patch

Note: Note: Might fail with the following error: "patch: **** unexpected end of file in patch at line 27". In that case applying the patch manually is the solution.

7. Rewrite the new environment to the image: ./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img

8. Write the image to the boot partition from the PineNote: dd if=~/uboot-patched.img of=/dev/mmcblk0p1

9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for /boot/which_os.txt to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to Android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an l in the file for Linux.

10. Reboot into Linux

Sources and further reading

  1. U-boot with rockchip docs
  2. Helpful stack overflow to learn a bit about the boot process/terminology
  3. This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.