Thread: hp-41cx / NoV-64d / Hepax XF multi-function
|
09-05-2023, 07:03 AM
Post: #3
|
|||
|
|||
RE: Thread: hp-41cx / NoV-64d / Hepax XF multi-function
(09-04-2023 03:02 PM)rprosperi Wrote: Using these HEPAX functions to see what the module thinks is in HEPRAM: Thanks Bob, I got the following results: HEPDIR H:DIR EMPTY HEPAX 002 3: -ext fnc 2d 4: no rom 5: -time 2c 6: -hepax 1d 7: no rom 8: hepax ram 9: @@@@@@@ A: hepax ram B: hepax ram C: no rom D: no rom E: no rom F: no rom Page 9 is not what it should be and indeed suggests that the memory has not been cleared. After this block dir I applied the CRF method: 1. enter + on: does not work. 2. <- + on: does work. HEPAX 002 3: -ext fnc 2d 4: no rom 5: -time 2c 6: no rom 7: no rom 8: no rom 9: no rom A: no rom B: no rom C: -hepax 1d D: no rom E: no rom F: no rom I would expect 'hepax ram' in 8 - B, but clearing hasn't happened yet, so this might be normal. Next, still following the procedure, for each chip, I cleared the pages: 000 -> 4100 OK -> alpha 8 -> X CLRAM 9 -> X CLRAM 10 -> X CLRAM 11 -> CLRAM and the same for 001 -> 4100, 002 -> 4100, 003 -> 4100 After a power cycle, this resulted in: 3: -ext fnc 2d 4: no rom 5: -time 2c 6: -hepax 1d 7: no rom 8: hepax ram 9: hepax ram A: hepax ram B: hepax ram C: no rom D: no rom E: no rom F: no rom for each of the four chips. While this result looks promising, keying in the test program and running it, like before, still results in: 1. nonexistent 2. 9:@@@@@ in the block dir In my mind there are three possibilities: 1. I interpreted the procedure for clearing incorrectly. 2. Something is broken. 3. The XF functionality does not work in a HP-41 CX. I hope somebody can confirm one of these possibilities, or can come up with a completely new one. Thanks again, Kees Jan |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)