--- wikisrc/ports/sandpoint/instqnap.mdwn 2015/09/04 22:30:35 1.3 +++ wikisrc/ports/sandpoint/instqnap.mdwn 2015/09/05 17:48:55 1.4 @@ -80,7 +80,7 @@ be converted into regular RS232 levels b you are not anxious using a soldering iron you find detailed 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 standard RS232 interface and for an USB interface. Look out for: @@ -137,10 +137,8 @@ bootinfo list to the kernel. The `altboot` boot loader has to be loaded and started using U-Boot. Usually there are three ways to invoke it: -- loadb - to load a binary file via serial line in kermit mode -- tftpboot - to load a binary file over the network with TFTP protocol +- **loadb** to load a binary file via serial line in kermit mode +- **tftpboot** to load a binary file over the network with TFTP protocol - start it from the flash memory The last option is prefered once the installation is completed, but @@ -165,19 +163,23 @@ argument to `kermit`. Load `altboot` into memory with Kermit protocol. The binary is relocated at 0x1000000, so type: - => - ## Ready for binary (kermit) download to 0x01000000 at 115200 bps... - -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 +
+=> loadb 1000000
+## Ready for binary (kermit) download to 0x01000000 at 115200 bps...
+
+ +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. - C-Kermit 8.0.211, 10 Apr 2004, for NetBSD 1.6 - Copyright (C) 1985, 2004, - Trustees of Columbia University in the City of New York. - Type ? or HELP for help. - (/tmp/) C-Kermit> +
+C-Kermit 8.0.211, 10 Apr 2004, for NetBSD 1.6
+ Copyright (C) 1985, 2004,
+  Trustees of Columbia University in the City of New York.
+Type ? or HELP for help.
+(/tmp/) C-Kermit>send path_to/altboot.bin
+
Boot the INSTALL kernel with altboot ------------------------------------ @@ -204,11 +206,15 @@ NetBSD/sandpoint distribution and copy i Then start the DHCP, NFS or TFTP server and boot the installation kernel from the firmware either with - => +
+=> tftp:netbsd-INSTALL
+
or from NFS: - => +
+=> nfs:netbsd-INSTALL
+
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 @@ -291,7 +297,8 @@ the kernel via network and launches it: Just follow the usual procedure to install a NetBSD system. -Sandpoint installation window +Sandpoint installation window + Post installation steps ======================= @@ -300,7 +307,7 @@ standalone when switched on, without the you have to modify the `bootcmd` in U-Boot's environment and write the `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 chosen `0xffe20000`. Replace that in all the following commands if you have chosen a different address. @@ -308,31 +315,35 @@ have chosen a different address. Load `altboot.bin` into memory at `0x1000000` again, as explained above. Then execute the following commands to write it to Flash ROM: - => protect off ffe20000 ffe3ffff - Un-Protected 1 sectors - => erase ffe20000 ffe3ffff - . done - Erased 1 sectors - => cp.b 1000000 ffe20000 18000 - Copy to Flash... done - => protect on ffe20000 ffe3ffff - Protected 1 sectors +
+=> protect off ffe20000 ffe3ffff
+Un-Protected 1 sectors
+=> erase ffe20000 ffe3ffff
+. done
+Erased 1 sectors
+=> cp.b 1000000 ffe20000 18000
+Copy to Flash... done
+=> protect on ffe20000 ffe3ffff
+Protected 1 sectors
+
Finally adapt the `bootcmd` environment string to autoboot `altboot` and start the `netbsd` kernel (which is the default name) from `wd0` on each reboot: - => setenv bootcmd cp.b ffe20000 1000000 18000\; go 1000000 wd0: - => saveenv - Saving Environment to Flash... - Un-Protected 1 sectors - Erasing Flash... - . done - Erased 1 sectors - Writing to Flash... done - Protected 1 sectors +
+=> setenv bootcmd cp.b ffe20000 1000000 18000\; go 1000000 wd0:
+=> saveenv
+Saving Environment to Flash...
+Un-Protected 1 sectors
+Erasing Flash...
+. done
+Erased 1 sectors
+Writing to Flash... done
+Protected 1 sectors
+
-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. Have fun with your mini NetBSD server!