From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 974 invoked by alias); 25 May 2005 12:37:44 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 958 invoked by uid 22791); 25 May 2005 12:37:35 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 25 May 2005 12:37:35 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j4PCbVFA017378; Wed, 25 May 2005 08:37:31 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j4PCbVO28144; Wed, 25 May 2005 08:37:31 -0400 Received: from 172.16.50.38 (vpn50-38.rdu.redhat.com [172.16.50.38]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id j4PCbUsR002150; Wed, 25 May 2005 08:37:31 -0400 From: Mark Salter To: s.s-c-h-m-i-t-t@web.de Cc: ecos-discuss@ecos.sourceware.org In-Reply-To: <42926CAC.10903@web.de> References: <42926CAC.10903@web.de> Content-Type: text/plain; charset=ISO-8859-1 Date: Thu, 26 May 2005 08:47:00 -0000 Message-Id: <1117024650.31883.21.camel@gienah.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [ECOS] Problem booting Linux with Redboot v1.94 on IXP425 X-SW-Source: 2005-05/txt/msg00334.txt.bz2 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