Examples of Memory MAP with 2x Clonix-D?

[J-F Garnier]

(10-13-2022 07:51 AM)Ángel Martin Wrote:  As it turns out, there's a difference in the way the [SPLASH] routine works between the FULLNUT and HALFNUT LCD drivers. Unfortunately I have no idea why this happens (which is not supposed to!), but the good news is that I figured out the code changes needed to make it work properly on each type.

We already discussed this problem previously, unfortunately with no definitive conclusion on the cause.
I don't believe there is a difference between the FN and HN LCD drivers, except the extra characters of course.
I'm more suspecting a problem in the driver emulation in the CL. But I don't own this machine and I will not investigate myself.
Someone with non-CL FN and HN machines may confirm that there is no difference relative to the SPLASH screen behaviour between FN and HN.

J-F

[Sylvain Cote]

(10-13-2022 09:08 AM)J-F Garnier Wrote:  I don't believe there is a difference between the FN and HN LCD drivers, except the extra characters of course.
I'm more suspecting a problem in the driver emulation in the CL. But I don't own this machine and I will not investigate myself.
Someone with non-CL FN and HN machines may confirm that there is no difference relative to the SPLASH screen behaviour between FN and HN.

I just made the test with a standard 41CX-FN (0:NFL 1:DCC) , 41CX-HN (0:NFL 1:DCC) and a Clonix-D module. (actually a NoV-64 configured as a Clonix-D with join blocks)
The NoV-64 module is configured with PicKit2 and ClonixConfig61 which include the revised bank switching firmware.

ROM sources:

Code:

LIB4CL.ROM   ← LIBRARY4_CL.ROM renamed for ClonixConfig 8.3 limit
LIBRARY4.ROM ← rom_files_220923.zip
OSXB1.ROM    ← rom_files_220923.zip
OSXB2.ROM    ← rom_files_220923.zip
OSXB3.ROM    ← rom_files_220923.zip
OSXB4.ROM    ← rom_files_220923.zip
HP-16C_1.ROM ← rom_files_220923.zip
HP-16C_2.ROM ← rom_files_220923.zip
HP-16C_3.ROM ← rom_files_220923.zip
HP-16C_4.ROM ← rom_files_220923.zip

With LIBRARY4 in page 4, OSX3 ROMs (4 banks) in page 8 & 16CS ROMs (4 banks) in page 9.

On the 41CX-FN, I get → "XROM:16:00 → "¯ -LIB#4-R ."
On the 41CX-HN, I get → "XROM:16:00 → "-LIB#4-R60b."

With LIBRARY4_CL in page 4, OSX3 ROMs (4 banks) in page 8 & 16CS ROMs (4 banks) in page 9.

On the 41CX-FN, I get → "XROM:16:00 → "-LIB#4-R60 ."
On the 41CX-HN, I get → "XROM:16:00 → after some characters scrolling the screen goes blank and freeze

[Ángel Martin]

(10-13-2022 10:03 AM)Sylvain Cote Wrote:  With LIBRARY4 in page 4, OSX3 ROMs (4 banks) in page 8 & 16CS ROMs (4 banks) in page 9.

1. On the 41CX-FN, I get → "XROM:16:00 → "¯ -LIB#4-R ."
2. On the 41CX-HN, I get → "XROM:16:00 → "-LIB#4-R60b."

With LIBRARY4_CL in page 4, OSX3 ROMs (4 banks) in page 8 & 16CS ROMs (4 banks) in page 9.

3. On the 41CX-FN, I get → "XROM:16:00 → "-LIB#4-R60 ."
4. On the 41CX-HN, I get → "XROM:16:00 → after some characters scrolling the screen goes blank and freeze

J-F's got a very good point, but Sylvain's experiments show that the CL driver control is *not* at fault. Confusing results perhaps, but not unexpected:

LIBRARY4 should work for HN machines, which is supported by your #1. and #2. cases above
LIBRARY4_CL should work on FN machines, which is fully supported by your #3. and #4. cases too.

So I'm now more convinced there's something different between the HN and FN drivers in the way they execute LCD MCODE instructions - heresy, yes I know.

See attached the MCODE for the routine - good luck trying to follow the flow on that one, it's really devilish..