Documentation edits

Wiki/CompilingOptiboot.md

@@ -27,20 +27,19 @@ make <platform>  <options>
 ~~~~
 Where <platform> is one of the named chips or boards implemented as normal targets in the makefile (ie "atmega328".) (the order may be reversed.) The implemented <options> include:
 
-  * AVR_FREQ=nnnnnn  --  Use CPU frequency as specified (default: target dependent, but usually 16000000L)
-  * BAUD_RATE=nnnnn  --  Use an alternate bitrate (default: usually 115200)
-  *
-  * LED=\<portpin\>  --  Like "LED=B5" or "LED=L5"; which LED to flash.
-  * LED\_START\_FLASHES=n  -- number of flashes to emit when the bootloader executes (default 3)  Setting this to 0 omits the LED-flashing code and saves some space.
-  * LED\_START\_ON  -- Turn on the LED when the bootloader starts.  A smaller alternative to LED_START_FLASHES.
-  * LED\_DATA\_FLASH  -- flash the LED in the data receive function as well as at bootloader startup.
-  *
-  * SOFT_UART=1  --  use a bit-banged Software Uart.  Required for chips without a HW UART.
-  * SINGLESPEED=1  -- Operate the UART in single-speed mode.
-  * UART=n  -- user UARTn instead of UART0.
-  *
-  * BIGBOOT=1 -- include extra features that cause the bootloader to grow to between 512 and 1024 bytes.
-  * SUPPORT_EEPROM=1 -- try to include EEPROM read/write support, without other BIGBOOT features.
+  * **AVR\_FREQ=nnnnnn**  --  Use CPU frequency as specified (default: target dependent, but usually 16000000L)
+
+  * **BAUD\_RATE=nnnnn**  --  Use an alternate bitrate (default: usually 115200)<br>
+  * **SINGLESPEED=1**  -- Operate the UART in single-speed mode.
+  * **UART=n**  -- user UARTn instead of UART0.
+  * **SOFT_UART=1**  --  use a bit-banged Software Uart.  Required for chips without a HW UART.
+  * **LED=\<portpin\>**  --  Like "LED=B5" or "LED=L5" - which LED to flash.
+  * **LED\_START\_FLASHES=n**  -- number of flashes to emit when the bootloader executes (default 3)  Setting this to 0 omits the LED-flashing code and saves some space.
+  * **LED\_START\_ON**  -- Turn on the LED when the bootloader starts.  A smaller alternative to LED\_START\_FLASHES.
+  * **LED\_DATA\_FLASH=1 ** -- flash the LED in the data receive function as well as at bootloader startup.
+  * **BIGBOOT=1** -- include extra features that cause the bootloader to grow to between 512 and 1024 bytes.
+  * **SUPPORT\_EEPROM=1** -- try to include EEPROM read/write support, without other BIGBOOT features.
+  * **NO\_APP\_SPM=1** -- Omit the code tat allows applications to have Optiboot execute an SPM instruction (for writing to flash.)
 
 For example:
 

Wiki/Virtual-Boot-Partition.md

@@ -10,20 +10,17 @@
  Bootloader assumes that start of application is typical vector table generated by most compilers. When Optiboot change start vector, it saves original jump to another free vector. Typically it uses SPM_RDY vector, or WDT if SPM_RDY is unavailable.
  
   1. I have chip without SPM_RDY and I need to use WDR vector in my code.<br>
- It's possible to assign arbitrary vector using additional option to CFLAGS: `-Dsave_vect_num=xxx` where xxx could be name of vector like `EE_RDY_vect_num` (see virboot8 target in Makefile) or even just number (see attiny84 target in Makefile.extras). In fact, any number could be used, even outside vector table. There is only one limitation: it **MUST** be located in first flash page!
+ It's possible to use an arbitrary vector by adding an additional option to CFLAGS: `-Dsave_vect_num=xxx` where xxx could be name of vector like `EE_RDY_vect_num` (see virboot8 target in Makefile) or even just number (see attiny84 target in Makefile.extras). In fact, any number could be used, even outside vector table. There is only one limitation: it **MUST** be located in first flash page!
  
-  1. I don't use a vector table. Can I use it anyway?<br? 
+  1. I don't use a vector table. Can I use this anyway?<br> 
  Yes, as long as first instruction is **jmp** on chips with more than 8KB memory or **rjmp** on smaller memory devices. You must also provide another jump to store old jump by Optiboot.<br>  
-  It could be done for example by adding `-Dsave_vect_num=1` to CFLAGS during compiling bootloader, and making beginning of application like this:
-  
-  ~~~~
-    rjmp app
-    rjmp nowhere
-  app:
-    ... ;your code here
-  ~~~~
+  It could be done for example by adding `-Dsave_vect_num=1` to CFLAGS during compiling bootloader, and making beginning of application like this: <br>  
+&nbsp;&nbsp;&nbsp; `    rjmp app`<br>
+&nbsp;&nbsp;&nbsp;`    rjmp nowhere`<br>
+`  app:`<br>
+&nbsp;&nbsp;&nbsp;`    ... ;your code here`<br>
 
-  1. I want to add VBP to chip XXX<br>
+  1. How do I add VBP to chip XXX<br>
  Check Makefile targets **virboot8**, **virboot328** or **attiny84** for examples.<br>
  There are 2 things required:<br>
  Add `-DVIRTUAL_BOOT_PARTITION` to CFLAGS<br>