Difference between revisions of "Booting the system via NFS (BELK/BXELK)"
| Line 1: | Line 1: | ||
{{InfoBoxTop}} | {{InfoBoxTop}} | ||
{{Applies To Bora}} | {{Applies To Bora}} | ||
| + | {{Applies To BoraX}} | ||
| + | {{Applies To BoraLite}} | ||
{{InfoBoxBottom}} | {{InfoBoxBottom}} | ||
Revision as of 14:17, 15 October 2019
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
History[edit | edit source]
| Version | Date | BELK version | Notes |
|---|---|---|---|
| 1.0.0 | November 2015 | 3.0.0 | First release |
| 2.0.0 | July 2017 | 3.0.0, 4.0.0 | Updates for BELK-4.0.0/BXELK-2.0.0 |
Instructions[edit | edit source]
It is assumed that the development environment has been set up properly as described here.
Assuming that:
- the CPU module is booting with a working FSBL (or U-boot SPL for BELK-4.0.0/BXELK-2.0.0) and U-Boot image (either from flash NOR SPI or flash NAND or MicroSD card)
- a kernel image is available and ready to be downloaded through tftp
- the root file system has been uncompressed into a nfs share
the system can boot using the net_nfs[a] configuration, as described here.
- ↑ The net_nfs configuration, besides setting the system for booting from the network, triggers a command (
program_fpga) which loads the FPGA binary from TFTP and programs the bitstream.
