Find's Treasure Forums

Welcome to Find's Treasure Forums, Guests!

You are viewing this forums as a guest which limits you to read only status.

Only registered members may post stories, questions, classifieds, reply to other posts, contact other members using built in messaging and use many other features found on these forums.

Why not register and join us today? It's free! (We don't share your email addresses with anyone.) We keep email addresses of our users to protect them and others from bad people posting things they shouldn't.

Click here to register!



Need Support Help?

Cannot log in?, click here to have new password emailed to you

Some new pictures

Hi Carl,

Fun days huh?

Sounds like down the road two chips are needed - one for the actual detecting operation, and a reprogrammable one to contain the operating system. Bound to happen someday. Heck, I'll pay for operating system upgrades. Microsoft has milked me since day one!

Steve Herschbach
 
Carl-NC said:
You would still have to reprogram the whole chip, and then recalibrate.

You just need to store the calibration parameters in a 19 cent 256 x 8 EEPROM device, and make sure when you change the firmware (FW) that the address of those parameters is not changed. If you use microcontrollers (uC's) with on-board EEPROM, you could still utilize that for storing user programs and settings, which could be backed up prior to flashing the uC with the wireless USB dongle. If the FW needs to re-map the user EEPROM locations due to reorganization of settings and parameters for new features, the computer software just needs to know what version it has backed up, and what version it is programming those features for. All new parameters would be set to default values.

I'm just guessing, but calibration parameters would only need to be changed if something like the transmit frequencies or something major was altered. All of the calibration for A/D's would be still valid.
 
Top