This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Booting Linux from arm


Gilles Bulthé wrote:
> Hello,
> 
> I have difficulties to boot Linux Kernel from my xm27 based platform, and am
> wondering whether there is link with RedBoot or not.
> My customized RedBoot starts as following :
> 
> ----------- StartOfQuote-------------------------------------------
> 
> ... Read from 0x03ee0000-0x03f00000 at 0xa0060000: .
> ... Read from 0x03ed3000-0x03ed4000 at 0xa007f000: .
> Turning on PMIC regulators: 1,2,3,4,5
> Unrecognized chip: 0xf8!!!
> hardware reset by WDOG
>              
> Clock input is 24 MHz
> Booting from [NOR flash]
> 
> RedBoot(tm) bootstrap and debug environment [ROMRAM] Non-certified release,
> version FSL 200904 - built 16:22:29, May 22 2009
> 
> 
> Platform: Freescale (i.MX27 )  PASS 1.0 [x32 DDR] Copyright (C) 2000, 2001,
> 2002, 2003, 2004 Red Hat, Inc.
> Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited
> 
>  
> RAM: 0x00000000-0x03f00000, [0x0000eb78-0x03ed1000] available
> FLASH: 0xa0000000 - 0xa4000000, 512 blocks of 0x00020000 bytes each.
> RedBoot>
> RedBoot> load -r -m xmodem -b 0x100000
> CRaw file loaded 0x00100000-0x0028940f, assumed entry at 0x00100000 xyzModem -
> CRC mode, 12585(SOH)/0(STX)/0(CAN) packets, 1 retries
> RedBoot> exec
> entry=0x80008000, target=0x80008000
> Using base address 0x00100000 and length 0x00189410 Uncompressing
> Linux.........................................................................................................
> done, booting the.
> 
> ------------EndOfQuote-----------------------------------------------------------
> and then, it stops.
> 
> 
> I see "RAM: 0x00000000-0x03f00000, [0x0000eb78-0x03ed1000] available"
>                -> why is not all the RAM available ?

RedBoot uses the RAM which is listed as "not available"

> And : "entry=0x80008000, target=0x80008000"
>                -> this entry point 0x8008000 is then out of available range,
> isn't it ? Is it possible to change it ?

There are options to 'exec' for this.  Try 'help exec' :-)

Also, the address '0x80008000' is a PHYSICAL address.  The addresses printed
by RedBoot (available range, etc) are LOGICAL addresses - not the same.

> 
> Regarding my ARM Linux sources and debugging with LED, I have notice that
> Linux bugs from the moment when it "__turn_mmu_on". There may be a link.
> I am now thinking that the MMU and the memory related lines quoted above may
> have link, but do not really know how.
> 
> If you have any idea about what's going on, it would be very helpfull !
> Thank you in advance for reading me.
> Gilles.
> 

You really should ask these questions on the Linux-ARM lists, not here,
as they have basically nothing to do with eCos/RedBoot.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]