From: Tom Rini Date: Fri, 5 Jul 2024 14:09:23 +0000 (-0600) Subject: Merge branch 'staging' of https://source.denx.de/u-boot/custodians/u-boot-tegra X-Git-Url: http://git.dujemihanovic.xyz/img/static/%7B%7B%20%28.OutputFormats.Get?a=commitdiff_plain;h=d12e1029133aed42c5086c04a22ece0fe597e704;p=u-boot.git Merge branch 'staging' of https://source.denx.de/u-boot/custodians/u-boot-tegra Branch contains minor improvemets for existing tegra devices along with bring up of 4 new devices (ASUS Transformers T20, Microsoft Surface RT, Lenovo Ideapad Yoga 11 and WEXLER Tab 7t). --- d12e1029133aed42c5086c04a22ece0fe597e704 diff --cc doc/board/asus/transformer_t20.rst index 0000000000,b5614b1092..d4bc12d161 mode 000000,100644..100644 --- a/doc/board/asus/transformer_t20.rst +++ b/doc/board/asus/transformer_t20.rst @@@ -1,0 -1,129 +1,129 @@@ + .. SPDX-License-Identifier: GPL-2.0+ + + U-Boot for the ASUS Eee Pad Transformer device family + ===================================================== + + ``DISCLAMER!`` Moving your ASUS Eee Pad Transformer/Slider to use U-Boot + assumes replacement of the vendor ASUS bootloader. Vendor Android firmwares + will no longer be able to run on the device. This replacement IS reversible. + + Quick Start + ----------- + + - Build U-Boot + - Process U-Boot + - Flashing U-Boot into the eMMC + - Boot + - Self Upgrading + + Build U-Boot + ------------ + + Device support is implemented by applying config fragment to a generic board + defconfig. Valid fragments are ``tf101.config``, ``tf101g.config`` and + ``sl101.config``. + + .. code-block:: bash + + $ export CROSS_COMPILE=arm-linux-gnueabi- + $ make transformer_t20_defconfig tf101.config # For TF101 + $ make + + After the build succeeds, you will obtain the final ``u-boot-dtb-tegra.bin`` + image, ready for further processing. + + Process U-Boot + -------------- + + ``DISCLAMER!`` All questions related to the re-crypt work should be asked + in re-crypt repo issues. NOT HERE! + + re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form + usable by device. This process is required only on the first installation or + to recover the device in case of a failed update. + + Permanent installation can be performed either by using the nv3p protocol or by + pre-loading just built U-Boot into RAM. + + Processing for the NV3P protocol + ******************************** + + .. code-block:: bash + + $ git clone https://gitlab.com/grate-driver/re-crypt.git + $ cd re-crypt # place your u-boot-dtb-tegra.bin here + $ ./re-crypt.py --dev tf101 + + The script will produce a ``repart-block.bin`` ready to flash. + + Processing for pre-loaded U-Boot + ******************************** + + The procedure is the same, but the ``--split`` argument is used with the + ``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready + to flash. + + Flashing U-Boot into the eMMC + ----------------------------- + + ``DISCLAMER!`` All questions related to NvFlash should be asked in the proper + place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before! + + Permanent installation can be performed either by using the nv3p protocol or by + pre-loading just built U-Boot into RAM. + + Flashing with the NV3P protocol + ******************************* + + Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can + enter it either by using ``wheelie`` with the correct ``blob.bin`` file or by + pre-loading vendor bootloader with the Fusée Gelée. + + With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in + encrypted state in form, which can just be written RAW at the start of eMMC. + + .. code-block:: bash + + $ wheelie --blob blob.bin + $ nvflash --resume --rawdevicewrite 0 1024 repart-block.bin + + When flashing is done, reboot the device. + + Flashing with a pre-loaded U-Boot + ********************************* + + U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently + U-Boot supports bootmenu entry fastboot, which allows to write a processed copy + of U-Boot permanently into eMMC. + + While pre-loading U-Boot, hold the ``volume down`` button which will trigger + the bootmenu. There, select ``fastboot`` using the volume and power buttons. + After, on host PC, do: + + .. code-block:: bash + + $ fastboot flash 0.1 bct.img + $ fastboot flash 0.2 ebt.img + $ fastboot reboot + + Device will reboot. + + Boot + ---- + + To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on + eMMC. Additionally, if the Volume Down button is pressed while booting, the + device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC + as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console + and update bootloader (check the next chapter). + + Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows -the user to use/partition it in any way the user desires. ++the user to use/partition it in any way the user desires. + + Self Upgrading + -------------- + + Place your ``u-boot-dtb-tegra.bin`` on the first partition of the MicroSD card + and insert it into the tablet. Enter bootmenu, choose update the bootloader + option with the Power button and U-Boot should update itself. Once the process + is completed, U-Boot will ask to press any button to reboot. diff --cc doc/board/wexler/qc750.rst index 0000000000,adef3c85dd..b61e40176b mode 000000,100644..100644 --- a/doc/board/wexler/qc750.rst +++ b/doc/board/wexler/qc750.rst @@@ -1,0 -1,125 +1,125 @@@ + .. SPDX-License-Identifier: GPL-2.0+ + + U-Boot for the WEXLER QC750 tablet + ================================== + + ``DISCLAMER!`` Moving your WEXLER QC750 to use U-Boot assumes replacement + of the vendor bootloader. Vendor Android firmwares will no longer be able + to run on the device. This replacement IS reversible. + + Quick Start + ----------- + + - Build U-Boot + - Process U-Boot + - Flashing U-Boot into the eMMC + - Boot + - Self Upgrading + + Build U-Boot + ------------ + + .. code-block:: bash + + $ export CROSS_COMPILE=arm-linux-gnueabi- + $ make qc750_defconfig + $ make + + After the build succeeds, you will obtain the final ``u-boot-dtb-tegra.bin`` + image, ready for further processing. + + Process U-Boot + -------------- + + ``DISCLAMER!`` All questions related to the re-crypt work should be asked + in re-crypt repo issues. NOT HERE! + + re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form + usable by device. This process is required only on the first installation or + to recover the device in case of a failed update. + + Permanent installation can be performed either by using the tegrarcm or by + pre-loading just built U-Boot into RAM. + + Processing for the NV3P protocol + ******************************** + + .. code-block:: bash + + $ git clone https://gitlab.com/grate-driver/re-crypt.git + $ cd re-crypt # place your u-boot-dtb-tegra.bin here + $ ./re-crypt.py --dev qc750 + + The script will produce a ``repart-block.bin`` ready to flash. + + Processing for pre-loaded U-Boot + ******************************** + + The procedure is the same, but the ``--split`` argument is used with the + ``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready + to flash. + + Flashing U-Boot into the eMMC + ----------------------------- + + ``DISCLAMER!`` All questions related to tegrarcm should be asked in the proper + place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before! + + Permanent installation can be performed either by using the nv3p protocol or by + pre-loading just built U-Boot into RAM. + + Flashing with the NV3P protocol + ******************************* + + Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can + enter it either by using ``wheelie`` with the correct ``blob.bin`` file or by + pre-loading vendor bootloader with the Fusée Gelée. + + With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in + encrypted state in form, which can just be written RAW at the start of eMMC. + + .. code-block:: bash + + $ wheelie --bct qc750.bct --bl bootloader.bin + $ nvflash --resume --rawdevicewrite 0 1024 repart-block.bin + + When flashing is done, reboot the device. + + Flashing with a pre-loaded U-Boot + ********************************* + + U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently + U-Boot supports bootmenu entry fastboot, which allows to write a processed copy + of U-Boot permanently into eMMC. + + While pre-loading U-Boot, hold the ``volume down`` button which will trigger + the bootmenu. There, select ``fastboot`` using the volume and power buttons. + After, on host PC, do: + + .. code-block:: bash + + $ fastboot flash 0.1 bct.img + $ fastboot flash 0.2 ebt.img + $ fastboot reboot + + Device will reboot. + + Boot + ---- + + To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on + eMMC. Additionally, if the Volume Down button is pressed while booting, the + device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC + as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console + and update bootloader (check the next chapter). + + Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows -the user to use/partition it in any way the user desires. ++the user to use/partition it in any way the user desires. + + Self Upgrading + -------------- + + Place your ``u-boot-dtb-tegra.bin`` on the first partition of the MicroSD card + and insert it into the tablet. Enter bootmenu, choose update the bootloader + option with the Power button and U-Boot should update itself. Once the process + is completed, U-Boot will ask to press any button to reboot.