Compiling Rockbox for m200

[rickbronson]

Rockboxers,

  I can do a m200 bootloader compile and run but when I try to compile a rockbox "normal build" I get:

...
LD vorbis.elf
/usr/local/arm-elf/lib/gcc/arm-elf/4.0.3/../../../../arm-elf/bin/ld: region PLUGIN_RAM is full (/home/rick/in/rockbox/normalbuild/apps/codecs/vorbis.elf section .header)
/usr/local/arm-elf/lib/gcc/arm-elf/4.0.3/../../../../arm-elf/bin/ld: region PLUGIN_RAM is full (/home/rick/in/rockbox/normalbuild/apps/codecs/vorbis.elf section .text)
/usr/local/arm-elf/lib/gcc/arm-elf/4.0.3/../../../../arm-elf/bin/ld: error: no memory region specified for loadable section `.icode'
collect2: ld returned 1 exit status
make[2]: *** [/home/rick/in/rockbox/normalbuild/apps/codecs/vorbis.elf] Error 1
make[1]: *** [build-codecs] Error 2
make: *** [build] Error 2

  Any help greatly appreciated!

  Rick

[MarcGuay]

I'm pretty sure the bootloader build includes all that's been done up to this point.

[LambdaCalculus]

Instead of just typing "make", type "make bin" if you just want to work with a normal build.

Remember to have tcctool compiled and ready for afterwards, so you can upload the code to your m200.

[MarcGuay]

Pardon my ignorance on this, but in the early stages of a port, what exactly is the difference between the bootloader build and the regular build? 

[LambdaCalculus]

The bootloader build is what you see in the picture I posted in this message:

http://forums.rockbox.org/index.php?topic=7727.msg125580#msg125580

The normal build just displays "*PANIC*" and some garbage characters on the screen.

[shotofadds]

I'm pretty sure the 'normal' builds for M200 / Logik DAX aren't much use at this stage (after all, how is the bootloader going to load it with no NAND driver ). But still, if the build is only failing with IRAM full errors at the linker stage, try adding the following to firmware/export/config-m200.h

Code: [Select]

/* Reduce Tremor's ICODE usage */
#define ICODE_ATTR_TREMOR_NOT_MDCT

Pardon my ignorance on this, but in the early stages of a port, what exactly is the difference between the bootloader build and the regular build? 

Quite simple: the bootloader is a tiny subset of the Rockbox codebase, which exists only to load the "normal" image. The reason for splitting it in this way is so that the small bootloader image can be easily patched into an original firmware image and flashed to the device, to allow dual-booting between the OF and Rockbox.

[MarcGuay]

The normal build just displays "*PANIC*" and some garbage characters on the screen.

That's what I figured... So why would someone want to run that?  

(Answering my own question: I suppose if they were working on the code and wanted to see the results).

[linuxstb]

@rickbronson,

That's perfectly normal - Rockbox is nowhere near finished on the m240.  The specific problem you're seeing is that the codecs don't compile.    The main Rockbox binary has already been compiled (you'll see a apps/rockbox.bin file in your build directory), and if you type "make bin", only this file will be compiled (meaning you won't see those errors, as the codecs are not compiled).

@MarcGuay,

A bootloader build consists of the code in firmware/, plus the code in bootloader/

The main Rockbox build consists of the code in firmware/, plus the code in apps/

In the early stages of a port (when not all the drivers are written and working), the bootloader is a nice way to test and develop drivers - it's easy to gradually add features to the bootloader as the relevant driver is implemented.  Once they're all working, work can start on the (relatively minor) parts  that are only used by the apps/ code - the sound driver normally being the main one.

The lack of a NAND driver makes attempting to run the main Rockbox binary at this stage pretty pointless.