|
|
| Line 57: |
Line 57: |
| | | | |
| | ==Quick start guide== | | ==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.
| + | Please refer to [[BELK_Quick_Start_Guide|this page]]. |
| − | ===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. If you also wish to access git repositories containing source code, please follow the procedure described [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].
| |
| − | | |
| − | ===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:BoraX-BoraXEVB-1st-boot.jpg|thumb|center|600px|Target setup for first boot]]
| |
| − | | |
| − | | |
| − | Once power has been applied to the target, FSBL or U-boot SPL 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:BXELK-NOR-partitioning.png|thumb|center|350px|BXELK <= 1.0.1 NOR flash default partitioning]]
| |
| − | [[File:BXELK-2.0.0-NOR-partitioning.png|thumb|center|350px|BXELK-2.0.0 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]] [2], [3]. At the end of boot process, Linux shell shall be available on the serial console. Default boot process '''does not download any bitstream''' to the Programmable Logic.
| |
| − | | |
| − | 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.
| |
| − | | |
| − | [2] This root file system has been generated by [[Advanced_use_of_Yocto_build_system_(BELK/BXELK)|Yocto build system]].
| |
| − | | |
| − | [3] The microSD card is bootable itself, as explained [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|here]].
| |
| − | | |
| − | ===Host setup and target software development===
| |
| − | 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</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up.
| |
| − | | |
| − | For more information about how to set up and use TFTP and NFS servers, please refer to the following link [[Booting_the_system_via_NFS_(BELK/BXELK)|Booting the system via NFS (BELK/BXELK)]].
| |
| − | | |
| − | ===Target configuration for standalone boot===
| |
| − | Please refer to [[Standalone_boot_(BXELK)|this page]]. | |
| − | ===Recovery procedure===
| |
| − | In case the target is not able to boot from NOR flash for any reason, this [[System_boot_and_recovery_via_microSD_card_(BELK/BXELK)|recovery procedure]] can be use to boot from microSD card.
| |
| | | | |
| | ==Physical devices mapping== | | ==Physical devices mapping== |
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) for BELK <= 3.0.2 and BXELK <= 1.0.1
- build U-boot SPL for BELK-4.0.0 and BXELK-2.0.0
- build the 2nd-stage bootloader (U-Boot)
- build and run Linux operating system on 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 BoraX SOM and BoraXEVB
- source code of target software
- technical documentation (hardware manuals, mechanical drawings, reference schematics, application notes etc.)
Logical structure of BXELK[edit | edit source]
Please refer to this page.
Please refer to this page.
Please refer to this page.
Please refer to this page.
Please refer to this page.
Please refer to this page.
GET A QUOTE
ONLINE HELPDESK
