NoV-64: Can't Access RAM Chip 3



#2

I had a hang while attempting to READROM the contents of a ROM images file into the four HEPAX RAM pages on chip 3. Since, I have not been able to access the chip. Trying to set the h4100 control word to 003, 103, 203, things hang momentarily and the screen displays a sometimes blinking NONEXISTENT that only clears when I remove the battery.

I have tried wiping the ROM in microbrn, clearing the RAM with CLRAM4.hex (the calc returns CLR OK), and using the CRF procedure in an unsuccessful effort to access the bum chip and clear any corrupted hex code. No dice. Any effort to point the calc to that chip yields the disturbing behaviour noted above. I have also manual cleared the RAM on chips 0, 1, and 2, which, by the way, seem to be behaving fine.

Any ideas? Diego advises that it is darn near impossible to damage these things with bad programming, so I hope I can recover this.

TIA,

Les


#3

Just bumping this.

The ominous lack of response after nearly 12 hours makes me fear that I have severely fried something.

I have written Diego directly, but I know he is vacationing and I was hoping someone else in the group could advise first.

Many hopeful thanks in advance,

Les


#4

I am heading out for a family night right now and will report details later, but I did recover the corrupted RAM and now have a fully functioning NoV-64 once again.

More later!

Les


#5

Hi Les,

This is a two side reply:

First I'm sorry not being on-line at first instace to help solving your chip #3 issue.

Second I'm happy to see you've got to fix it yourself... that's what the CRF was designed for... :-)

Hope you get a nice buch of fun out of your HP-41/NoV tools!

Cheers from Dominican Republic.

Diego.

Edited: 28 May 2012, 10:07 p.m.


#6

Thanks, Diego. I already told you in the email, but for the benefit of others, here is what I did:

I used HEXEDIT to change h'4100 contents to h'003. Within a second--I didn't even have to leave HEXEDIT--NONEXISTENT started flashing. I did NOT remove the battery this time--instead, I executed the ENTER-double ON manoeuvre and found myself with a normal display. I did NOT turn off the calculator--I simply executed CLRAM for 11 down to 8, and, voilà, on turning the calc on and off I am able to point myself to RAM chip 3 by changing h'4100 to any of the configurations that do so.

Of course, I lost everything, such as it was, in the 4 pages of HEPAX RAM in chip 3, but considering that I believed I had physically damaged the memory, this is a small inconvenience. I have been able to restore my desired ROMs and other files using ClonixConfig and mass storage routines with HP-IL and PIL-Box.

Thanks for the reply. I am learning a lot and sorting out things on my own.

Les


Possibly Related Threads...
Thread Author Replies Views Last Post
  42S with nonvolatile RAM Lyuka 5 350 12-13-2013, 08:52 AM
Last Post: Lyuka
  HP-41 Clonix&NoV's SW Update. (For the non-Primer's guys out there... :-) Diego Diaz 21 737 11-13-2013, 09:00 AM
Last Post: Ángel Martin
  HP Prime - RPN stack access from programs? Mike Mander (Canada) 10 382 09-30-2013, 11:20 AM
Last Post: steindid
  Best way to test HP-71B RAM modules (the 32K/96K ones etc.)? Philippe Lasnier 4 371 09-25-2013, 09:54 AM
Last Post: Philippe Lasnier
  HP 2225D+ RAM failure/replacement Luca 4 285 09-10-2013, 01:46 PM
Last Post: Luca
  Questions about building a RAM card for hp 48 Waon Shinyoe (China) 0 158 07-09-2013, 09:53 PM
Last Post: Waon Shinyoe (China)
  HP-41CL & NoV(-64): Race condition? Geir Isene 11 564 05-03-2013, 01:59 PM
Last Post: Diego Diaz
  Latest Clonix/NoV's SW update. Diego Diaz 5 278 02-15-2013, 12:12 PM
Last Post: Ángel Martin
  ACT CHIP aj04062 5 262 01-27-2013, 02:11 PM
Last Post: Eric Smith
  Classic calculator display chip type number? Juergen Hofstaedter 3 216 01-22-2013, 12:47 PM
Last Post: Eric Smith

Forum Jump: