Merge pull request #3 from oilulio/restructure

Restructured core (unchanging) app layer routines into applicationCore.c

Author: oilulio

Makefile

@@ -12,7 +12,7 @@ OBJDUMP = $(AVRPATH)\avr-objdump
 SIZE    = $(AVRPATH)\avr-size --format=avr --mcu=$(MCU)
 CFLAGS    = -Wall -Os -mmcu=$(MCU) -c -std=gnu99 -funsigned-char -funsigned-bitfields -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -gdwarf-2
 #-DF_CPU=$(CLK)
-SRCS = application.c lfsr.c init.c isp.c mem23SRAM.c w25q.c main.c network.c linkENC28J60.c transport.c md5.c ripemd160.c sha1.c sha256.c power.c
+SRCS = application.c applicationCore.c lfsr.c init.c isp.c mem23SRAM.c w25q.c main.c network.c linkENC28J60.c transport.c md5.c ripemd160.c sha1.c sha256.c power.c
 #where.c
 
 OBJS = $(patsubst %.c,obj/%.o,$(SRCS)) 

README.md

@@ -40,7 +40,9 @@ Whereas the standard protocol bindings should not need to change (e.g)
 #endif
 ```
 
-**application.c** : This is where the majority of user changes are likely (although not in stock application layer routines like "queryNTP()" or "handleDNS()") whereas "sendHTML()" is the core routine for a server where it responds to an incoming request.
+**applicationCore.c** : Contains stock application layer routines like "queryNTP()" or "handleDNS()"
+
+**application.c** or **application[DeviceName].c** contains device-specific application layer material, e.g. "sendHTML()" is the core routine for a server where it responds to an incoming request.
 
 Some routines, e.g. **power.c**, **stepper.c** are bespoke to specific hardware finished products.