Difference between revisions of "Building U-Boot (BELK/BXELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
(Instructions)
Line 31: Line 31:
 
make bora_noflash
 
make bora_noflash
 
</pre>
 
</pre>
**:<code>bora_qspi</code>: this target is <u>available for BORA only</u>. U-Boot is built to use NOR flashed based environment.
+
:<code>bora_qspi</code>: this target is <u>available for BORA only</u>. U-Boot is built to use NOR flashed based environment.
**:<code>bora_mmc</code>: this target is <u>available for BORA only</u>. U-Boot environment is placed in SD/MMC card.
+
:<code>bora_mmc</code>: this target is <u>available for BORA only</u>. U-Boot environment is placed in SD/MMC card.
**:<code>bora_noflash</code>: this target is <u>available for BORA and BORAX</u>. U-Boot environment is placed in SD/MMC card. NOR flash and NAND flash are disabled.
+
:<code>bora_noflash</code>: this target is <u>available for BORA and BORAX</u>. U-Boot environment is placed in SD/MMC card. NOR flash and NAND flash are disabled.
 
* build U-Boot by issuing <code>make</code> command. This will generate U-Boot binary images.
 
* build U-Boot by issuing <code>make</code> command. This will generate U-Boot binary images.
  
 
Subsequent builds just require <code>make</code> command, without targets, to update the binary images. Once the build process is complete, the binary images can be copied to the tftp root directory (eg. <code>/srv/tftp/belk/</code>) with the following command: <code>cp u-boot.bin /srv/tftp/belk/</code>.
 
Subsequent builds just require <code>make</code> command, without targets, to update the binary images. Once the build process is complete, the binary images can be copied to the tftp root directory (eg. <code>/srv/tftp/belk/</code>) with the following command: <code>cp u-boot.bin /srv/tftp/belk/</code>.

Revision as of 13:11, 2 November 2015

Info Box
Bora5-small.jpg Applies to Bora
BORA Xpress.png Applies to BORA Xpress

History[edit | edit source]

Version Date BELK version Notes
1.0.0 November 2015 3.0.0 First release

Instructions[edit | edit source]

It is assumed that the development environment has been set up properly as described 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):

git clone git@git.dave.eu:dave/bora/u-boot-xlnx.git -b bora

  • Setup the server environment (please refer to this section)
  • enter the source tree directory and select the desired target by issuing one of the following commands:
make bora_qspi
make bora_mmc
make bora_noflash
bora_qspi: this target is available for BORA only. U-Boot is built to use NOR flashed based environment.
bora_mmc: this target is available for BORA only. U-Boot environment is placed in SD/MMC card.
bora_noflash: this target is available for BORA and BORAX. U-Boot environment is placed in SD/MMC card. NOR flash and NAND flash are disabled.
  • build U-Boot by issuing make command. This will generate U-Boot binary images.

Subsequent builds just require make command, without targets, to update the binary images. Once the build process is complete, the binary images can be copied to the tftp root directory (eg. /srv/tftp/belk/) with the following command: cp u-boot.bin /srv/tftp/belk/.