@@ -30,17 +30,6 @@ Therefore, the first step is to fetch TI's fork:
3030
3131 git clone https://github.com/TexasInstruments/armbian-build.git
3232
33- .. ifconfig :: CONFIG_part_variant in ('AM62LX')
34-
35- .. note ::
36-
37- BeagleBadge is supported in Armbian but is not yet supported on **ti-main ** branch, therefore run the following command
38- before building for BeagleBadge:
39-
40- .. code-block :: console
41-
42- git checkout 2025.12-beaglebadge
43-
4433 Repository Structure
4534--------------------
4635
@@ -92,6 +81,12 @@ Armbian supports both an interactive UI and a noninteractive build process.
9281 sudo usermod -aG docker $USER
9382 newgrp docker
9483
84+ If the host machine is behind a proxy, be sure to set **at minimum ** the HTTP_PROXY environment variable prior to building:
85+
86+ .. code-block :: console
87+
88+ export HTTP_PROXY=http://<proxy_address>:<proxy_port>
89+
9590 - To build interactively:
9691
9792 .. code-block :: console
@@ -132,8 +127,9 @@ For a list of boards and branches supported by each SoC, refer:
132127 AM62-LP,sk-am62-lp,``config/boards/sk-am62-lp.conf``,"vendor, vendor-rt, vendor-edge, edge"
133128 AM62SIP,sk-am62-sip,``config/boards/sk-am62-sip.conf``,"vendor, vendor-rt, vendor-edge, edge"
134129 AM62Lx,tmds62levm,``config/boards/tmds62levm.conf``,"vendor, vendor-rt, vendor-edge"
135- AM62Lx,beaglebadge,``config/boards/beaglebadge.conf``,"vendor-edge"
130+ AM62Lx,beaglebadge,``config/boards/beaglebadge.conf``,"vendor, vendor-rt, vendor -edge"
136131 AM62Px,sk-am62p,``config/boards/sk-am62p.conf``,"vendor, vendor-rt, vendor-edge, edge"
137132 AM64x,sk-am64b,``config/boards/sk-am64b.conf``,"vendor, vendor-rt, vendor-edge, edge"
133+ AM64x,tmds64evm,``config/boards/tmds64evm.conf``,"vendor, vendor-rt, vendor-edge, edge"
138134
139135``output/images/ `` stores the built images. These images have a ``.img `` extension.
0 commit comments