[ECOS] exec kernel with cvs ecos
Fri Nov 17 09:43:00 GMT 2006
Fixed it. sorry for the post.
I would like to know though, why I have to specify the physical address
exec -c "root=/dev/ram console=ttyAM" 0xc0080000
I didnt use to.
any ideas as to why I have to now with the new ecos code?
On Thu, 2006-11-16 at 21:26 -0600, Brian Austin wrote:
> I have been using ecos-2.0 for quite some time and have moved up to a
> daily snapshot.
> I have moved my code over and am able to get redboot running on the
> board. I can init flash, setup net and all the good stuff.
> However, when I exec the kernel I get
> Using base address 0x00080000 and length 0x00128938
> My watchdog even resets the board.
> I do not see an uncompress kernel message, so I am assuming it is
> something in redboot.
> My question is... What has changed in the core that would break code
> from ecos-2.0?
> Are there new values for variables that have changed?
> I have looked at other ARM9 platforms and they seem pretty much the
> Here is my full output.
> +Ethernet eth0: MAC address 0e:00:00:ea:18:f0
> IP: 192.168.1.2/255.255.255.0, Gateway: 192.168.1.1
> Default server: 192.168.1.1
> RedBoot(tm) bootstrap and debug environment [ROMRAM]
> Non-certified release, version UNKNOWN - built 19:44:35, Nov 16 2006
> Platform: Cirrus Logic EDB9315A Board (ARM920T) Rev A
> Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
> Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited
> RAM: 0x00000000-0x04000000, [0x00042ee0-0x03fdd000] available
> FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
> RedBoot> load -v -r -b 0x100000 9315A/zImage
> Using default protocol (TFTP)
> Raw file loaded 0x00100000-0x00228937, assumed entry at 0x00100000
> RedBoot> exec -c "root=/dev/ram console=ttyAM"
> Using base address 0x00100000 and length 0x00128938
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss