!BELK /BXELK version

|{{oldid|6723 |1.0.0}}

|[[Bora_Embedded_Linux_Kit_(BELK)/BXELK_software_components#BELK_software_componentsBELK_3.0.0|3.0.0/ N/A]]

<section begin=BELK/>=Instructions=Building U-Boot==It is assumed that the development environment has been set up properly as described [[Build_system_(BORA_SOM/BELK)-L/Development/Build_system|here]]. *start the Linux development server and login into the system*assuming that a local repository has not been created, clone the remote U-Boot git repository (the “-b” option is used to automatically checkout the current branch):<code>git clone git@git.dave.eu:dave/bora/u-boot-xlnx.git -b bora-4.x.x</code>*Setup the server environment (please refer to [[BORA_SOM/BELK-L/Development/Build_system#Pre-built_toolchain|this section 3.3.3.3]])*enter the source tree directory and run select the desired target by issuing one of the following commands:** For '''BELK <= 3.0.2''' and '''BXELK <= 1.0.1''': <pre>make bora_configbora_qspi_config &#10;make bora_mmc_config &#10;make bora_noflash_config</pre>** For '''BELK 4.0.0''' and '''BXELK 2.0.0''': <pre>makebora_qspi_defconfig &#10;make bora_mmc_defconfig &#10;make bora_noflash_defconfig &#10;make borax_qspi_defconfig &#10;make borax_mmc_defconfig &#10;make borax_noflash_defconfig</pre>** '''BELK 4.1.1''' or newer more targets have been added for BoraLite booting from NAND and for the former command selects the default BORA configuration which application note [[BELK-AN-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|AN006]] <pre>make bora_nand_defconfig &#10;make bora_mmc_an006_defconfig</pre> :<code>bora_qspi</code> and <code>borax_qspi</code>: U-Boot is built to use NOR flashed based environment. The resulting binary files are used to boot from SPI serial NOR Flashflash.:<code>bora_mmc</code> and <code>borax_mmc</code>: U-Boot environment is placed in SD/MMC card. The resulting binary files are used to boot from SD/MMC card. However, while the latter builds the uNOR flash and NAND flash are accessible.:<code>bora_noflash</code> and <code>borax_noflash</code>: U-Boot environment is placed in SD/MMC card. The resulting binary files are used to boot from SD/MMC card. NOR flash and NAND flash are disabled.:<code>bora_nand_defconfig</code>: U-Boot environment is placed on NAND flash.* build U-Boot by issuing <code>make</code> command. This will generate U-Boot binary images.** file extension <code>.elf</code> must be manually added on <code>u-boot</code> if ELF file is required (for example to build <code>boot.bin</code> for uSD) Subsequent builds just require ''<code>make'' </code> command, without targets, to update the binary images. Once  {{ImportantMessage|text=By default, BoraEVB and BoraXEVB are configured to boot from NOR flash. Consequently, the U-Boot image stored in the NOR flash is built with <code>bora_qspi_defconfig</code> and <code>borax_qspi_defconfig</code> configuration respectively.}}   In order to download them to the target via TFPT protocol, once the build process is complete, the binary images can be copied to the [[BORA_SOM/BORA_Evaluation_Kit/Getting_started/Connections_and_first_boot#Target_configuration_for_the_development_stage_.28net_nfs.29|tftp root directory ]] (ege. g. <code>/srvtftpboot/tftpbora/belk</code>) with the following commandcommands:* For '''BELK 4.0.0''' or newer and '''BXELK 2.0.0''' or newer::<pre>cp spl/boot.bin /tftpboot/bora/ &#10;cp u-boot.img /tftpboot/bora/</pre>* For '''BELK <= 3.0.2''' and '''BXELK <= 1.0.1''' ::<pre>cp u-boot.bin /srvtftpboot/tftpbora/</belkpre> <section end=BELK/>