Main Site Documentation

G120 Device Keys and Signed Deployment


#1

Hi,

I’ve been trying to assign device keys to a G120 device running TinyBooter v4.3.4.0 and TinyCLR 4.3.6.0. When I try to update device keys (in MFDeploy), it allows me to change the key when the incorrect key is provided as the old key. As well, I can deploy any HEX file to the device regardless of the key used to sign it and the key on the device.

Does anyone have any advice on what might be going wrong with what I am doing?

Thanks


#2

Sorry, Application Protection is not working in 4.3 (and no promises it will ever will).


#3

@ MathewM - Can you detail the exact steps you took from start to finish? Have you tried this on a different non-G120 board?


#4

Hi John

I’ve tried on 2 different Cobra II boards I had as well as a G120 module.

Key Issue:
Steps:

  1. Create 2 keys in MFDeploy.
    2 Assign Key 1 to deployment sector of device.
  2. Try to assign an empty key to the device by using Key 2 as the old key. Empty key appears to be on the device.

Deployment Issue:
Steps:

  1. Create 2 keys in MFDeploy.
    2 Assign Key 1 to deployment sector of device.
  2. Sign deployment file using key 2.
  3. Deploy deployment file onto the device (program executed with no issues)

#5

@ MathewM - Have you tried with an EMX or G400?


#6

@ John

I tried on a Hydra, it also didn’t appear to work


#7

@ MathewM - We will take a look and see what we can find.


#8

@ MathewM - Do you by any chance have a board from a different manufacturer that you can try? When we tried it on the Mountaineer boards we saw the same issue.


#9

@ John - Sorry, I don’t have boards from any other manufacturers


#10

@ MathewM - Since we saw it on other boards as well, it seems like it is an issue in NETMF. I would create an issue on CodePlex.