[41CL WARP] XEQ+ oddness

[Monte Dalrymple]

(04-11-2021 02:12 PM)Sylvain Cote Wrote:  41CL boards from Monte Dalrymple:

1. ENBANK1 to ENBANK4 are supported (aka ENROMx, 0x100, 0x180, 0x140, 0x1C0)
2. page & bank mapping are done with the WCMD NEWT instruction and with the MMU (0x804xxx adresses)
3. extended 16 bits NUT instruction structure
   
   1. bits 15 to 14 unused (should/must be set to zero ?)
   2. bits 13 to 12 used for turbo handling (bits = this/next instruction)
      • 00 = turbo execute / turbo fetch (if enabled)
      • 01 = normal execute / normal fetch
      • 1x = refetch, normal execute / normal fetch
        
   3. bits 11 to 10 unused (should/must be set to zero ?)
   4. bits 9 to 0 are for NUT instructions
      
4. pages that are bank switch enabled
   
   1. some lower pages are standalone (0x4, 0x5)
   2. some lower pages are linked (0x6/0x7)
   3. even/odd port pages are linked (0x8/0x9, 0xA/0xB, 0xC/0xD, 0xE/0xF)
      
5. OS pages are not bank switch enabled (0x0, 0x1, 0x2, 0x3)
   

Some corrections:

[*]bits 15 to 14 unused (ignored)
[*]bits 11 to 10 unused (ignored)
[*]some lower pages are standalone (0x4, 0x6, 0x7)
[*]some lower pages are linked (0x3/0x5)
[*]OS pages are not bank switch enabled (0x0, 0x1, 0x2)

The 0x3/0x5 linking is required by the CX Extended Functions. The bank is switched by code in page 3 before a jump to code in page 5.

[rprosperi]

(04-11-2021 05:45 PM)MeindertKuipers Wrote:  

(04-11-2021 02:12 PM)Sylvain Cote Wrote:  Incomplete list of HP & EPROM/Flash box/modules bank switched product introduction year ...
...

Very impressive this list, thanks Sylvain! Maybe store this in the articles section?

1 +

Excellent suggestion Meindert, it will make it easier to find by readers in the future. I'd include Angel's and your comments as well. All useful and related info, best to keep it all together.

[cdmackay]

thanks very much Ángel, Bob, Meindert, Monte, Sylvain for the comprehensive notes, all very helpful.

I think I have just one question remaining, regarding how this issue affects pages 6/7.

I think I am reading that, on the 41CL, pages 6 & 7 are standalone? Therefore, had I used:

6 OSX3
7 WARP

that would, in theory, have been fine, despite both being bank-switched modules, since WARP could switch OSX's page 6 banks, without also switching its own banks in page 7?



And on the DM41X, where it's all controlled by the MOD file notes, does that mean it's OK to combine P6- & P7-specific bank-switched MODs? e.g. is it OK to use both OSX_BS4X-P6 & WARP_BS3-P7 concurrently?

[rprosperi]

(04-11-2021 09:39 PM)cdmackay Wrote:  And on the DM41X, where it's all controlled by the MOD file notes, does that mean it's OK to combine P6- & P7-specific bank-switched MODs? e.g. is it OK to use both OSX_BS4X-P6 & WARP_BS3-P7 concurrently?

Yes, this works, though I've not tried this with the new OSX files. In the past, this is just how I loaded these, until I started installing HEPAX, which self-relocates to Page-6, if available, so now WARP is installed in a higher port.

[Sylvain Cote]

Thank you Ángel and Monte for the corrections.
Thank you Meindert and Robert for the article suggestion.
I am starting a new job this week, so free time will be scarce, but I will create an article as soon as I can.

[Ángel Martin]

(04-12-2021 01:36 AM)rprosperi Wrote:  

(04-11-2021 09:39 PM)cdmackay Wrote:  And on the DM41X, where it's all controlled by the MOD file notes, does that mean it's OK to combine P6- & P7-specific bank-switched MODs? e.g. is it OK to use both OSX_BS4X-P6 & WARP_BS3-P7 concurrently?

Yes, this works, though I've not tried this with the new OSX files. In the past, this is just how I loaded these, until I started installing HEPAX, which self-relocates to Page-6, if available, so now WARP is installed in a higher port.

DM-41X / V41: If you use the "page-specific" versions of the MOD files (i.e. OSX_P6.MOD, OSX_P7.MOD, and WARP_P7.MOD) then the OSX / WARP module will always be plugged in those pages, with or without HEPAX present. The HEPAX will re-locate itself to any *available* pages but those are already used by said modules so they aren't available anymore. That happens first in the module loader, while the relocation is triggered by the CALC_ON polling point which happens *after* the module loader has done the initial allotment of pages. OK?

SY-41CL: Yes it's perfectly safe to use the OSX3.ROM in page#6 and the PWRX.ROM or the WARP.ROM in page #7. In fact this is exactly my configuration (except when I need to plug the HP-IL, obviously).

It's really not that complicated once you get the knack of it... ;=)

[rprosperi]

(04-12-2021 06:19 AM)Ángel Martin Wrote:  

(04-12-2021 01:36 AM)rprosperi Wrote:  Yes, this works, though I've not tried this with the new OSX files. In the past, this is just how I loaded these, until I started installing HEPAX, which self-relocates to Page-6, if available, so now WARP is installed in a higher port.

DM-41X / V41: If you use the "page-specific" versions of the MOD files (i.e. OSX_P6.MOD, OSX_P7.MOD, and WARP_P7.MOD) then the OSX / WARP module will always be plugged in those pages, with or without HEPAX present. The HEPAX will re-locate itself to any *available* pages but those are already used by said modules so they aren't available anymore. That happens first in the module loader, while the relocation is triggered by the CALC_ON polling point which happens *after* the module loader has done the initial allotment of pages. OK?

SY-41CL: Yes it's perfectly safe to use the OSX3.ROM in page#6 and the PWRX.ROM or the WARP.ROM in page #7. In fact this is exactly my configuration (except when I need to plug the HP-IL, obviously).

It's really not that complicated once you get the knack of it... ;=)

Sorry I was not clear; I used to load the page-specific Warp .mod file, but when I install HEPAX, I use the general (install in any page) version of the .mod file. It will indeed work the other way, but I've changed my 'normal' setup to this style.

[cdmackay]

thank you all, again. A most informative thread.