Difference between revisions of "PineNote Development/Booting Linux"

From PINE64
Jump to navigation Jump to search
m (almost done)
(v1)
Line 2: Line 2:


== Steps to patch uboot ==
== Steps to patch uboot ==
 
<ol>
# Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the python tool]:
<li> Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the python tool]:
<pre>
<pre>
$ mkdir pinenote-uboot && cd pinenote-uboot
$ mkdir pinenote-uboot && cd pinenote-uboot
Line 10: Line 10:
$ chmod o+x pinenote-uboot-envtool.py
$ chmod o+x pinenote-uboot-envtool.py
</pre>
</pre>
# Write your uboot partition to disk: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>
</li>
# Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
<li> Write your uboot partition to disk: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code></li>
# Poke around the files (or skip this if you don't like to learn...):
<li> Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code></li>
## Open <code>uboot.env</code> -- see, it's just text at this point!
<li> Poke around the files (or skip this if you don't like to learn...):</li>
## Open <code>boot-menu.patch</code> to get a feel for how that works
<ol>
# 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.
<li> Open <code>uboot.env</code> -- see, it's just text at this point!</li>
# Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>
<li> Open <code>boot-menu.patch</code> to get a feel for how that works</li>
## This doesn't work for me for some reason:
</ol>
<li> 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.</li>
<li> Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code></li>
<ol>
<li>This doesn't work for me for some reason:
<pre>
<pre>
$ patch uboot.env boot-menu.patch                                                             
$ patch uboot.env boot-menu.patch                                                             
Line 25: Line 29:
patch: **** unexpected end of file in patch at line 27
patch: **** unexpected end of file in patch at line 27
</pre>
</pre>
I couldn't figure out what it's complaining about here, so I ended up applying the patch manually. It's pretty straight-forward.
I couldn't figure out what it's complaining about here, so I ended up applying the patch manually. It's pretty straight-forward.</li>
# Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>
</ol>
# Write the image to the boot partition: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>
<li>Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code></li>
 
<li> Write the image to the boot partition: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code></li>
At this point, restarting your system will boot into Android -- this is because the patched uboot 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.
<li> At this point, restarting your system will boot into Android -- this is because the patched uboot 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.</li>
 
<li> Reboot into linux and go "wow"</li>
Create that file on the same boot partition you specified in the boot-menu.patch file, placing an `l` in the file for linux.  
</ol>
 
== Sources and further reading ==
== Sources and further reading ==
[https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
[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 uboot.]

Revision as of 21:13, 27 August 2022

To boot linux, we need to patch stock uboot. I used charasyn's method, based off work from Dorian as credited in the script. We'll use the script to pull the uboot environment out of the stock uboot 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 uboot

  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 uboot partition to disk: 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!
    2. 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
    1. This doesn't work for me for some reason:
      $ patch uboot.env boot-menu.patch                                                             
      patching file env.original
      Hunk #3 FAILED at 24.
      patch unexpectedly ends in middle of line
      patch: **** unexpected end of file in patch at line 27
      
      I couldn't figure out what it's complaining about here, so I ended up applying the patch manually. It's pretty straight-forward.
  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: dd if=~/uboot-patched.img of=/dev/mmcblk0p1
  9. At this point, restarting your system will boot into Android -- this is because the patched uboot 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 and go "wow"

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 uboot.