BELK/BXELK Quick Start Guide
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
 For BELK 3.0.2 or older, please refer to the BELK Quick Start Guide in PDF format. |
Contents
BELK/BXELK Quick start guide[edit | edit source]
This page describes how to quickly start working with the BELK/BXELK kit. The following paragraphs will guide you through the setup and installation procedures.
Kit registration[edit | edit source]
|
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 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 here.
Target setup and first boot[edit | edit source]
This section describes how to quickly start Bora/BoraEVB and BoraX/BoraXEVB systems included in the BELK/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 BoraEVB/BoraXEVB board to an Ethernet LAN by plugging cable into connector J8, also denoted as ETH0 on BoraEVB and BORAX ETHERNET on BoraXEVB
- connect 12V power supply to JP2 or J7 connector, also denoted as PSU 12V
- insert the microSD card in the slot J21, also denoted as MICROSD.
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 Bora/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.
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 mmcblk0p2 partition of the 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.
TBD
[1] bootscript is used to do this task.
[2] This root file system has been generated by Yocto build system.
[3] The microSD card is bootable itself, as explained here.
Host setup and target software development[edit | edit source]
Please refer to this page.
Target configuration for the development stage (net_nfs)[edit | edit source]
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 here.
In DAVE Embedded Systems development kits, this configuration is generally denoted as net_nfs. 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).
Target configuration for standalone boot[edit | edit source]
Please refer to this page.
Recovery procedure[edit | edit source]
In case the target is not able to boot from NOR flash for any reason, this recovery procedure can be use to boot from microSD card.
