Svyatoslav Ryhel | 7a12009 | 2022-01-27 19:42:04 +0200 | [diff] [blame] | 1 | .. SPDX-License-Identifier: GPL-2.0+ |
| 2 | |
| 3 | U-Boot for the ASUS Eee Pad Transformer device family |
| 4 | ===================================================== |
| 5 | |
| 6 | ``DISCLAMER!`` Moving your ASUS Eee Pad Transformer/Slider to use U-Boot |
| 7 | assumes replacement of the vendor ASUS bootloader. Vendor Android firmwares |
| 8 | will no longer be able to run on the device. This replacement IS reversible. |
| 9 | |
| 10 | Quick Start |
| 11 | ----------- |
| 12 | |
| 13 | - Build U-Boot |
| 14 | - Process U-Boot |
| 15 | - Flashing U-Boot into the eMMC |
| 16 | - Boot |
| 17 | - Self Upgrading |
| 18 | |
| 19 | Build U-Boot |
| 20 | ------------ |
| 21 | |
| 22 | Device support is implemented by applying config fragment to a generic board |
| 23 | defconfig. Valid fragments are ``tf101.config``, ``tf101g.config`` and |
| 24 | ``sl101.config``. |
| 25 | |
| 26 | .. code-block:: bash |
| 27 | |
| 28 | $ export CROSS_COMPILE=arm-linux-gnueabi- |
| 29 | $ make transformer_t20_defconfig tf101.config # For TF101 |
| 30 | $ make |
| 31 | |
| 32 | After the build succeeds, you will obtain the final ``u-boot-dtb-tegra.bin`` |
| 33 | image, ready for further processing. |
| 34 | |
| 35 | Process U-Boot |
| 36 | -------------- |
| 37 | |
| 38 | ``DISCLAMER!`` All questions related to the re-crypt work should be asked |
| 39 | in re-crypt repo issues. NOT HERE! |
| 40 | |
| 41 | re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form |
| 42 | usable by device. This process is required only on the first installation or |
| 43 | to recover the device in case of a failed update. |
| 44 | |
| 45 | Permanent installation can be performed either by using the nv3p protocol or by |
| 46 | pre-loading just built U-Boot into RAM. |
| 47 | |
| 48 | Processing for the NV3P protocol |
| 49 | ******************************** |
| 50 | |
| 51 | .. code-block:: bash |
| 52 | |
| 53 | $ git clone https://gitlab.com/grate-driver/re-crypt.git |
| 54 | $ cd re-crypt # place your u-boot-dtb-tegra.bin here |
| 55 | $ ./re-crypt.py --dev tf101 |
| 56 | |
| 57 | The script will produce a ``repart-block.bin`` ready to flash. |
| 58 | |
| 59 | Processing for pre-loaded U-Boot |
| 60 | ******************************** |
| 61 | |
| 62 | The procedure is the same, but the ``--split`` argument is used with the |
| 63 | ``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready |
| 64 | to flash. |
| 65 | |
| 66 | Flashing U-Boot into the eMMC |
| 67 | ----------------------------- |
| 68 | |
| 69 | ``DISCLAMER!`` All questions related to NvFlash should be asked in the proper |
| 70 | place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before! |
| 71 | |
| 72 | Permanent installation can be performed either by using the nv3p protocol or by |
| 73 | pre-loading just built U-Boot into RAM. |
| 74 | |
| 75 | Flashing with the NV3P protocol |
| 76 | ******************************* |
| 77 | |
| 78 | Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can |
| 79 | enter it either by using ``wheelie`` with the correct ``blob.bin`` file or by |
| 80 | pre-loading vendor bootloader with the Fusée Gelée. |
| 81 | |
| 82 | With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in |
| 83 | encrypted state in form, which can just be written RAW at the start of eMMC. |
| 84 | |
| 85 | .. code-block:: bash |
| 86 | |
| 87 | $ wheelie --blob blob.bin |
| 88 | $ nvflash --resume --rawdevicewrite 0 1024 repart-block.bin |
| 89 | |
| 90 | When flashing is done, reboot the device. |
| 91 | |
| 92 | Flashing with a pre-loaded U-Boot |
| 93 | ********************************* |
| 94 | |
| 95 | U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently |
| 96 | U-Boot supports bootmenu entry fastboot, which allows to write a processed copy |
| 97 | of U-Boot permanently into eMMC. |
| 98 | |
| 99 | While pre-loading U-Boot, hold the ``volume down`` button which will trigger |
| 100 | the bootmenu. There, select ``fastboot`` using the volume and power buttons. |
| 101 | After, on host PC, do: |
| 102 | |
| 103 | .. code-block:: bash |
| 104 | |
| 105 | $ fastboot flash 0.1 bct.img |
| 106 | $ fastboot flash 0.2 ebt.img |
| 107 | $ fastboot reboot |
| 108 | |
| 109 | Device will reboot. |
| 110 | |
| 111 | Boot |
| 112 | ---- |
| 113 | |
| 114 | To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on |
| 115 | eMMC. Additionally, if the Volume Down button is pressed while booting, the |
| 116 | device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC |
| 117 | as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console |
| 118 | and update bootloader (check the next chapter). |
| 119 | |
| 120 | Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows |
Tom Rini | eb96db3 | 2024-07-05 08:09:23 -0600 | [diff] [blame] | 121 | the user to use/partition it in any way the user desires. |
Svyatoslav Ryhel | 7a12009 | 2022-01-27 19:42:04 +0200 | [diff] [blame] | 122 | |
| 123 | Self Upgrading |
| 124 | -------------- |
| 125 | |
| 126 | Place your ``u-boot-dtb-tegra.bin`` on the first partition of the MicroSD card |
| 127 | and insert it into the tablet. Enter bootmenu, choose update the bootloader |
| 128 | option with the Power button and U-Boot should update itself. Once the process |
| 129 | is completed, U-Boot will ask to press any button to reboot. |