MLDL 2000 and HEPAX Message #1 Posted by Howard Owen on 7 Nov 2006, 4:47 a.m.
I've run in to a snag trying to get HEPAX 1D working with my MLDL 2000. I've read and reread the threads from last year, especially this one, containing discussions between Meindert, Luiz and Diego regarding how to get HEPAX working. I have gotten almost all the way there, but I still get bogus HEPDIR entries, C2, C3, C4 and C5 in my handmade 16K HEPAX file system, as reported by Luiz in message #27 of the referenced thread. My configuration is as follows.
Flash Addr: Content - Comment
$3D000: Hepax1-1D - Checksum fails
$3E000: Hepax2-1D - good checksum
$3F000: Hepax3-1D - good checksum
$40000: Hepax4-1D - good checksum
SRAM Addr: Content
$14000: Hepax RAM page 1
$15000: Hepax RAM page 2
$16000: Hepax RAM page 3
$17000: Hepax RAM page 4
SRAM SR #1:
Page 7
B0: $03D = Enabled Flash page @ $3D000
B1: $03F = Enabled Flash page @ $3F000
B2: $03E = Enabled Flash page @ $3E000
B3: $040 = Enabled Flash page @ $40000
Page 8
B0: $114 = Enabled SRAM page @ $14000, write protect OFF
B1: $114 = Enabled SRAM page @ $14000, write protect OFF
B2: $114 = Enabled SRAM page @ $14000, write protect OFF
B3: $114 = Enabled SRAM page @ $14000, write protect OFF
Page 9
B0: $115 = Enabled SRAM page @ $15000, write protect OFF
B1: $115 = Enabled SRAM page @ $15000, write protect OFF
B2: $115 = Enabled SRAM page @ $15000, write protect OFF
B3: $115 = Enabled SRAM page @ $15000, write protect OFF
Page A
B0: $116 = Enabled SRAM page @ $16000, write protect OFF
B1: $116 = Enabled SRAM page @ $16000, write protect OFF
B2: $116 = Enabled SRAM page @ $16000, write protect OFF
B3: $116 = Enabled SRAM page @ $16000, write protect OFF
Page B
B0: $117 = Enabled SRAM page @ $17000, write protect OFF
B1: $117 = Enabled SRAM page @ $17000, write protect OFF
B2: $117 = Enabled SRAM page @ $17000, write protect OFF
B3: $117 = Enabled SRAM page @ $17000, write protect OFF
Page C
B0: $140 = Enabled SRAM page @ $00000, write protect ON ( CCD/OSX)
B1: $3FF = DEFAULT
B2: $3FF = DEFAULT
B3: $3FF = DEFAULT
Page D
B0: $3FF = DEFAULT
B1: $3FF = DEFAULT
B2: $3FF = DEFAULT
B3: $3FF = DEFAULT
Page E
B0: $142 = Enabled SRAM page @ $02000, write protect ON (Sandbox Low)
B1: $3FF = DEFAULT
B2: $3FF = DEFAULT
B3: $3FF = DEFAULT
Page F
B0: $143 = Enabled SRAM page @ $03000, write protect ON (Sandbox High)
B1: $3FF = DEFAULT
B2: $3FF = DEFAULT
B3: $3FF = DEFAULT
I loaded all zeros into the RAM pages from the HEPAX ROM images found at TOS. I then manually edited the images to create the HEPAX file system chain. When the 41 (a halfnut 41CX with a 2X extended memory module) powers up, the contents of the RAM pages are fine. I can run HEXEDIT to verify this on the 41 itself. But if I execute HEPROOM or HEPDIR, the HEPAX operating system adds the bogus entries. These show up in all four pages. Page 8 differs from the other three. It has this:
$8902: 048 0B0 000 01C 000 000 000 000 047 00F
Whereas the others all have:
$X902: 04E 00F 000 000 ...
I can reset these words to zeros, but they come back on the next access to the file system by the HEPAX.
Based on the report by Luiz, I believe that I may be able to go ahead and use the HEPAX like this, ignoring the bogus entries. But I wondered if others had progressed beyond this point.
Regards Howard
|