Booting on Raspberry Pi

Adam Lackorzynski adam at
Thu Sep 12 08:55:09 CEST 2013

Hi Robert,

On Wed Sep 11, 2013 at 07:02:52 +0200, Robert Kaiser wrote:
> Robert Kaiser wrote:
> > Hello Adam
> > 
> > Robert Kaiser wrote:
> >> Just tried a rawimage -> still silence on the serial port :-(. It may be
> >> due a configuration mistake.
> >> I guess I'll have to wade through the code to find out where it goes
> >> wrong -- stay tuned.
> > 
> > I've tracked it down a little further:
> > 
> > Booting a rawimage basically works, i.e. the bootloader copies itself
> > the right place in memory and starts executing. It gets to the point
> > where it wants to print its first message -- and that's where it crashes
> > :-(.
> > 
> > The crash happens during a division computed in fputs.c. The compiler
> > calls a libgcc routine named __aeabi_uidiv which apparently throws an
> > exception. (However it is *not* a divide by zero exception -- I have
> > checked the values).
> > 
> > Time to try a different toolchain, I guess. So far, I have been using
> > the linaro toolchain (gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux).
> > Can you please tell me which toolchain you have used (and where to
> > obtain it)?
> OK, I read somewhere else that the Codesourcery toolchain is
> recommended. (You have to register with Mentor to obtain it which is why
> I initially chose the linaro toolchain). Anyway: I recompiled everthing
> with arm-2013.05/arm-none-linux-gnueabi. This fixed the crash problem,
> so the linaro toolchain is definitely broken!

Ok, thanks for letting us know. Sometimes I also see somewhat strange
behaviour in those toolchains but did not take the time to pinpoint
anything. Definitely I used the 4.5-based codesourcery when I did the
rpi. (But this definitely needs checking.)

> Unfortunately, it *still* doesn't work. The last messages I see trying
> to run the bootstrap_hello example are:
> MOE: cmdline: moe --init=rom/hello
> MOE: Starting: rom/hello
> MOE: loading 'rom/hello'
> L4Re: unhandled exception: pc=0xffffff9c
> Any hints what could be wrong now?

Would be interesting to know where this is coming from (lr). Anyway,
this does not look so bad because quite a few things have happened
again. For which architecture version have you been building?

Adam                 adam at

More information about the l4-hackers mailing list