About 10% of our devices containing Bitsy boards (image 3.20, ROM 1.75) are being returned to us by our customers. Once received by us, we attach a serial cable. Some of the boards are stopping after ‘InitializeJIT’ is output (reference Topic 341). Others are not providing any output. Some we are able to bring back to life using the JTAG utility. Others are sent back to ADS to determine the cause of failure.
A brief description of our operating conditions: 1. Our applications utilize the CF interface for data acquisition.
2. The PCMCIA card is used to store the data acquired. Under normal operating conditions the PCMCIA card does not contain files which the ADS loader program would automatically load. In other words, under normal operating conditions the following files are NOT on the PCMCIA card: ADSLoad.reg, ADSLoad.exe, ADSLoad.rom ADSLoad.bmp, ADSLoad.hwt, nkload.bin.
3. We utilize a small application specific registry which is maintained in the onboard flash (\FlashFx Disk). The contents of this registry are added to the device registry as part of the ADSLoad program.
The boards which are failing are failing under normal operating conditions – there are no files on the PCMCIA card which would be automatically loaded.
We will continue to check the availability of power at critical times.
Please also see Topic 854 in which we addressed concerns about an unlocked flash. Note that we have abandoned the idea to reflash the loader files ourselves.
On our end, we assembled a test stand and programatically cycled power at device startup in an attempt to determine whether or not a power cycle at an inopportune start-up time was the culprit. We had over 5000 power cycles without a problem.
We have also utilized an all-but-drained battery and disconnected external power upon boot in an attempt to mimic what our customers may have been (inadvertently) doing. But we have been unable to kill a board.