1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
.. SPDX-License-Identifier: GPL-2.0+
U-Boot for the Acer Iconia Tab A500
===================================
``DISCLAMER!`` Moving your Acer Iconia Tab A500 to use U-Boot assumes
replacement of the vendor Acer bootloader. Vendor Android firmwares will no
longer be able to run on the device. This replacement IS reversible if you have
backups.
Quick Start
-----------
- Build U-Boot
- Process U-Boot
- Flashing U-Boot into the eMMC
- Flashing U-Boot into the eMMC with NvFlash
- Boot
- Self Upgrading
Build U-Boot
------------
.. code-block:: bash
$ export CROSS_COMPILE=arm-none-eabi-
$ make picasso_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. You need to know your device
individual SBK to continue.
.. 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 a500 --sbk <your sbk> --split
where SBK has next form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
Flashing U-Boot into the eMMC
-----------------------------
``DISCLAMER!`` All questions related to fusee-tools 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 by pre-loading just built U-Boot into RAM.
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
according to fusee-tools README to continue.
Bootloader preloading is performed to device in APX/RCM mode connected to host
PC. This mode can be entered by holding ``power`` and ``volume up`` buttons on
turned off tablet connected to the host PC. Host PC should detect APX USB
device in ``lsusb``.
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. This is how U-Boot can be preloaded using
fusee-tools:
.. code-block:: bash
$ ./utils/nvflash_t20 --setbct --bct ./bct/picasso.bct --configfile ./utils/flash.cfg
--bl u-boot-dtb-tegra.bin --sbk <your sbk> --sync
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.
Flashing U-Boot into the eMMC with NvFlash
------------------------------------------
``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!
This method is discouraged and is used only if fastboot commands from previous
chapter failed with ``Writing '0.1' FAILED (remote: 'too large for partition')``
error. This error means that your tablet has 512 Kb boot0/boot1 partitons which
is too small to contain U-Boot image as the minimum boot partition size must
me 1 MB. This situation can be workarounded but self-update will not work and
flashing to eMMC will wipe U-Boot. This should not be a big issue since installing
OS on microSD is a preferred method anyway.
This method involves use of Nv3p. Nv3p is a custom Nvidia protocol used to
recover bricked devices. Devices can enter it by pre-loading vendor bootloader
into RAM with the nvflash.
With Nv3p, ``repart-block.bin`` is used (produced by re-crypt without ``--split``
key). It contains BCT and a bootloader in encrypted state in form, which can just
be written RAW at the start of eMMC. Place your ``repart-block.bin`` and vendor
bootloader with name ``bootloader.bin`` into fusee-tools folder and run:
.. code-block:: bash
$ ./utils/nvflash_t20 --setbct --bct ./bct/picasso.bct --configfile ./utils/flash.cfg
--bl ./bootloader.bin --sbk <your sbk> --sync
$ ./utils/nvflash_t20 --resume --rawdevicewrite 0 512 ./repart-block.bin
When flashing is done, reboot the device.
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 ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
allows 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.
|
