{"id":315,"date":"2013-03-23T23:50:14","date_gmt":"2013-03-23T23:50:14","guid":{"rendered":"http:\/\/retroramblings.net\/?p=315"},"modified":"2023-01-27T20:36:20","modified_gmt":"2023-01-27T20:36:20","slug":"trials-tribulations-and-toolchains","status":"publish","type":"post","link":"https:\/\/retroramblings.net\/?p=315","title":{"rendered":"Trials, Tribulations and Toolchains"},"content":{"rendered":"

Edit:<\/strong> Future me, nearly 10 years later, says don’t bother attempting these steps unless you really have no alternative. My comment below about guides found on the net quickly becoming obsolete now applies to this post!<\/em><\/p>\n

If you’re using Ubuntu or a derivative, then the arm-none-eabi-… toolchain is now in the repos, so can easily be installed with apt, and there’s even an m68k gcc cross compiler too.<\/em><\/p>\n

<Historical content resumes…><\/em><\/p>\n

To build the OSD firmware for the Minimig projects, a cross-compilation environment is needed. Configuring GCC for this task can be an arcane process, and aspects tend to change from time to time, so guides found on the net quickly become obsolete. For instance, guides recommending the target “arm-elf” will fail with the latest GCC. Instead we need to use the target “arm-none-eabi”.<\/p>\n

Here’s how I built a toolchain for building both M68K (Chameleon Minimig port) and ARM (Original Minimig and MiST<\/a>) versions of the firmware:
\n
\nFirstly I downloaded the latest versions of Binutils, GCC and Newlib. At the time of writing these were: Binutils 2.23.1, GCC 4.8.0 and Newlib 2.0.0.<\/p>\n

Unpack all three tarballs into the same toplevel directory, then proceed as follows.
\nGCC is a bit of a special case when it comes to compiling. Rather than simply issuing the usual .\/configure \/ make \/ make install commands from the toplevel directory, we have to create a target-specific build directory, and issue the configure command from within. (This is compulsory for GCC. It’s not compulsory for binutils, but a good idea nonetheless, since we’re going to be building for two different targets.)<\/p>\n

cd binutils-2.23.1
\nmkdir arm-none-eabi
\ncd arm-none-eabi
\n..\/configure --target=arm-none-eabi --prefix=\/opt\/arm-none-eabi
\nmake
\nsudo make install
\ncd ..\/..\/<\/code><\/p>\n

Now we need to add the newly-compiled binutils to the PATH so they can be used when building GCC:<\/p>\n

export PATH=\/opt\/arm-none-eabi\/bin:$PATH<\/code><\/p>\n

Before building GCC we need to link newlib into it, like so:<\/p>\n

cd gcc-4.8.0
\nln -s ..\/newlib-2.0.0\/newlib .<\/code><\/p>\n

Now we can make a directory to hold build files, and build GCC.<\/p>\n

mkdir arm-none-eabi
\ncd arm-none-eabi
\n..\/configure --target=arm-none-eabi --prefix=\/opt\/arm-none-eabi --enable-languages=c --with-newlib
\nmake
\nsudo make install
\ncd ..\/..\/
\n<\/code><\/p>\n

That’s all there is to it. The toolchain is now complete enough to build the firmware<\/a> for the MiST project.<\/a> At the time of writing the makefile needs one small adjustment; it assumes that the toolchain has been built with the target “arm-elf” – but as mentioned earlier that target is no longer available, so just change the first line of the Makefile to read:
\nBASE = arm-none-eabi<\/code><\/p>\n

If we want an m68k toolchain the steps are almost identical:<\/p>\n

cd binutils-2.23.1
\nmkdir m68k-elf
\ncd m68k-elf
\n..\/configure --target=m68k-elf --prefix=\/opt\/m68k-elf
\nmake
\nsudo make install<\/code><\/p>\n

<\/code><\/code><\/p>\n

export PATH=\/opt\/m68k-elf\/bin:$PATH<\/p>\n


\n<\/code><\/p>\n

cd ..\/..\/gcc-4.8.0
\n# I assume you've already linked newlib in by this point, but if not:
\n# ln -s ..\/newlib-2.0.0\/newlib .
\nmkdir m68k-elf
\ncd m68k-elf
\n..\/configure --target=m68k-elf --prefix=\/opt\/m68k-elf --enable-languages=c --with-newlib
\nmake
\nsudo make install<\/code><\/p>\n

The only other thing needed for the m68k is VASM, which you can find here.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Edit: Future me, nearly 10 years later, says don’t bother attempting these steps unless you really have no alternative. My comment below about guides found on the net quickly becoming obsolete now applies to this post! If you’re using Ubuntu … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4],"tags":[],"class_list":["post-315","post","type-post","status-publish","format-standard","hentry","category-amiga","category-fpga"],"_links":{"self":[{"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/posts\/315","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/retroramblings.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=315"}],"version-history":[{"count":13,"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/posts\/315\/revisions"}],"predecessor-version":[{"id":1961,"href":"https:\/\/retroramblings.net\/index.php?rest_route=\/wp\/v2\/posts\/315\/revisions\/1961"}],"wp:attachment":[{"href":"https:\/\/retroramblings.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=315"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/retroramblings.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=315"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/retroramblings.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=315"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}