Post Reply 
NOV64d with HEPAX STD & HEPAXRAM & CCD
06-06-2024, 10:38 AM
Post: #1
NOV64d with HEPAX STD & HEPAXRAM & CCD
i have a minor problem with following configuration

- HP41CV Halfnut from 1986
- NOV64d Module
- NOV64D config:
- HEPAX 1D
- CCDL B on page C
- CCDU B on page D

I am am using Matrix and Hex functions without any problems. The ROMID is #9
I run into trouble with the I/O functions e.g. INPT or PMTK with XROM number #11,xx and son on.

With XEQ they excecute programs stored in Heapax ram!

If I switch to an empty HEPAX ram page (HEXEDIT:4100) then NONEXISTENT appears.

I/O finctions are listet in CAT 2

The reason is clear, the HEPAXram (HEXEDIT: 8000) first byte is "B" which is 11 dec. so this is a conflict with the CCD I/O functions. The byte stands for the ROMID.

I changed the byte to 1B and now the I/O function work. But may be this could corrupt my HEPRAM.

So is there a workarond that the romid can be set manually?
Or a special nov64d config?
Ralf

/41/48/
Find all posts by this user
Quote this message in a reply
06-06-2024, 12:00 PM
Post: #2
RE: NOV64d with HEPAX STD & HEPAXRAM & CCD
You're better off changing the analogous ROM ID byte of the conflicting CCD module, which will have no impact other than making programs which use these CCD functions not portable to other machines that use the default CCD module ROM ID. I don't know for certain that the HEPAX ROM requires it's default ROM ID, but its likely that it looks for this at some point, perhaps using functions such as HEPDIR, etc.

--Bob Prosperi
Find all posts by this user
Quote this message in a reply
06-06-2024, 12:22 PM (This post was last modified: 06-06-2024 02:34 PM by Sylvain Cote.)
Post: #3
RE: NOV64d with HEPAX STD & HEPAXRAM & CCD
You can change the XROM ID directly with HEXEDIT without any effect.

Procedure I do when I want to reset a NoV HEPAX RAM block:
Code:
"OK"
8    CLRAM
9    CLRAM
10   CLRAM
11   CLRAM
OFF  ON      // power cycle
HEPDIR       // X is set to 2600

Assuming no other module is configured in the NoV module or plugged-in, the above initialization procedure should produce the following contig:
Code:
 XROM  ID    Prev. Page   Next Page
---------- + ---------- + ----------
0x8000 00B | 0x8FE7 000 | 0x8FE8 009
0x9000 00C | 0x9FE7 008 | 0x9FE8 00A
0xA000 00D | 0xAFE7 009 | 0xAFE8 00B
0xB000 00E | 0xBFE7 00A | 0xBFE8 000

If I insert a physical the CCD module in port 3, I get a XROM conflict (11) and page 8 take precedence over page 13.

Here we have three options:
  1. with HEXEDIT, manually change the XROM ID with a non conflicting value (ex. 0x8000 001)
  2. if the HEPAX RAM block is empty, clear the conflicting HEPAX RAM page like this:
    Code:
    "OK"
    8
    CLRAM
    OFF
    ON       // power cycle
    HEPDIR   // X is set to 2600
    the above should produce the following configuration:
    Code:
     XROM  ID    Prev. Page   Next Page
    ---------- + ---------- + ----------
    0x8000 00F | 0x8FE7 00B | 0x8FE8 000
    0x9000 00C | 0x9FE7 000 | 0x9FE8 00A
    0xA000 00D | 0xAFE7 009 | 0xAFE8 00B
    0xB000 00E | 0xBFE7 00A | 0xBFE8 008
  3. redo the full initialization procedure to produce the following config:
    Code:
     XROM  ID    Prev. Page   Next Page
    ---------- + ---------- + ----------
    0x8000 00C | 0x8FE7 000 | 0x8FE8 009
    0x9000 00D | 0x9FE7 008 | 0x9FE8 00A
    0xA000 00E | 0xAFE7 009 | 0xAFE8 00B
    0xB000 00F | 0xBFE7 00A | 0xBFE8 000

edit: option #2, double-linked list data updated

Sylvain Côté
Find all posts by this user
Quote this message in a reply
06-06-2024, 03:04 PM
Post: #4
RE: NOV64d with HEPAX STD & HEPAXRAM & CCD
Hi Bob, hi Sylvain,
thanks for help. It works now. Option #1 was my choice.
Ralf

/41/48/
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)