Document NVCM programming procedure about tillitis-key1

[dehanj]

@cibomahto i'm about to break out the pynvcm.py with friends to a separate repository to separate it a bit from the rest in this repo.
Just to cross-check, it is still fine to do the write, verify and secure in one go? It seems to work fine during my tests, but got a bit curious since you mention it as three seperate steps here

./pynvcm.py --write ../application_fpga/application_fpga.bin --verify ../application_fpga/application_fpga.bin --secure --my-design-is-good-enough

[cibomahto]

I think it's fine, the Lattice tools don't power cycle the chip between these steps.

Just note that pynvcm doesn't honor the order of operations passed to it; it has a fixed order that it evaluates them (which works for this case):

tillitis-key1/hw/production_test/pynvcm.py

Line 725 in 7cd085a

if args.sleep_flash:

I think I wrote it as separate steps for clarity.

[dehanj]

Thanks, appreciate the clarity!

[dehanj]

pynvcm.py now lives in its own repo: https://github.com/tillitis/pynvcm

We have not removed these files from this repo, but it will most likely be done in the near future, so closing this.