Blame view

buildroot/buildroot-2016.08.1/board/arm/juno/readme.txt 3.42 KB
6b13f685e   김민수   BSP 최초 추가
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
  ARM Juno r1/r0
  
  Intro
  =====
  
  These instructions apply to all models of the ARM Juno:
    - Juno r0 (does not support PCIe)
    - Juno r1 (supports PCIe)
    - Juno r2 (Big Cluster with A72)
  
  Buildroot will generate the kernel image, device tree blob and a
  minimal root filesystem.
  
  How to build it
  ===============
  
  Configure Buildroot
  -------------------
  
  Configuring Buildroot is pretty simple, just execute:
  
    $ make arm_juno_defconfig
  
  Build the rootfs, kernel and DTB
  --------------------------------
  
  Note: you will need to have access to the network, since Buildroot will
  download the packages' sources.
  
  You may now build your rootfs with:
  
    $ make
  
  (This may take a while)
  
  Result of the build
  -------------------
  
  After building, you should obtain this tree:
  
      output/images/
      +-- rootfs.tar
      +-- juno.dtb (if Juno r0 is used)
      +-- juno-r1.dtb (if Juno r1 is used)
      +-- juno-r2.dtb (if Juno r2 is used)
      +-- Image
  
  Preparing your rootfs
  ======================
  
  Format your pen drive as a ext3 filesystem by executing:
  
     $ mkfs.ext3 /dev/<your device>
  
  Installing your rootfs
  ======================
  
  After mounting the pen drive please execute the following:
  
     $ sudo tar -xvf output/images/rootfs.tar -C <pen drive mount path>
  
  When completed make sure to unmount the device:
  
     $ umount <pen drive mount path>
  
  Insert the pen drive in one of the ARM Juno' USB type A connectors.
  
  Configure *.dtb in the boot configuration for Juno r0
  =====================================================
  
  SITE1/HBI0262B/images.txt
  .....
  NOR3UPDATE: AUTO                 ;Image Update:NONE/AUTO/FORCE
  NOR3ADDRESS: 0x00C00000          ;Image Flash Address
  NOR3FILE: \SOFTWARE\juno.dtb     ;Image File Name
  NOR3NAME: board.dtb              ;Specify Image name to preserve file extension
  NOR3LOAD: 00000000               ;Image Load Address
  NOR3ENTRY: 00000000              ;Image Entry Point
  ......
  
  Configure *.dtb in the boot configuration for Juno r1
  =====================================================
  
  SITE1/HBI0262C/images.txt
  ......
  NOR3UPDATE: AUTO                 ;Image Update:NONE/AUTO/FORCE
  NOR3ADDRESS: 0x00C00000          ;Image Flash Address
  NOR3FILE: \SOFTWARE\juno-r1.dtb  ;Image File Name
  NOR3NAME: board.dtb              ;Specify target filename to preserve file extension
  NOR3LOAD: 00000000               ;Image Load Address
  NOR3ENTRY: 00000000              ;Image Entry Point
  ......
  
  Configure *.dtb in the boot configuration for Juno r2
  =====================================================
  
  SITE1/HBI0262D/images.txt
  ......
  NOR3UPDATE: AUTO                 ;Image Update:NONE/AUTO/FORCE
  NOR3ADDRESS: 0x02000000          ;Image Flash Address
  NOR3FILE: \SOFTWARE\juno-r2.dtb  ;Image File Name
  NOR3NAME: board.dtb              ;Specify target filename to preserve file extension
  NOR3LOAD: 00000000               ;Image Load Address
  NOR3ENTRY: 00000000              ;Image Entry Point
  ......
  
  Installing kernel image and DTB
  ===============================
  
  1. Connect to the ARM Juno UART0 and execute USB_ON in the terminal
  2. Connect a USB cable between your PC and ARM Juno USB type B connector
     A mass storage device should appear in your desktop.
  3. Open the software/ folder
  4. Copy the 'Image' file to software/
  5. Copy the 'juno-r1.dtb' (r1), 'juno.dtb' (r0) or juno-r2.dtb (r2) file to software/
  6. Press the red button in the front pannel of ARM Juno
  
  At this time, the board will erase the Flash entry for each new item and
  replace it with the lastest ones.