Difference between revisions of "Booting the system via NFS (BELK/BXELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
(Created page with "{{InfoBoxTop}} {{Applies To Bora}} {{Applies To BoraX}} {{InfoBoxBottom}} == History == {| class="wikitable" border="1" !Version !Date !BELK version !Notes |- |1.0.0 |Novembe...")
 
 
(12 intermediate revisions by 4 users not shown)
Line 2: Line 2:
 
{{Applies To Bora}}
 
{{Applies To Bora}}
 
{{Applies To BoraX}}
 
{{Applies To BoraX}}
 +
{{Applies To BoraLite}}
 
{{InfoBoxBottom}}
 
{{InfoBoxBottom}}
  
Line 15: Line 16:
 
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|3.0.0]]
 
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|3.0.0]]
 
|First release
 
|First release
 +
|-
 +
|2.0.0
 +
|July 2017
 +
|[[Bora_Embedded_Linux_Kit_(BELK)#BELK_software_components|3.0.0, 4.0.0]]
 +
|Updates for BELK-4.0.0/BXELK-2.0.0
 
|-
 
|-
 
|}
 
|}
  
==Instructions==
+
<section begin=BELK/>
It is assumed that the development environment has been set up properly as described [[Build_system_(BELK)|here]].
+
==Booting the system via NFS==
 +
It is assumed that the development environment has been set up properly as described [[BORA_SOM/BELK-L/Development/Build_system|here]].
  
 
Assuming that:
 
Assuming that:
the CPU module is booting with a working FSBL and U-Boot image (either from flash NOR SPI or flash NAND or MicroSD card)
+
*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
+
*a kernel image is available and ready to be downloaded through tftp
the root file system has been uncompressed into a nfs share
+
*the root file system has been uncompressed into a nfs share
the system can boot using the net_nfs1 configuration, as described in
+
the system can boot using the <code>net_nfs</code>{{efn|The net_nfs configuration, besides setting the system for booting from the network, triggers a command (<code>program_fpga</code>) which loads the FPGA binary from TFTP and programs the bitstream.}} configuration, as described [[BORA_SOM/BELK-L/General/Booting_from_NFS|here]].
http://wiki.dave.eu/index.php/Booting_Linux_Kernel#Configuration_net_nfs
+
 
 +
{{notelist}}
  
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
+
<section end=BELK/>

Latest revision as of 14:53, 23 November 2021

Info Box
Bora5-small.jpg Applies to Bora
BORA Xpress.png Applies to BORA Xpress
BORALite-TOP.png Applies to BORA Lite

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


Booting the system via NFS[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.

  1. 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.