ColdFire Project?

[Donar]

What about the Dragon then?

Oh i wrote some e-mails to Elbox, one answer said they were polishing drivers, the next they were readying production.
And that was umm, half a year ago.

I fear they showed a Dragon from which only the PCI part was working probably using the 020 of the host A1200. Everybody mentioned that it was slow e.g. on loading Icons.

I said AROS, not AmigaOS, so you could compile it for the right cpu faily.

Any body here who want's to bring the AROS 68k port out of unmaintained, where it sits for long now?
AROS Kickstart ROM Replacement Phase I

You just have to edit the AROS 68K source code before compiling replacing the offending code with coldfire acceptable code.

I think the AROS code is in c or c++ so a simple recompile to Coldfire or 68k/Coldfire mixed code should do the trick without editing the source. That only would be needed if the source is in assembler.

[Donar]

To make clean coldfire builds, you'll need to edit legacy 68K code to replace these missing and misinterpeted instructions. Luckily the list of edits will probably be small.

From C++ Source you only need to set Coldfire as target for the compiler - it will avoid "bad" instructions then.

If you have Assembler source you have to run it through "PortASM" (tool provided by freescale) or pick the bad ones out by hand and replace them.

Another option, if you don't have the source, would be to disassemble an executable pick out the "baddies" and assemble it to an executable or provide a patch file for the original executable. That probably is the least desired thing.

That's at least how i understood it.

[Donar]

Wasn't there a tool to convert 68k assembly to coldfire assembly?

The Name of the Tool is "PortASM" from MicroAPL.

If there is one, it should be possible to create coldfire binaries for the whole OS using a suitable disassembler and this tool.

I had the same idea but i got several errors - i must admit i know nothing about what i was doing there...