Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.arch.embedded > #24555
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Newsgroups | comp.arch.embedded |
| Subject | Re: dsPIC serial number |
| Date | 2016-07-06 13:44 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <nlinf8$a91$1@dont-email.me> (permalink) |
| References | (3 earlier) <nlb065$g5t$1@dont-email.me> <nlb0cf$g5t$2@dont-email.me> <nlba37$frr$1@dont-email.me> <nlhjp6$b12$1@dont-email.me> <nlil77$3tb$1@dont-email.me> |
On 6.7.16 13:06, Syd Rumpo wrote: > On 06/07/2016 01:35, Don Y wrote: >> On 7/3/2016 8:13 AM, Syd Rumpo wrote: >>> I think you've convinced me that it can't be done /easily/, so it >>> looks like a >>> serial ID chip is needed. I was rather hoping there was something I'd >>> overlooked in the manual. >> >> I guess it depends on what you consider "easily" -- the fact that >> you're expecting (?) folks to do the upgrades themselves suggests >> you've already imposed a certain level of competence on them. >> >> Another way of looking at it: what's the potential (loss of) >> value if they "get the number wrong"? Will the product stop >> working? (you've previously indicated the "correct number" doesn't >> entitle them to anything special...) > > The customers would usually have access to a PIC programmer - both the > equipment and the person - of some kind and would get a hex file, > probably by email or from the web. I can't mandate a particular type of > programmer. > > I had hoped that there was some easy way of embedding a number in the > dsPIC and not overwriting it when firmware is changed. The ID is really > for traceability. Sadly, the dsPIC has no EEPROM. > > Cheers The configuration registers are separate from the code memory. There are some user bytes in the register bank. A normal program update should not write anything to the configuration area. -- -TV
Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-03 11:51 +0100
Re: dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-03 12:01 +0100
Re: dsPIC serial number Don Y <blockedofcourse@foo.invalid> - 2016-07-03 04:14 -0700
Re: dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-03 12:46 +0100
Re: dsPIC serial number Don Y <blockedofcourse@foo.invalid> - 2016-07-03 05:24 -0700
Re: dsPIC serial number Don Y <blockedofcourse@foo.invalid> - 2016-07-03 05:28 -0700
Re: dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-03 16:13 +0100
Re: dsPIC serial number Don Y <blockedofcourse@foo.invalid> - 2016-07-05 17:35 -0700
Re: dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-06 11:06 +0100
Re: dsPIC serial number Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-06 13:44 +0300
Re: dsPIC serial number Syd Rumpo <usenet@nononono.co.uk> - 2016-07-06 13:16 +0100
Re: dsPIC serial number Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-06 16:36 +0300
Re: dsPIC serial number Richard Damon <Richard@Damon-Family.org> - 2016-07-16 21:50 -0400
Re: dsPIC serial number Paul Rubin <no.email@nospam.invalid> - 2016-07-03 09:46 -0700
Re: dsPIC serial number Les Cargill <lcargill99@comcast.com> - 2016-07-03 12:46 -0500
Re: dsPIC serial number Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-03 21:04 +0300
csiph-web