CT60 TOS source reloaded

[wongck]

I agree, Beta 10 is a good starting point but if e.g. @wongck confirms that Beta 12 has the *ctpci* ide fixed, it would make much more sense reverse engineer Beta 12 changes than reverting to Beta 10.

I flashed beta 12 and on reboot I get this warning messages... I have not seen this before...
"Warning: Bad ROM CRC IN CHIP E"

Screenshot.jpg

I pressed the space bar ( I guess ) and it continue to the boot selector and then continue like normal, however it hang loading NVDI.
I did a hardware reset but it did not restart any more .... My floppy drive is now flashing and then stops.
Not sure if it's this beta 12 or what... but now my CT63 no longer boots.

I had to go back ot 030 mode to flash beta 10. Point to note is that in 030 mode, NVDI still continue to crash.

So now back to beta 10 but still the CT63 does not boot and flashes my floppy.
I got to check that CTPCI.HYP file now.

Any ideas guys?

[wongck]

I know that EPROM/ EEPROM has a limit on programming cycles.... I hope I have not reach that limit on my CT63.
That hardware is like 20 years old... I have flash it many times over those years. Well I don't know. I need to check the HYP on what that floppy led means.

[mikro]

That error message comes from TOS (in this case CT60 TOS) so your suspicion may be correct, i.e. the content of the flash is not read properly. That would also explain the hangs and weird behaviour (also try to erase NVDI's bitmap fonts cache, maybe it got corrupted during the boot).

However I would try something proven first, i.e. flash 1.03c and observe whether the error is still there.

[wongck]

it is not the FIF file, I deleted that immediately.
May be some fonts that are bad.

I am trying to find my first ctpci firmware to try.

[Ektus]

I've seen that "Bad ROM CRC" message before, IIRC even without the CT6x. Could also be NVRAM related. Doesn't the flash program perform a verify run anyway? If that one is good, the flash should be fine.

[wongck]

Ok back in business

I think when I flashed beta 12 or re-flash back to beta 10, NVDI was not running properly or not running at all.

After I replaced my fonts folder from my backup, NVDI ran fine and I re-flashed beta 10 and the CT63 ran as expected.
So I reflash beta 12 again....
It has an extra status.... SCSIDVR found..

Screenshot.jpg

In TOS, I copied and deleted several folders without any warning messages.

So I tried to run Mint.... but it hang after displaying Ext2 filesystem driver message.
I rebooted (power off/on) and tried 3 times to run Mint and every time it hangs after displaying the Ext2 filesystem driver message.

I guess SCSIDRV was changes in this beta.

[mikro]

@wongck glad to hear you have solved / fixed it!

Also many thanks for your testing, that's really interesting. I guess your FreeMiNT installation works nicely in Beta 10. It seems that Didier did fix something in Beta 12 but not enough to make FreeMiNT happy. Beta 10 perhaps doesn't do any of this stuff and that's why it works so much better.

Well, we tried...

[wongck]

Yes, Mint works well with beta 10 (with network and USB as well).

I also tested the older Mint v1.18... I guess without the FAT32 correction updates... but it still hang at the same point (after EXT2 driver message).
That is the oldest Mint version I have on my Falcon, so I did not test v1,17.

[marss]

Hi,
With Mikro's latest beta 11, it is impossible to launch Freemint/ Myaes. The setup stops just before launching Myaes ;(
With Didier' s latest beta 10, it launches fine
Can someone confirm?
Thanks

[mikro]

@wongck confirmed it a couple of messages above yours. ;)

But thanks for checking, that makes it a really good motivation to revert /reverse engineer all IDE/SCSIDRV changes back to Beta 10 and start anew with SCSIDRV support.

[marss]

Hi,
Any update about the possibility to run Mikro's latest beta 11 under Freemint/ Myaes?
Thanks

[mikro]

This is a way more demanding task than just taking a look at something. First I'd need to get my CTPCI up and running. Then I'd have to fix current kernel which has a mysterious issue with it, I had spent hours trying to track it down with Latz. And only then I can start experimenting with the actual TOS.

But one day I'll get to it.

[marss]

fingers crossed