[ECOS] Problem booting Linux with Redboot v1.94 on IXP425

[ECOS] Problem booting Linux with Redboot v1.94 on IXP425

[s.s-c-h-m-i-t-t]

Hi there,

After updating to Redboot´s v1.94 I can´t boot the 2.4.19-rmk6 kernel 
any more. I adapted Redboot successfully (I guess) for my IXP425-Target 
which has no PCI NIC, 128MB SDRAM and the second UART only usable.

After initializing Redboot (fis init) I load the zImage and start it:

 > load -r -v -b 0x01600000 zImage
 > go 0x01600000

After this there is no message any more. The kernel seems to stick - 
BID2000, however, says the target is running. The same with prebuilt 
uClinux Images for the ixdp425.

When doing this with the old v2.00 (v1.5) Redboot with the kernel 
everything works fine.

Any comments or hints???

Regards,
Stefan.


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

Re: [ECOS] Problem booting Linux with Redboot v1.94 on IXP425

[Mark Salter]

On Tue, 2005-05-24 at 01:52 +0200, s.s-c-h-m-i-t-t@web.de wrote:
> Hi there,
> 
> After updating to Redboot´s v1.94 I can´t boot the 2.4.19-rmk6 kernel 
> any more. I adapted Redboot successfully (I guess) for my IXP425-Target 
> which has no PCI NIC, 128MB SDRAM and the second UART only usable.

You did this with 1.94?

> 
> After initializing Redboot (fis init) I load the zImage and start it:
> 
>  > load -r -v -b 0x01600000 zImage
>  > go 0x01600000

You should probably use the "exec" command. Older kernels could be
started by "go", but later ones need "exec". Something like:

  RedBoot> exec -b 0x01600000 -l 0 0x01600000

would be equivalent to the go command (except that exec will turn
off the MMU).

> 
> After this there is no message any more. The kernel seems to stick - 
> BID2000, however, says the target is running. The same with prebuilt 
> uClinux Images for the ixdp425.
> 
> When doing this with the old v2.00 (v1.5) Redboot with the kernel 
> everything works fine.

Are you building the kernel with BDI2000 support built in? Doing so
adds a "break" insn early in the boot process. The old v1.5 RedBoot
would setup the CPU debug unit so that the "break" insn is ignored.
v1.9x enables the debug unit so that the "break" actually causes
the kernel to stop.

--Mark



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