[okl4-developer] okl4 on arm1136jfs goes haywire

Ashish Bijlani ashish.bijlani at gmail.com
Sat Jul 19 03:11:16 EST 2008


Hi,

I'm trying to run okl4 on arm1136jfs. The kernel seems to be going
haywire once virtual memory is switched on. Any ideas why? Am I not
passing memory info correctly? Could it be because of the compiler
flags?

The config file is pasted below :-

class Device(arm1136js):
    memory = arm1136js.memory.copy()
    cpp_defines = arm1136js.cpp_defines

class Board(Device):
    virtual = False
    memory = Device.memory.copy()
    memory['physical'] = [Region(0x80008000L, 0x88000000L)]

Please note that I'm compiling code for arm1136jfs and using configs
from arm1136js class in "arch/arm/tools/machine.py". I'm using
gcc-3.4.4.

Upon disassembling the image.boot, I can see kernel.kspace section is
loaded at 0x8002c00 (physical) and 0xf0024000 (virtual)



More information about the Developer mailing list