Differences

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

--- spiffchorder:using_the_atmega8 [2009/05/04 15:20] – priestdo
+++ spiffchorder:using_the_atmega8 [2023/02/09 23:32] (current) – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 If you like me, build the hex file, then program by using avrdude or some other program directly, or use the usb bootloader then you only need to make the first change below.
-===== Makefile changes =====
+===== 1 Makefile changes =====
-==== 1 - Change the MCU name ====
+==== 1.1 Change the MCU name ====
 Where for the ATmega168 it says:
@@ Line 20: / Line 20: @@
 </code>
-==== 2 - Change the fuse settings ====
+==== 1.2 Change the fuse settings ====
 If you are not using the usb bootloader and want to use the Makefile to program your chip, you will also need to change the fuse settings in the Makefile as follows.
@@ Line 34: / Line 34: @@
 </code>
-===== Prebuilt code with bootloader =====
+===== 2 Fuse Settings For the ATmega8 =====
+|               ^  hfuse ^  lfuse  |
+^  no bootloader|  0xD9  |  0x3F  |
+^ usb bootloader|  0xD8  |  0x3F  |
+===== 3 Prebuilt code with bootloader =====
 If you want to start by downloading a known working hexfile with the usb bootloader on it which you can then change by downloading your new program over the usb connection to your spiffchorder, you can begin with the hex file below
-==== Known working Spiffchorder for ATmega8 with usb bootloader in place ====
+==== 3.1 Known working Spiffchorder for ATmega8 with usb bootloader in place ====
@@ Line 45: / Line 52: @@
 ^ MD5 checksum| dc681522d0af047330e82347b6343b34  chorder-working-atmega8.hex|
-==== avrdude commands for above ATmega8 hex file ====
+==== 3.2 avrdude commands for above ATmega8 hex file ====
 When loading a hex image on to the atmega8 do: