0.3.0 switch over to LCM repository

This is a one way ticket to start using the life-cycle-manager
repository
When it executes, it will set the ota-main routine to the latest LCM
version as long as the LCM version is higher than this one
for more info see https://github.com/HomeACcessoryKid/life-cycle-manager
Once the LCM ota-main routine kicks in, the UDPlogger output can be
seen running in terminal
nc -kulnw0 45678

deploy.md

@@ -7,21 +7,21 @@ cd ota/src
 ```
 #initial steps to be expanded
 
-mkdir ../certificates/0.2.4v
-cp ../certificates/certs.sector* ../certificates/0.2.4v
+mkdir ../certificates/0.3.0v
+cp ../certificates/certs.sector* ../certificates/0.3.0v
 #set local.mk to the ota-main program
-make -j6 rebuild OTAVERSION=0.2.4
-mv firmware/otamain.bin ../certificates/0.2.4v
+make -j6 rebuild OTAVERSION=0.3.0
+mv firmware/otamain.bin ../certificates/0.3.0v
 #set local.mk back to ota-boot program
-make -j6 rebuild OTAVERSION=0.2.4
-cp firmware/otaboot.bin ../certificates/0.2.4v
-#commit this as version 0.2.4
-#set up a new github release 0.2.4 as a pre-release using the just commited master...
+make -j6 rebuild OTAVERSION=0.3.0
+cp firmware/otaboot.bin ../certificates/0.3.0v
+#commit this as version 0.3.0
+#set up a new github release 0.3.0 as a pre-release using the just commited master...
 
 #erase the flash and upload the ota-boot program to the device that contains the private key
 ```
 esptool.py -p /dev/cu.usbserial-* --baud 230400 erase_flash 
-make flash OTAVERSION=0.2.4
+make flash OTAVERSION=0.3.0
 ```
 #run the code to change the sysparam area already
 #upload the privatekey