Need provisioning step-by-step guide about catena-sketches

[forrestfiller]

@terrillmoore some dissonence between the updated readme and information provided here. For example, I was unable to complete the LoRaWAN provisioning section successfully--couldn't get my device registered to my application. However, once I found this issue, specifically the "Reprovisioning" section at the end of this issue, I entered in

lorawan configure nwkskey 0
lorawan configure appskey 0
lorawan configure devaddr 0
lorawan configure netid 0

And then the serial monitor went into a loop of EV_TXSTART, EV_TXSTART, etc.

Then I git cloned your random sysEUI generator here into my project dir, ran:

cc random-eui.c
./a.out

and grabbed the generated sysEUI printed in my terminal window. You reference it as a potential devEUI above, so on the TTN console I was able to change the devEUI there, and use the command from the above:

system configure syseui yoursyseui

in my serial monitor in atom via platformIO (which could be done in any terminal with cli installed):

pio device monitor --port /dev/cu.usbmodem1421 --baud 115200

then I ran through the LoRaWAN Provisioning commands from the README.md using the generated sysEUI as my devEUI, and now I'm finally seeing packets hitting my backend on TTN console.

This is a bit of a debug dump (sorry). I'm make a pull on your README, and hopefully you can cherry pick somethings that are useful to help people out.

Thanks for your support, excited to have the Catena4450 up and running via TTN.

[forrestfiller]

Another quick thing to consider adding into the README.md is the payload decoder option in the TTN console.

I dropped your code from your Catena message decoder for TTN into my decoder function on the TTN console and now I have lovely human readable data to view without converting hex in my brain - which I can't do thaaaaat well at this point anyway.

[terrillmoore]

Hm, the info here is better than some of the info in the README.md. Leaving this open in hopes that I'll remember to update the README. But we need to split up this repo (keep 4410 separate from 4450, etc.)