|Re: Nov-64: Complete Newbie Needs Help|
Message #8 Posted by Les Wright on 4 May 2012, 11:09 a.m.,
in response to message #7 by Diego Diaz
Diego, I don't think it is your fault this time, since somehow enough of a programming job was completed for me to corrupt the chip.
I've cleaned the contacts on the connector. The pins are present and straight. The module's contacts seem to contact the connector fine--not too snug, but no gaps. Just for good measure I have tried this on more than one computer running XP and the same thing occurs. I have ensured that the USB cable is connected directly to the computer at a fully powered port and not a hub.
I know that the module is correctly oriented on the connector and the connector is correctly inserted into the programmer, because when it isn't microbrn tells me it can't detect the chip.
Still, I get the same bad ROM error, and this time it is consistent--only this time the address is 0x0000, "Good" is 6AF2 and "Bad" is 6A42, so at the very first address. "Good" refers to data in the hex file, and "Bad" refers to what already lives at that address when I do a "Read" of the corrupted ROM contents.
I should admit that I recall being able to complete one programming of the module--I got all the way to verification--but it was after that even HEPAX wasn't there anymore. Before that the ROM error was at address 0x0005. I have a sinking feeling that I inadvertently overwrote the module with something other than the appropriate HEX file.
The module did not endure any physical abuse by me. It looks fine on inspection and I trust it survived the long journey.
I am glad you are willing to help with this. I know that the technical aspects of the Clonix family could be quite sophisticated, but I figured that if I could just burn in one or two favourite modules like PPC to get started and enjoy the HEPAX functionality I would certainly get my money's worth until I learned the finer points about blocks, pages, potential conflicts, etc.
Look forward to rescuing this.
PS: Before I get started with a programming attempt, I get a dialog box stating "ROM = Not Erased, EEPROM = Not Erased, ID = Not Erased, ID = Not Erased, Fuse = Not Erased. Continue to erase and program this chip?" Is this normal behaviour? Don't I want the ROM to be erased and overwritten with what's in the HEX file? I should also mention that I get the above-mentioned ROM error without attempting to program--I click Verify and it immediately tells me the same thing. It is as though the programmer is telling me the module is bad from its very first address and it doesn't want to put my new HEX data there.
Edited: 4 May 2012, 6:10 p.m. after one or more responses were posted