Bureaucrats, dave_user, Administrators
8,154
edits
Changes
m
{{WorkInProgress}}
U0007 moved page FAQs (Bora/BoraX) to FAQs (Bora/BoraX/BoraLite)
{{InfoBoxTop}}
{{Applies To Bora}}
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{InfoBoxBottom}}
| [[:Category:Bora|Bora category page]] || This page lists all the wiki pages regarding the Bora CPU module
|-
| [[Bora_SOM :Category:Bora| Bora SOMcategory page]] || This page reports Bora SOM specification and basic information
|-
| [[Hardware_Manual_(Bora) | Bora Hardware Manual]] || This page points to the Bora Hardware Manual
= Using BELK =
=== Q: It there a Board Support Package (BSP) for the Bora SOM? How is it integrated in Vivado? ===
'''A''': BELK has been built around Vivado but some deviations from the default development approach suggested by Xilinx have been introduced, in order to push the modularization and the maintainability of the projects to the maximum extent. We recommend reading the [[BELK#Logical_structure_of_Bora_Embedded_Linux_Kit_.28BELK.29 | Logical structure of Bora Embedded Linux Kit]] page and the "BELK Quick Start Guide" document.
=== Q: I've received the BELK package. How am I supposed to start working with it? ===
=== Q: How can I update the BELK version? ===
'''A''': All BELK source trees (FPGA project, U-Boot and Linux kernel) are provided as git repositories. This means that these components can be kept in sync and up to date with '''DAVE Embedded Systems''' repositories.
Once the a git account is enabled, the developer can clone the repository and synchronize a source tree using git commands. For further details, please refer to section 3.3.3.5 of the '''BELK Quick Start Guide'''or visit the [[Bora_Embedded_Linux_Kit_(BELK)#How_to_update_BELK | How to update BELK]] page. === Q: I'm a Windows user. Can I use Git? How can I create the ssh RSA key? ==='''A''': The recommended Git tool for Windows is MsysGit (http://msysgit.github.io/). For detailed information, please refer to https://github.com/msysgit/msysgit/wiki. Please visit https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Git for some hints on how to set up SSH for GIT. A simple Windows tool for generating the SSH RSA keys is PuTTYgen, which is part of the PuTTY project (http://www.chiark.greenend.org.uk/~sgtatham/putty/). Please refer to the official documentation (http://the.earth.li/~sgtatham/putty/0.63/htmldoc/Chapter8.html#pubkey-puttygen) for further details. For a quick guide, please visit this page: http://katsande.com/using-puttygen-to-generate-ssh-private-public-keys.
=== Q: Where can I found the BELK Quick Start Guide document? ===
=== Q: Can I use Bora in an Asymmetric Multi Processing (AMP) configuration? ===
'''A''': Yes, Zynq processor can be configured to run independent software stacks on each of its processor cores. BELK owners can get access to an application note that describes how to build the software components required to run a simple application on FreeRTOS running on the second Zynq core, while Linux runs on the first Zynq core.Please refer to [[BELK-AN-001:_Asymmetric_Multiprocessing_(AMP)_on_Bora_–_Linux_FreeRTOS |Asymmetric Multiprocessing (AMP) on Bora – Linux FreeRTOS]]
=== Q: I've just installed the tools on Linux and when I launch the "vivado" command, the build procesess fails. How can I solve this problem? ===
* has a proper subnet IP address
For detailed information, please refer to [[Booting_Linux_Kernel#Configuration_net_nfs | Configuration net_nfs]]
=== Q: What if NAND/NOR flash is ''unverified'' according to Xilinx classification? ===
Bora SOM may be equipped with a NAND or NOR flash devices that are tagged as ''Unverified'' according to Xilinx nomenclature (see [http://www.xilinx.com/support/answers/50991.html here] and [http://www.xilinx.com/support/answers/63798.html here] for more details). All DAVE Embedded Systems SOMs are built upon devices - including but not limited to NAND and NOR flashes - that are submitted to severe qualification process, '''whether or not they previously have been verified by the system-on-chip manufacturer''' (Xilinx in this case).
The qualification process is based on internal procedures that are extensively used and tested across different embedded platforms and operating systems. These procedures are continuously updated to keep pace with technology evolution and are relentlessly improved according to data collected from products installed and operating on the field.
