Sauce.Cheng wrote:
i tried
CONFIG_PPC_EARLY_DEBUG_CPM=y
CONFIG_PPC_EARLY_DEBUG_CPM_ADDR=0xf0008
how can i make sure CPM_ADDR, 0xf008 is default value
Look at the u-boot source, or dump the memory and see if it looks like a
ring buffer.
sorry, i mean that CPM_ADDR is address of wha
evolution! kernel 2.6.11 has run on the board with u-boot 1.1.4, also, at
early booting time LEDs are disabled due to MMU on and off. so i tried to
turn LEDs on after start_kernel function, wow, blinking! that is before
start_kernel will be done successfully. then i modified registers mapping in
i
thanks Scott 's following
> I don't quite follow the above, but what I meant is that you need to
> put a mapping in place that covers your LED I/O once you have the MMU on.
> Any mappings that U-boot made will be gone at that point.
i am sorry for my poor expression. i think i have got your mean
On Thu, 2009-04-02 at 11:12 -0500, Scott Wood wrote:
> On Wed, Apr 01, 2009 at 08:23:42PM -0700, Sauce.Cheng wrote:
> > > I don't see where you set up a BAT that covers 0xf000.
> >
> > if i have to set up a BAT that cover 0xF000. i had a debug with LEDs
> > like that in u-boot code. everyt
On Wed, Apr 01, 2009 at 08:23:42PM -0700, Sauce.Cheng wrote:
> > I don't see where you set up a BAT that covers 0xf000.
>
> if i have to set up a BAT that cover 0xF000. i had a debug with LEDs
> like that in u-boot code. everything is //normal. 0xF is the value
> of CFG_IMMR(CONFIG
thanks Scott
> Another thing that would generally be good is to keep replies on the
> list rather than taking it to private e-mail as soon as someone replies.
> Someone else may have something helpful to say based on your followup,
> or may have the same problem and be helped by the conclusion.
thanks Scott!
> That is very old code; you're more likely to get help when running
> something up-to-date.
i have a latest u-boot-2009.03 updated instead of mine, and kernel version
is instead of 2.6.24.5
> This alternative was listed as text/plain. is not plaintext.
> Please fix your maile
On Fri, Mar 27, 2009 at 04:36:28PM +0800, chmhou wrote:
> there is something confused me, which is my kernel code is halt because of
> something wrong i have no hint about it.
> my bootloader is u-boot, version is 1.1.4, kernel version is 2.6.14.1,
> processor is MPC8247.
That is very old code;
