Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
__FORCETOC__
==Introduction==
From the software standpoint, [[Bora Embedded Linux Kit (BELK)|Bora Embedded Linux Kit (BELK)]] and [[BoraX_Embedded_Linux_Kit_(BXELK)|BoraX Embedded Linux Kit (BXELK)]] are built on top of Zynq Linux BSP released by Xilinx. Customization Customizations are added to support for the Bora and BoraX platforms, in particular at bootloader and Linux kernel levels. BELK and BXELK share the '''same''' software modules, even if they are based on different hardware platforms.
Reading of [[Host_setup_and_development_flow_(BXELK)|this document]] is strongly recommended to understand the logical structure of the kits and how the software components are related.
**U-Boot SPL: <code>boot.bin</code>
**U-Boot: <code>u-boot.img</code>
**Fpga [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA Bitstream]]: <code>fpga.bit</code>
**Linux kernel: <code>uImage</code>
**Device tree: <code>bora.dtb</code>}}
| mksd.sh || [[mirror:bora/belk-4.0.0/mksd.sh|mksd.sh]] || [[mirror:bora/belk-4.0.0/mksd.sh|mksd.sh]]
|-
| [[Working_with_the_Yocto_build_system#bootscript |bootscript]] || [[mirror:bora/belk-4.0.0/boot.scr|boot.scr]] || [[mirror:bora/belk-4.0.0/boot.scr|boot.scr]]
|-
| U-Boot SPL (for uSD boot)|| [[mirror:bora/belk-4.0.0/belk-4.0.1_bora_mmc_boot.bin|boot.bin]] || [[mirror:bora/belk-4.0.0/belk-4.0.1_borax_mmc_boot.bin|boot.bin]]
| U-Boot (for NOR flash boot)|| [[mirror:bora/belk-4.0.0/belk-4.0.1_bora_qspi_u-boot.img|u-boot.img]] || [[mirror:bora/belk-4.0.0/belk-4.0.1_borax_qspi_u-boot.img|u-boot.img]]
|-
| Fpga [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA Bitstream ]] || [[mirror:bora/belk-4.0.0/belk-4.0.0_bora_fpga.bit|fpga.bit]] || [[mirror:bora/belk-4.0.0/belk-4.0.0_borax_fpga.bit|fpga.bit]]
|-
| Linux kernel || [[mirror:bora/belk-4.0.0/belk-4.0.0_uImage|uImage]] || [[mirror:bora/belk-4.0.0/belk-4.0.0_uImage|uImage]]
| mksd.sh || [[mirror:bora/belk-3.0.2/mksd.sh|mksd.sh]] || [[mirror:bora/bxelk-1.0.1/mksd.sh|mksd.sh]]
|-
| [[Working_with_the_Yocto_build_system#bootscript |bootscript]]|| [[mirror:bora/belk-3.0.2/boot.scr|boot.scr]] || [[mirror:bora/bxelk-1.0.1/boot.scr|boot.scr]]
|-
| FSBL (QSPI) || [[mirror:bora/belk-3.0.2/belk-3.0.0_bora_fsbl.bin|fsbl.bin]] || [[mirror:bora/bxelk-1.0.1/belk-3.0.0_borax_fsbl.bin|fsbl.bin]]
** For '''BELK 4.0.0''' or newer and '''BXELK 2.0.0''' or newer:
***<code>boot.bin</code> u-boot SPL image
***<code>fpga.bit</code> optional Fpga [[BELK-AN-008:_Programming_the_FPGA_Bitstream_with_U-Boot|FPGA bitstream]]
***<code>u-boot.img</code> u-boot image
***U-Boot <code>boot.scr</code> bootscript
*an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target.
bootscript and root file system are used to boot the target as described in [[BoraX_Embedded_Linux_Kit_(BXELK)BELK/BXELK_Quick_Start_Guide#Target_setup_and_first_boot|this section]].
It is worth remembering that the microSD card is [[System boot and recovery via microSD card (BELK/BXELK)|bootable]] and U-Boot environment is retrieved from (and stored to with <code>saveenv</code>) into the FAT partition as <code>bora.env</code>
!Description
|-
|10001
|BoraEVB
|External DDR3 bank (BoraEVB only)
|DDR3 bank can be populated on request. For more details please refer to [mailto:sales@dave.eu Sales Department].
|-
|20002
|BoraEVB/BoraXEVB
|ETH1 interface
|Please refer to [[AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB|this application note]] for second Ethernet interface support.
|-
|30003
|BoraEVB/BoraXEVB
|RTC
|Date/time retention is limited to about 4 hours.
|-
|40004
|MVM
|MVM Eclipse cross-toolchain configuration
otherwise, the SDK can be updated for fixing this issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file
|-
|50005
|MVM
|MVM Eclipse gdb remote debug
This issue will be fixed in next BELK/BXELK release. The SDK can be updated for fixing this issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file
|-
|60006
|MVM
|Cross-building environment
