Open main menu

DAVE Developer's Wiki β

Changes

BoraX Embedded Linux Kit (BXELK)

1,645 bytes removed, 31 January
no edit summary
{{Applies To BoraX}}
{{InfoBoxBottom}}
==Introduction==
{{ObsoleteWikiPage|link=DESK-XZ7-L}}
[[File:TBD{{ImportantMessage|text='''For BXELK 1.0.1 or older, the boot process was based on the FSBL+second-stage bootloader (U-Boot) combination. From BXELK 2.0.0 on, the boot process is based on the first-stage bootloader (U-Boot SPL)+second-stage bootloader (U-Boot) combination.png|thumb|center|100px|BoraX SOM]]'''}}
<section begin="Unboxing" />
==Unboxing==
 
[[File:BORA_Xpress.png|thumb|center|400px|BoraX SOM]]
 
 
BoraX Embedded Linux Kit (BXELK for short) provides all the necessary components required to set up the developing environment for:
* building the first-stage bootloader:
**FSBL for BXELK 1.0.1 or older
**U-boot SPL for BXELK 2.0.0 or newer
* building the second-stage bootloader (U-Boot)
* building and running Linux operating system on [[BORA_Xpress_SOM|BORA Xpress SOM]]
* building and debugging applications that will be executed on top of Yocto-based Linux distribution running on the target.
BoraX Embedded Linux Kit (BXELK for short) provides all the necessary components required to set up the developing environment to:
* build the first-stage bootloader (FSBL)
* build the 2nd-stage bootloader (U-Boot)
* build and run Linux operating system on [[:Category:BoraX|BoraX system-on-module (SOM)]]
* build and debug applications that will be executed on top of Yocto-based Linux distribution running on the target.
The main kit components are:
* hardware platform, composed by [[:Category:BoraXBORA_Xpress_SOM|BoraX BORA Xpress SOM]] and [[BoraXEVBBORA_Xpress_SOM/BORA_Xpress_Evaluation_Kit | BORA Xpress Evalutation kit]]* source code of target software
* technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)
<section end="Unboxing" />
<section begin="Kit Content" />
==Kit contentcontents== {| class="wikitable" style="margin: auto;"
|-
!Component
!Notes
|-
|style="text-align: center;" | [[File:TBDBORA_Xpress.png|60px]]|BoraX [[BORA Xpress SOM|BORA Xpress]] SOM (p/n DBXF4110D2RDBXF4110S2R)<br>
*SoC: Xilinx XC7Z030 (866Mhz, Speed "-3", Tj 0-100°C)
*SDRAM: 1 GB DDR3
*NAND: 1GB (SLC)
|
* For more details, please refer to the[[BORA_Xpress_SOM/BORA_Xpress_Hardware | BORA Xpress Hardware Manual]]
* By default, ARM cores frequency is set to 667 MHz and the [[Creating and building example Vivado project (BELK/BXELK)|example Vivado project]] is implemented for a "-1" device. This choice makes the software released with the kit compatible with possible variants based on different SoM models. In this regard, see also the [[#Order codes|order codes section]].
|-
|style="text-align: center;" | [[File:TBDBoraXEVB-01.png|40px60px]]|[[BoraXEVBBORA_Xpress_SOM/BORA_Xpress_Evaluation_Kit | BORA Xpress]] carrier Carrier board
|
|-
|style="text-align: center;" | [[File:Alimentatore.jpg|40px]]
|AC/DC Single Output Wall Mount adapter<br>
Output: +12V – 2.0 A
|
|-
|style="text-align: center;" | [[File:ProdSDC-MBLY-thumb.png|50px]]|MicroSDHC microSDHC card with SD adapter and USB adapter
|
|-
|}
 
===Order codes===
{| class="wikitable" style="margin: auto;"
|+
!Order code
!Description
|-
|BXELK-H-S
|This code refers to the default configuration detailed above
|-
|BXELK-H-S-D
|This variant is like BELK-L-S, except the SOM, which is DBXD4110S2R.
|}
<section end="Kit Content" />
==Logical structure of BXELK==
==Quick start guide==
This chapter describes how to quickly start working with the BXELK kit. The following paragraphs will guide you through the setup and installation procedures.===Kit registration==={{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.}} Please register your development kit by sending an email to [mailto:support-bora@dave.eu support-bora@dave.eu], providing the kit P/N and CODE. ===Target setup and first boot===This section describes how to quickly start BoraX/BoraXEVB system included in the BXELK:*on target side, connect a null-modem cable on J17 DB9 connector, denoted also as UART1*on host side, connect the other end of the null-modem cable to a COM port and start your favorite terminal software that will be used to interact with the target's serial console; communication parameters are 115200-8-N-1*optionally connect the BoraXEVB board to an Ethernet LAN by plugging cable into connector J8, also denoted as BORAX ETHERNET*connect 12V power supply to JP2 connector, also denoted as PSU 12V JACK*insert the microSD card in the slot J21, also denoted as MICROSD.  [[File:TBD.png|thumb|center|600px|Target setup for first boot]]  Once power has been applied to the target, FSBL and U-Boot bootloaders will be fetched from the SPI NOR flash that equips BoraX SOM and executed. Boot messages will be printed out to the serial console. Redundant U-Boot environment is stored in the NOR flash as well, as depicted in the following image.  [[File:TBD.png|thumb|center|350px|NOR flash default partitioning]]  By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#BXELK microSD Layout|microSD card itself]]. At the end of boot process, Linux shell shall be available on the serial console. The following dump shows the typical messages printed out to the console during bootstrap process.<pre class="mw-collapsible mw-collapsed">TBD</pre>   [1] <code>bootscript</code> is used to do this task. ===Host setup===Please refer to [[Host setup and development flow (BXELK)|this page]]. ===Target configuration for the development stage (<code>net_nfs</code>)===During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:*retrieve binary images (i.e. Linux kernel) via TFTP protocol*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs<BELK/code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]]. For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].===Target configuration for standalone boot===Please refer to [[Standalone_boot_(BXELK)BXELK_Quick_Start_Guide|this page]].
==Physical devices mapping==
Please refer to [[Physical_devices_mapping_(BELK/BXELK)|this page]].
==Advanced topics==
===Debugging with Eclipse===
Please refer to [[Debugging with Eclipse (MVM)|this page]].
===ConfigID feature===
Please refer to [[ConfigID_management_(BELK/BXELK)|this page]].
U0007
Bureaucrats, dave_user, Administrators
8,226
edits
Retrieved from "https://wiki.dave.eu/index.php/Special:MobileDiff/6382...20050"