Signing on EMX doesn't work

Archive
1

Hi,

I’ve seen a couple threads in this forum where people couldn’t upload application due to signature problems. My problem is completely opposite: I couldn’t sign my EMX Devboard…

To sign it, I:

  1. Update EMX with EMXUpdater (so it erases everything).
  2. Deploy a simple LED flashing application.
  3. In MFDeploy, select “Target->Application deployment->Create application deployment”
  4. Select the deployment file, click “Create key”
  5. Go to “Target->Manage device keys->Update device keys” and then select the key created in the previous step (this part seems to be working, as I cannot change the key until I provide correct old one)
  6. Erase everything (in MFDeploy).

And it doesn’t work. I can upload anything. I have tried many other combinations, but no matter what I do, it just doesn’t work.

Is there anybody in this forum actually using this signing feature on EMX? Perhaps I am skipping some crucial step?..

2

Whoa, so many responses :slight_smile: A little update: signing works as expected ONLY if EMX is in TinyBooter mode. But once I restart the EMX to run the application, anyone can deploy anything again. A workaround would be to change debug interface to COM1 which, at least for me, is not working either. So, basically I would mask one broken feature with another broken feature. Doesn’t sound very inspiring…

I really need to restrict access to my EMX firmware. Where are GHI responses when I need them so much?.. :slight_smile:

P.S. It looks like my thread is in the wrong section. Could moderators be so king and move it to the right one?

3

We did see your post and we are looking into it but this needs some time to test. More time as we are on 4.2