EMX in a production system == no TFT display and firmware update ahead

[GerhardKreuzer]

Hi,

after playing around with the EMX-dev kit, I am going to construct two systems using EMX. I detected some issues at firmware update and software deployment, like pressing some buttons and having some messages on TFT. Sometimes deploy hands for no reason.

In my systems, there will be no TFT around, so providing something for the buttons is easy, but how can I tell the user, that firmware update is ok, the module is in a correct state for someting or not or things like this?

Is there something (blinking LED when connected to IO line x) which I have to take into account while routing my production boards?

With best regards

Gerhard

PS: Notification when somebody replies didn't work!!!!

[SupportAdmin]

You know from the USB status
In GHI loader, the virtual COM driver is loaded
in tinybooter, a ping from mfdeploy returns tinybooter
in firmware, a ping returns tinyclr

[GerhardKreuzer]

Ok, so it is the best practice, to have the USB (device) interface on the production board and some switches for entering the different maintenance modes. Everything is controlled and monitored by the USB communication.

Thanks for helping

Gerhard

[SupportAdmin]

Yes correct