20-02-2014, 09:59 AM
piker,
As a general advice, if you are programming your devices with a development tool, then it means you are on a very dangerous track. Let me explain why...
With doing this you are showing that your firmwares are not under source control. Looks like you are publising (releasing) them without tracking the revisions. This is OK with DIY projects but not OK in a bigger scope. Production programming means you are selling some devices or releasing to the field even without selling them. And if you can not track the revisions and not test them enough, you'll going to get into trouble sooner or later.
You should track your revisions in a system even for beta and field tests.
Also your "MCU loading" stage has to be isolated from the development medium. This way you can always load the expected firmware. Otherwise you cannot be sure about that.
As a general advice, if you are programming your devices with a development tool, then it means you are on a very dangerous track. Let me explain why...
With doing this you are showing that your firmwares are not under source control. Looks like you are publising (releasing) them without tracking the revisions. This is OK with DIY projects but not OK in a bigger scope. Production programming means you are selling some devices or releasing to the field even without selling them. And if you can not track the revisions and not test them enough, you'll going to get into trouble sooner or later.
You should track your revisions in a system even for beta and field tests.
Also your "MCU loading" stage has to be isolated from the development medium. This way you can always load the expected firmware. Otherwise you cannot be sure about that.
/// Murat Ursavas
/// www.muratursavas.com
Click here for a comprehensive EmBlocks and ARM tutorial.
/// www.muratursavas.com
Click here for a comprehensive EmBlocks and ARM tutorial.