Diff for /wikisrc/ports/sandpoint/inststorcenter.mdwn between versions 1.3 and 1.4

version 1.3, 2015/09/04 22:30:35 version 1.4, 2015/09/05 17:57:37
Line 125  to be converted into regular RS232 level Line 125  to be converted into regular RS232 level
 you are not anxious using a soldering iron you find detailed  you are not anxious using a soldering iron you find detailed
 instructions how to build such a converter here:  instructions how to build such a converter here:
   
 -   Serial adapter for 3.3V TTL  -   [Serial adapter for 3.3V TTL](http://www.netbsd.org/ports/sandpoint/ttl2rs232.html)
   
 Make sure that the layout of the plug fits to the pinout of the  Make sure that the layout of the plug fits to the pinout of the
 StorCenter's serial header, as shown above.  StorCenter's serial header, as shown above.
Line 189  bootinfo list to the kernel. Line 189  bootinfo list to the kernel.
 The `altboot` boot loader has to be loaded and started using U-Boot.  The `altboot` boot loader has to be loaded and started using U-Boot.
 Usually there are three ways to invoke it:  Usually there are three ways to invoke it:
   
 -   loadb  -   **loadb** to load a binary file via serial line in kermit mode
     to load a binary file via serial line in kermit mode  -   **tftpboot** to load a binary file over the network with TFTP protocol
 -   tftpboot  
     to load a binary file over the network with TFTP protocol  
 -   start it from the flash memory  -   start it from the flash memory
   
 The last option is prefered once the installation is completed, but  The last option is prefered once the installation is completed, but
Line 200  obviously it is not possible for the fir Line 198  obviously it is not possible for the fir
 has set up the network interface, which we can use after configuring the  has set up the network interface, which we can use after configuring the
 `ipaddr` and `serverip` environment variables:  `ipaddr` and `serverip` environment variables:
   
     IOMEGA=>   <pre>
     IOMEGA=>   IOMEGA=&gt; <strong>setenv ipaddr 192.168.0.105</strong>
     IOMEGA=>   IOMEGA=&gt; <strong>setenv serverip 192.168.0.5</strong>
     Saving Environment to Flash...  IOMEGA=&gt; <strong>saveenv</strong>
     Un-Protected 1 sectors  Saving Environment to Flash...
     Erasing Flash...  Un-Protected 1 sectors
     . done  Erasing Flash...
     Erased 1 sectors  . done
     Writing to Flash... done  Erased 1 sectors
     Protected 1 sectors  Writing to Flash... done
   Protected 1 sectors
   </pre>
   
 Once you have set up TFTP and DHCP ([read below](#altboot_install)) you  Once you have set up TFTP and DHCP ([read below](#altboot_install)) you
 can download `altboot` like this:  can download `altboot` like this:
   
     IOMEGA=>   <pre>
     TFTP from server 192.168.0.5; our IP address is 192.168.0.105  IOMEGA=&gt; <strong>tftp 1000000 altboot.bin</strong>
     Filename 'altboot.bin'.  TFTP from server 192.168.0.5; our IP address is 192.168.0.105
     Load address: 0x1000000  Filename 'altboot.bin'.
     Loading: ###############  Load address: 0x1000000
     done  Loading: ###############
     Bytes transferred = 74732 (123ec hex)  done
   Bytes transferred = 74732 (123ec hex)
   </pre>
   
 Boot the INSTALL kernel with altboot  Boot the INSTALL kernel with altboot
 ------------------------------------  ------------------------------------
Line 247  NetBSD/sandpoint distribution and copy i Line 249  NetBSD/sandpoint distribution and copy i
 Then start the DHCP, NFS or TFTP server and boot the installation kernel  Then start the DHCP, NFS or TFTP server and boot the installation kernel
 from the firmware either with  from the firmware either with
   
     IOMEGA=>   <pre>
   IOMEGA=&gt; <strong>go 1000000 tftp:netbsd-INSTALL</strong>
   </pre>
   
 or from NFS:  or from NFS:
   
     IOMEGA=>   <pre>
   IOMEGA=&gt; <strong>go 1000000 nfs:netbsd-INSTALL</strong>
   </pre>
   
 Our bootloader configures the hardware, determines the IP address, loads  Our bootloader configures the hardware, determines the IP address, loads
 the kernel via network and launches it:  the kernel via network and launches it:
Line 335  the kernel via network and launches it: Line 341  the kernel via network and launches it:
   
 Just follow the usual procedure to install a NetBSD system.  Just follow the usual procedure to install a NetBSD system.
   
 Sandpoint installation window  <img src="//www.netbsd.org/images/ports/sandpoint/install_window.jpg" alt="Sandpoint installation window" /></td>
   
 Post installation steps  Post installation steps
 =======================  =======================
   
Line 344  standalone when switched on, without the Line 351  standalone when switched on, without the
 you have to modify the `bootcmd` in U-Boot's environment and write the  you have to modify the `bootcmd` in U-Boot's environment and write the
 `altboot.bin` binary to the Flash ROM.  `altboot.bin` binary to the Flash ROM.
   
 To find a suitable place in the Flash ROM you can use the `flinfo`  To find a suitable place in the Flash ROM you can use the **flinfo**
 command and look out for empty sectors `(E)`. On my StorCenter I have  command and look out for empty sectors `(E)`. On my StorCenter I have
 chosen `0xffe80000`. Replace that in all the following commands if you  chosen `0xffe80000`. Replace that in all the following commands if you
 have chosen a different address.  have chosen a different address.
Line 352  have chosen a different address. Line 359  have chosen a different address.
 Load `altboot.bin` into memory at `0x1000000` again, as explained above.  Load `altboot.bin` into memory at `0x1000000` again, as explained above.
 Then execute the following commands to write it to Flash ROM:  Then execute the following commands to write it to Flash ROM:
   
     IOMEGA=> protect off ffe80000 ffe9ffff  <pre>
     Un-Protected 2 sectors  IOMEGA=&gt; <strong>protect off ffe80000 ffe9ffff</strong>
     IOMEGA=> erase ffe80000 ffe9ffff  Un-Protected 2 sectors
   IOMEGA=&gt; <strong>erase ffe80000 ffe9ffff</strong>
     . done  
     Erased 2 sectors  . done
     IOMEGA=> cp.b 1000000 ffe80000 18000  Erased 2 sectors
     Copy to Flash... done  IOMEGA=&gt; <strong>cp.b 1000000 ffe80000 18000</strong>
     IOMEGA=> protect on ffe80000 ffe9ffff  Copy to Flash... done
     Protected 2 sectors  IOMEGA=&gt; <strong>protect on ffe80000 ffe9ffff</strong>
   Protected 2 sectors
   </pre>
   
 Finally adapt the `bootcmd` environment string to autoboot `altboot` and  Finally adapt the `bootcmd` environment string to autoboot `altboot` and
 start the `netbsd` kernel (which is the default name) from `wd0` on each  start the `netbsd` kernel (which is the default name) from `wd0` on each
 reboot:  reboot:
   
     IOMEGA=> setenv bootcmd cp.b ffe80000 1000000 18000\; go 1000000 wd0:  <pre>
     IOMEGA=> saveenv  IOMEGA=&gt; <strong>setenv bootcmd cp.b ffe80000 1000000 18000\; go 1000000 wd0:</strong>
     Saving Environment to Flash...  IOMEGA=&gt; <strong>saveenv</strong>
     Un-Protected 1 sectors  Saving Environment to Flash...
     Erasing Flash...  Un-Protected 1 sectors
     . done  Erasing Flash...
     Erased 1 sectors  . done
     Writing to Flash... done  Erased 1 sectors
     Protected 1 sectors  Writing to Flash... done
   Protected 1 sectors
   </pre>
   
 The `\` is important for `setenv` not to misinterpret the `;` as the end  The `\` is important for **setenv** not to misinterpret the `;` as the end
 of the command.  of the command.
   
 Have fun with your mini NetBSD server!  Have fun with your mini NetBSD server!

Removed from v.1.3  
changed lines
  Added in v.1.4


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb