From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Lange Date: Mon, 24 May 2004 21:53:35 +0200 Subject: [U-Boot-Users] AMD dbau1550 In-Reply-To: <1085412151.21246.50.camel@fortress> References: <1085412151.21246.50.camel@fortress> Message-ID: <40B252BF.1010106@corelatus.se> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de The first thing I would check, is the parameters passed to kernel. E.g. wrong memory size will make things really bad. Default behaviour for dbau1x00 u-boot is to pass mem size in bytes. Does your kernel expect that? I suggest activating DEBUG macro in lib_mips/mips_linux.c /Thomas Leif Lindholm wrote: > Hi > > I've been working on getting u-boot 1.1.1 up and running on , > in little endian mode (which someone asked for a few days ago I > believe). > > I've been able to get as far as "Starting kernel ..." after downloading > the kernel u-boot image through tftp. > > I know this tecnically means u-boot is finished, however the same kernel > (in srec format) boots fine from the original yamon loader on the board. > > When I halt the processor through jtag (bdi2000), the PC is always at > 0xbfc00424 (somewhere in ROM exception land?). > > The loaded image has been configured using > tools/mkimage -C gzip -a 0x80100000 -e 0x80246040 -A mips -O linux -T kernel -d vmlinux.gz vmlinux.u-boot > > 0x80246040 is the location of "kernel_entry". > > Does anyone have any hints about how I could work my way past this problem? > > regards > / > Leif > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users >