Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Known Limitations
The following table details the software modules of BELK/BXELK releases.
{| class="wikitable"
!colspan="10" | Kit composition
|-
|'''Release number'''<br>BELK<br>BXELK
|-
|'''Drivers'''
|valign="top" | -|valign="top" | -|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]|valign="top" | Gigabit Eth #0<br>UART<br>NOR<br>NAND<br>SD/MMC<br>USB Host/Device<br>RTC<br>CAN<br>I2C<br>[[ConfigID_and_UniqueID | ConfigID]]
|-
|'''Vivado version'''
|valign="top" | 2013.2|valign="top" | 2013.3|valign="top" | 2013.3|valign="top" | 2013.3|valign="top" | 2014.4|valign="top" | 2014.4|valign="top" | 2014.4|valign="top" | 2014.4|valign="top" | 2017.1
|-
|'''Build System'''
|valign="top" | -|valign="top" | -|valign="top" | -|valign="top" | Yocto Daisy (1.6)|valign="top" | Yocto Daisy (1.6)|valign="top" | Yocto Daisy (1.6)|valign="top" | Yocto Daisy (1.6)|valign="top" | Yocto Daisy (1.6)|valign="top" | Yocto Morty (2.2)
|-
|'''[[Managed Virtual Machine (MVM)]]'''
{| class="wikitable"
|-
! rowspan="2" |Image !! colspan="1" |BELK version !! colspan="1" |BXELK version
|-
| 4.0.0 || 2.0.0
|Root File System || [[mirror:bora/belk-4.0.0/belk-4.0.0_bora-image-devel-bora.tar.gz|bora.tar.gz]] || [[mirror:bora/belk-4.0.0/belk-4.0.0_bora-image-devel-bora.tar.gz|bora.tar.gz]]
|}
{| class="wikitable"
|-
! rowspan="2" |Image !! colspan="1" |BELK version !! colspan="1" |BXELK version
|-
| 3.0.2 || 1.0.1
|Root File System || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora-image-devel-bora.tar.gz|bora.tar.gz]] || [[mirror:bora/belk-3.0.2/belk-3.0.2_bora-image-devel-bora.tar.gz|bora.tar.gz]]
|}
{| class="wikitable"
|-
! rowspan="2" |Image !! colspan="1" |BELK version !! colspan="1" |BXELK version
|-
| 3.0.1 || 1.0.0
{| class="wikitable"
|-
!IssueID!Component!Subsystem
!Description
|-
|1
|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].
|-
|2
|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.
|-
|3
|BoraEVB/BoraXEVB
|RTC
|Date/time retention is limited to about 4 hours.
|-
|4
|MVM
|MVM Eclipse cross-toolchain configuration
|Cross-toolchain configuration in Eclipse in the BELK MVM cannot be saved correctly.<br/>To fix the problem the following commands must be issued in the MVM terminal:
<pre>
cd /home/dvdk/bora/sdk/belk-4.0.0/sysroots/
</pre>
otherwise, the SDK can be updated for fixing this issues issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file
|-
|5
|MVM
|MVM Eclipse gdb remote debug
|Remote debug of an application using Eclipse and gdb is not working due to an issue with the Yocto SDK included in the BELK/BXELK MVM.
This issue will be fixed in next BELK/BXELK release. The SDK can be updated for fixing this issues issue using [https://mirror.dave.eu/bora/belk-4.0.0/belk-4.0.1_sdk.sh this] file|-|6|MVM|Cross-building environment|The script ~/env.sh dows not set the CC variable properly.To fix this, please comment out the following line: export CC=gcc
|-
|}
|-
|}
=== BELK 3.0.1 / BXELK 1.0.0 ===
