SERDATR bit 13 also needs to work correctly.

Note that AROS early boot assumes correctly working memory (and custom chipset) mirroring, used for model and hardware detection. (Gayle, A3000/A4000 32-bit MB RAM regions etc..)

Missing second ROM file won't prevent early boot to work, something will be output to serial port before it freezes or crashes.

Thanks for clearing things out.

I tried out the adf, which also should allow to boot AROS.
It fails with 'boot/aros.hunk.gz': Can't parse, error 103'.

Looking in the sourcecode of AROS I see that function ROMLoad of AROSBootstrap.c is failing. When calling InternalLoadSeg_ELF the output value rom stays NULL.

Now looking into why function InternalLoadSeq_ELF is unsuccesfull...

Chipram was not set to 2Mb and after fixing this, it did not fail anymore on above error.
After the ELF file is succesfully loaded, the screen is cleared and goes to nearly black.

It seems to reach the same point as the starting WinFellow with the AROS ROM-file.

I guess I have to check which errors are written to the serial port?

This thread has been closed and the discussion on support for the AROS rom can be continued here.