Differences

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

--- arduino:arduino_without_a_bootloader [2021/04/22 00:50] – [Hardware] mithat
+++ arduino:arduino_without_a_bootloader [2021/04/22 00:53] – [Procedures] mithat
@@ Line 39: / Line 39: @@
 </WRAP>
 ===== Procedures =====
-As is the case when uploading a program to your Arduino using a bootloader, when uploading a program using a programmer you must specify what the target board is. So when doing any of the following, make sure //Tools > Board// and //Tools > Processor// (or other board options) are set correctly for your board.
+As is the case when uploading a program to your Arduino using a bootloader, when uploading a program using a programmer you must specify what the target board is. So when doing the following, make sure //Tools > Board// and //Tools > Processor// (or other board options) are set correctly for your board.
 Now is also a good time to mention a significant caveat about using a programmer as described here. <WRAP center round important 80%>
-Using a programmer involves making connections between the programmer and the Arduino's RST, SCK, MOSI, and MISO pins. If these pins are not used in your application, then programming should be a breeze.
+Using a programmer involves making connections between the programmer and the Arduino's RST, SCK, MOSI, and MISO pins. If these pins are not used in your application, then programming should be a breeze. However, if these pins //are// used (e.g. for SPI), then you will probably need to disconnect those connections when you are uploading programs.
-However, //if these pins are used (e.g. for SPI), then you will probably need to disconnect those connections when you are uploading programs!//
 </WRAP>
-Yes, this is yet another way the bootloader makes your life simpler.
+This can be bit of a drag and is yet another way the bootloader makes your life simpler.
 With that out of the way, let's move on to some specific cases.