[BACK]Return to instqnap.mdwn CVS log [TXT] [DIR] Up to [NetBSD Developer Wiki] / wikisrc / ports / sandpoint

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

version 1.3, 2015/09/04 22:30:35 version 1.4, 2015/09/05 17:48:55
Line 80  be converted into regular RS232 levels b Line 80  be converted into regular RS232 levels b
 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)
   
 Another option is to buy such a converter. There are solutions for a  Another option is to buy such a converter. There are solutions for a
 standard RS232 interface and for an USB interface. Look out for:  standard RS232 interface and for an USB interface. Look out for:
Line 137  bootinfo list to the kernel. Line 137  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 165  argument to `kermit`. Line 163  argument to `kermit`.
 Load `altboot` into memory with Kermit protocol. The binary is relocated  Load `altboot` into memory with Kermit protocol. The binary is relocated
 at 0x1000000, so type:  at 0x1000000, so type:
   
     =>   <pre>
     ## Ready for binary (kermit) download to 0x01000000 at 115200 bps...  =&gt; <strong>loadb 1000000</strong>
   ## Ready for binary (kermit) download to 0x01000000 at 115200 bps...
 Now quit your terminal program and launch `kermit cmdfile`. When you are  </pre>
 already running `kermit` enter the command mode by typing `CTRL-\`  
 followed by `C`. Then send `altboot.bin`. Reconnect when the transfer is  Now quit your terminal program and launch **kermit cmdfile**. When you are
   already running `kermit` enter the command mode by typing **CTRL-\\**
   followed by **C**. Then send `altboot.bin`. Reconnect when the transfer is
 finished.  finished.
   
     C-Kermit 8.0.211, 10 Apr 2004, for NetBSD 1.6  <pre>
      Copyright (C) 1985, 2004,  C-Kermit 8.0.211, 10 Apr 2004, for NetBSD 1.6
       Trustees of Columbia University in the City of New York.   Copyright (C) 1985, 2004,
     Type ? or HELP for help.    Trustees of Columbia University in the City of New York.
     (/tmp/) C-Kermit>  Type ? or HELP for help.
   (/tmp/) C-Kermit><strong>send path_to/altboot.bin</strong>
   </pre>
   
 Boot the INSTALL kernel with altboot  Boot the INSTALL kernel with altboot
 ------------------------------------  ------------------------------------
Line 204  NetBSD/sandpoint distribution and copy i Line 206  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
   
     =>   <pre>
   =&gt; <strong>tftp:netbsd-INSTALL</strong>
   </pre>
   
 or from NFS:  or from NFS:
   
     =>   <pre>
   =&gt; <strong>nfs:netbsd-INSTALL</strong>
   </pre>
   
 At the time of writing the network transfer will fail for the first time  At the time of writing the network transfer will fail for the first time
 after cold start. After an automatic reset, caused by five xmit  after cold start. After an automatic reset, caused by five xmit
Line 291  the kernel via network and launches it: Line 297  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 300  standalone when switched on, without the Line 307  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 Turbo Station I have  command and look out for empty sectors `(E)`. On my Turbo Station I have
 chosen `0xffe20000`. Replace that in all the following commands if you  chosen `0xffe20000`. Replace that in all the following commands if you
 have chosen a different address.  have chosen a different address.
Line 308  have chosen a different address. Line 315  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:
   
     => protect off ffe20000 ffe3ffff  <pre>
     Un-Protected 1 sectors  =&gt; <strong>protect off ffe20000 ffe3ffff</strong>
     => erase ffe20000 ffe3ffff  Un-Protected 1 sectors
     . done  =&gt; <strong>erase ffe20000 ffe3ffff</strong>
     Erased 1 sectors  . done
     => cp.b 1000000 ffe20000 18000  Erased 1 sectors
     Copy to Flash... done  =&gt; <strong>cp.b 1000000 ffe20000 18000</strong>
     => protect on ffe20000 ffe3ffff  Copy to Flash... done
     Protected 1 sectors  =&gt; <strong>protect on ffe20000 ffe3ffff</strong>
   Protected 1 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:
   
     => setenv bootcmd cp.b ffe20000 1000000 18000\; go 1000000 wd0:  <pre>
     => saveenv  =&gt; <strong>setenv bootcmd cp.b ffe20000 1000000 18000\; go 1000000 wd0:</strong>
     Saving Environment to Flash...  =&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