Aros m68k (Kickstart substitute)

[blizz1220]

What youtube video ? So long time ago

From what I read no other ideas are pursued except Vampire FPGA
that is now with Apollo core.Igor might have trouble getting original
FPGAs where he (and I) is because we fall into East-Europe regions
Z category and local dealers often order cheapest things they can.

Igor seems to take his own order of doing things which proved good
so far.What will happen when Vampires become competition for all
other is yet to be seen.Problem I see is that only few people can
build them as individuals and no company seems that interested.
Probably because it's end-all-close-the-shop solution.

[chaos]

Hopefully there is an AROS developer around here to help me out

I'm trying to boot AROS on the MiST board running minimig. I've added support for 1MB kickstart ROMs, which seems to work OK, even with 'normal' extended kickstart ROMs (thanks mfilos for your help two years ago ).

So the AROS kickstart replacement boots up just fine, I even managed to start Agony (which didn't work completely OK - sprite collision problems?, but still good enough to finish level 1).

What I'd like to do is boot the AROS distro, but the kickstart replacement doesn't seem to detect the Gayle IDE, as implemented in minimig. The normal kickstart detects the minimig Gayle just fine.

The same AROS kickstart replacement works in WinUAE though.

Another thing - using the normal kickstart to try and boot AROS doesn't seem to work - it reports missing std.library and later hangs.

Here is the serial log from running AROS kickstart replacement on minimig:

...
[InitCode] calling InitResident (4 81 "ata.device")
[InitCode] calling InitResident (4 81 "ata_gayle.hidd")
[ATA] Gayle ID=dd. Possible IDE port=00da0000.
[ATA] Status=40,40
[ATA  ] ata_ReadSignature: Found signature for ATA device, but further validation failed
[ATA  ] ata_ReadSignature: Found signature for ATA device, but further validation failed
[GAYLE-ATA] Failed to create object for device IO: da0000:da1010 IRQ: da9000
...

So, if there is anyone that could tell me how AROS kickstart is trying to detect Gayle, I'd be grateful!

[wawa]

what aros kickstart (image) are you using? hopefully an up to date one, one from nightly?

as for soft kicking aros from amiga kickstart, heres a short introduction, hopefully up to date:
http://www.amigaforum.de/index.php?t....msg223#msg223
you need to remember than when booting strightly from hard drive you need to edit first line of startup sequence accordingly.

btw, try to boot to early startup and then with no s-s, with mouse buttons pressed, wanderer may need about 6mb to load.

other than that there may still be a bug in ata.device. last time i tried i had no problems to boot on an internal ide on an 1200, but on a4000 it was very flaky, and mostly remained stuck. perhaps its your problem. sorry for these messy comments, but i have not booted aros for a while, just from the top of my head.

[Samurai_Crow]

Stdc.library is the C runtime library. AROS is written in C so you can't boot AROS from an Amiga Kickstart ROM but you could boot AmigaOS from an AROS ROM.

[Toni Wilen]

AFAIK all reimplementations have too basic IDE drive implementation, most likely because it was based on KS ROM driver behavior.

KS ROM driver is extremely simple and works even if most ATA-1 requirements are not correctly implemented. I also got it wrong in UAE originally. (I based it on KS driver behavior, not what ATA-1 spec said)

[wawa]

Originally Posted by Samurai_Crow

Stdc.library is the C runtime library. AROS is written in C so you can't boot AROS from an Amiga Kickstart ROM but you could boot AmigaOS from an AROS ROM.

yes, i assume he is running aros from hd or image and due to lack of arosbootstrap line in the s-s while sofkinking aros is tring to run from amiga kickstart.

[chaos]

wawa: yes, I was missing the arosbootstrap in the s-s, thanks! Works now, well, sort of ...

toni wilen: it looks like you're right, thanks! For starters, I added CS and CFG registers for Gayle, although they don't seem to be needed (I will need them later anyway, for PCMCIA ethernet emulation). I'm still looking into other things missing.

The 'fun' part: I looked through the AROS sources, and in the ata_ReadSignature() function, one of the tests if there is a valid IDE device attached is that it reads the ATA Error register and expects to be set to 1 (= AMNF bit set, Address Mark Not Found). I looked through the ATA spec and I didn't find anywhere mentioning that the ATA Error register should have this bit set. Anyone have any idea? I just permanently set the error register to 1, and the test in AROS ata_ReadSignature() now passes. I don't particularly like this solution, though.

AROS still doesn't boot, as later I get "ATA interrupt but BUSY flag set!?" error, still looking into that (it shouldn't happen).

[Toni Wilen]

Originally Posted by chaos

ATA Error register and expects to be set to 1 (= AMNF bit set, Address Mark Not Found)

7.2.9 Error register
This register contains status from the last command executed by the drive or a Diagnostic Code.

<snip>

9.7 Execute drive diagnostic

<snip>

The Diagnostic Code written to the Error Register is a unique 8-bit code as shown in table 10, and not as the single bit flags defined in 7.2.9.

(This is from ATA-1, it is usually the best spec to look out for basic features because later specs have too much extra stuff that no one needs to care, only exception probably being LBA48..)

[chaos]

Missed that , thanks! I'll have to add support for the drive diagnostic command.

[terminills]

qqqqqqqaqqQA1

[clebin]

Originally Posted by terminills

qqqqqqqaqqQA1

Final Writer 2015 reaches the Quality Assurance phase...

[terminills]

Originally Posted by clebin

Final Writer 2015 reaches the Quality Assurance phase...

rofl iphone does ;D for the life of me that has got to be the first time I've ever pocket posted to forums

[Amiga1992]

Probably asked this before, sorry for being a noob, but I am unable to find the AROS ROM to test on my Amiga. The link wawa posted above links to i386 versions of Icaros.
Do I have to get that then copy files?
https://en.wikibooks.org/wiki/Aros/P...ctual_Hardware

[wawa]

Originally Posted by Akira

Probably asked this before, sorry for being a noob, but I am unable to find the AROS ROM to test on my Amiga. The link wawa posted above links to i386 versions of Icaros.
Do I have to get that then copy files?
https://en.wikibooks.org/wiki/Aros/P...ctual_Hardware

here:
http://aros.sourceforge.net/de/download2.php

in the 68k section.

zou will have to soft kick aros. i have not looked at it for a while and cannot be bothered in the middle of the night, but basically the instructions are here:
http://www.amigaforum.de/index.php?t....msg223#msg223

[prowler]

Originally Posted by Akira

Probably asked this before, sorry for being a noob, but I am unable to find the AROS ROM to test on my Amiga. The link wawa posted above links to i386 versions of Icaros.
Do I have to get that then copy files?
https://en.wikibooks.org/wiki/Aros/P...ctual_Hardware

You need to download only the amiga-m68k-boot binaries lha archive (1.89MB) from the AROS site to try the ROM on your Amiga. A bootable floppy disk image is included.

[gilgamesh]

Why is Aros ROM so big compared to the original Kickstart? Does it contain extra stuff or is it just not optimized for space?

[mfilos]

It's not big at all.
It's an 1MB ROM, which may not be near full
Most custom ROM images these days are 1MB anyway if you put some extra stuff.

[gilgamesh]

Ah ok, But this is still some way from the original 256kB, 512kB for V1.3 and V2.0 relatively speaking.

[wawa]

aros rom contains a lot of extra stuff like usb or rtg support.all enabled yet for 68k.

I had one question here, but I found the answer.
In short: the "uaequit" works also with aros rom.