Rockbox Development > Starting Development and Compiling

Compiling Rockbox for m200

<< < (2/2)

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: ---/* Reduce Tremor's ICODE usage */
#define ICODE_ATTR_TREMOR_NOT_MDCT
--- End code ---


--- Quote from: MarcGuay on May 30, 2008, 01:38:33 PM ---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? 

--- End quote ---

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:

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

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.

Navigation

[0] Message Index

[*] Previous page