meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
documentation:client_side [2015/07/03 14:10] – micdocumentation:client_side [2016/11/03 14:24] (current) – removed vor
Line 1: Line 1:
-======PXE Client configuration====== 
  
-The clients have to be set up in order to boot from the PXE server and not from the internal flash storage or HHD.\\ 
-For CXP modules the network boot option in the BIOS has to be activated. In most cases that is enough.\\ 
- 
-The Apalis and Colibri modules must have an u-boot that supports booting over network (version and higher). 
-And some things ave to be set in the u-boot enviornmentals as described below. 
- 
-The u-boot can be reached by connecting a serial console to the module and then pressing any key when starting the module to abort the booting process. 
-=====Christmann Apalis Exynos===== 
- 
-Tested with **U-Boot 2015.07-rc1-00408-g012681b-dirty** 
- 
-The following variables have to be set in u-boot: 
-<code> 
-setenv usbethaddr 
-setenv nfsboot 'usb reset; dhcp; mmc dev 1; mmc read 22000000 3000 100; bootm 23e00000 - 22000000' 
-setenv bootcmd 'run nfsboot; usb start; mmc dev 1; mmc read 0x20008000 600 2700; mmc read 0x22000000 3000 100; bootm 0x20008000 - 0x22000000' 
-setenv bootargs 'root=/dev/nfs rw netdevwait console=ttySAC2,115200n8 init --no-log' 
-</code> 
- 
-:!: But it is necessary at the moment to have an SD card with the original Image, or with the flattend device tree blob at sector 3000 of teh SD card.\\ 
-:!: At the moment teh kernel stops bootin with ''drm_kms_helper: panic occurred, switching back to text console'' 
- 
-=====Toradex Apalis T30===== 
- 
-Tested with **U-Boot 2014.10** 
- 
-Only the option for ''nfsboot'' has to be added to the ''bootcmd'' in u-boot. 
-Note that in the following steps the MAC address has to be replaced with the actual address of the module.:!: 
- 
-If only network boot is desired the following commands have to be executet in the u-boot enviornment: 
-<code> 
-setenv serverip 
-setenv ipaddr 
-setenv ethaddr 00:14:2D:00:00:00 
-setenv nfsboot 'run setup; setenv bootargs ${defargs} ${nfsargs} ${setupargs} ${vidargs}; echo Booting via DHCP/TFTP/NFS...; dhcp ${kernel_addr_r} && bootm ${kernel_addr_r} - ${dtbparam}' 
-setenv bootcmd 'run nfsboot; echo; echo nfsboot failed' 
-saveenv 
-</code> 
- 
- 
-If the original bootorder should not be replaced the commands are the following: 
-<code> 
-setenv serverip 
-setenv ipaddr 
-setenv ethaddr 00:14:2D:00:00:00 
-setenv bootcmd 'run nfsboot; echo; echo nfsboot failed; run emmcboot; echo; echo emmcboot failed' 
-saveenv 
-</code> 
-But this will result in one error message ''*** ERROR: `serverip' not set'' because the module then trys to load a flash image from a server whos IP is not set in ''serverip''. 
- 
- 
-=====Toradex Colibri T20=====