cleaned up Makefiles and READMEs

blinker02/Makefile

@@ -3,11 +3,12 @@ ARMGNU ?= arm-none-eabi
 
 COPS = -Wall -O2 -nostdlib -nostartfiles -ffreestanding 
 
-all : kernel.img
+all : blinker02.hex blinker02.bin
 
 clean :
 	rm -f *.o
 	rm -f *.bin
+	rm -f *.hex
 	rm -f *.elf
 	rm -f *.list
 	rm -f *.img
@@ -18,13 +19,13 @@ novectors.o : novectors.s
 blinker02.o : blinker02.c
 	$(ARMGNU)-gcc $(COPS) -c blinker02.c -o blinker02.o
 
-kernel.img : memmap novectors.o blinker02.o 
+blinker02.elf : memmap novectors.o blinker02.o 
 	$(ARMGNU)-ld novectors.o blinker02.o -T memmap -o blinker02.elf
 	$(ARMGNU)-objdump -D blinker02.elf > blinker02.list
-	$(ARMGNU)-objcopy blinker02.elf -O binary kernel.img
-
-
-
 
+blinker02.bin : blinker02.elf
+	$(ARMGNU)-objcopy blinker02.elf -O binary blinker02.bin
 
+blinker02.hex : blinker02.elf
+	$(ARMGNU)-objcopy blinker02.elf -O ihex blinker02.hex
 

blinker02/README

@@ -1,17 +1,14 @@
 
 See the top level README for information on where to find the
 schematic and programmers reference manual for the ARM processor
-on the raspberry pi.
-
-Based on some web searches the gpio is based at address 0x20200000 not
-0x7E200000 as shown in the documentation.  I have to go figure that out.
+on the raspberry pi.  Also find information on how to load and run
+these programs.
 
 There is a free-running 64 bit timer, super easy to use, just read it.
 
 Based on a couple of experiments, without messing with anything it
 appears that the timer is runing at about a megahertz, 1 million ticks
-per second.  I am guessing it is divided down from the 700MHz somewhere,
-will dig deeper.
+per second.
 
 Hmm, there are comments in the manual about the system clock coming up
 at 250MHz.  I wonder if this system timer is 250MHz/256 = 0.976MHz.