blob: 08ae0e0e67600e3891cea9a3ec663e0a5ebfd7cc (
plain)
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
|
ZII VF610 Based Boards
======================
Building Barebox
----------------
To build Barebox for ZII VF610 based boards do the following:
.. code-block:: sh
make ARCH=arm CROSS_COMPILE=<ARM toolchain prefix> mrproper
make ARCH=arm CROSS_COMPILE=<ARM toolchain prefix> zii_vf610_dev_defconfig
make ARCH=arm CROSS_COMPILE=<ARM toolchain prefix>
Uploading Barebox via JTAG
--------------------------
Barebox can be bootstrapped via JTAG using OpenOCD (latest master) as
follows:
.. code-block:: sh
cd barebox
Documentation/boards/imx/zii-vf610-dev/bootstrap.sh
A custom OpenOCD binary and options can be specified as follows:
.. code-block:: sh
OPENOCD="../openocd/src/openocd -s ../openocd/tcl " \
Documentation/boards/imx/zii-vf610-dev/bootstrap.sh
Writing Barebox to NVM
----------------------
With exception of Dev boards, all of ZII's VF610 based boards should
come with eMMC. To permanently write Barebox to it do:
.. code-block:: sh
barebox_update -t eMMC -y barebox.img
This should also automatically configure your board to boot that
image. Note that the original ZII stack's bootloader in eMMC should be
left intact. Barebox is configured to be programmed to one of the MMC boot
partitions, whereas the original bootloader is located in user partition.
To restore the board to booting using the original bootloader do:
.. code-block:: sh
detect mmc0
mmc0.boot=disabled
|
