Yes, i think so.
2010/12/8 Mike Frysinger
> 2010/12/7 Chong Huang :
> > Replace the 2009 toolchain with the 2010R1-RC4 one, will solve this
> problem.
>
> cool. so current trunk works fine for you without modification ?
> -mike
>
___
U-Boot-devel mail
2010/12/7 Chong Huang :
> Replace the 2009 toolchain with the 2010R1-RC4 one, will solve this problem.
cool. so current trunk works fine for you without modification ?
-mike
___
U-Boot-devel mailing list
U-Boot-devel@blackfin.uclinux.org
https://blackfi
Replace the 2009 toolchain with the 2010R1-RC4 one, will solve this problem.
regards.
2010/12/1 Mike Frysinger
> 2010/12/1 Chong Huang
> > Adding the read code back, the kernel can be autoboot up fine.
> >
> > --- drivers/mtd/spi/eon.c(版本 2513)
> > +++ drivers/mtd/spi/eon.c(工作副本)
> > @@
2010/12/1 Chong Huang
> Adding the read code back, the kernel can be autoboot up fine.
>
> --- drivers/mtd/spi/eon.c (版本 2513)
> +++ drivers/mtd/spi/eon.c (工作副本)
> @@ -240,7 +240,13 @@
> const struct eon_spi_flash_params *params;
> struct eon_spi_flash *eon;
> unsigned int i;
>
Hi, mike:
CONFIG_EXTRA_ENV_SETTINGS value isn't the cause.
Adding the read code back, the kernel can be autoboot up fine.
--- drivers/mtd/spi/eon.c(版本 2513)
+++ drivers/mtd/spi/eon.c(工作副本)
@@ -240,7 +240,13 @@
const struct eon_spi_flash_params *params;
struct eon_spi_flash *eon
2010/12/1 Mike Frysinger
> On Tue, Nov 30, 2010 at 06:47, Chong Huang wrote:
> > I found a problem, when the board autoboot into kernel, it will get
> error
> > like:
> >
> > Hit any key to stop autoboot: 0
> > 16384 KiB EN25Q128 at 0:1 is now current device
> > Wrong Image Format for bootm com
On Tue, Nov 30, 2010 at 06:47, Chong Huang wrote:
> I found a problem, when the board autoboot into kernel, it will get error
> like:
>
> Hit any key to stop autoboot: 0
> 16384 KiB EN25Q128 at 0:1 is now current device
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
>
> T
I found a problem, when the board autoboot into kernel, it will get error
like:
*
Hit any key to stop autoboot: 0
16384 KiB EN25Q128 at 0:1 is now current device
Wrong Image Format for bootm command
ERROR: can't get kernel image!*
The 'printenv' result is something like:
..
*bootcmd=run sfbo
On Tue, Nov 30, 2010 at 01:46, Chong Huang wrote:
> Thanks, Mike. Hope this time it's ok.
i noticed the EON spi driver had a useless idcode read in its probe
func, so i punted that and committed to trunk. please double check
that current trunk works for you still.
-mike
__
Thanks, Mike. Hope this time it's ok.
2010/11/29 Mike Frysinger
> On Mon, Nov 29, 2010 at 06:42, Chong Huang wrote:
> > We use a new board named bf525-ucr2 for robot control which has a bf525
> > processor. Click to see it. Here is the robot. There is a cFeon EN25Q128
> > flash on it. The first
On Mon, Nov 29, 2010 at 06:42, Chong Huang wrote:
> We use a new board named bf525-ucr2 for robot control which has a bf525
> processor. Click to see it. Here is the robot. There is a cFeon EN25Q128
> flash on it. The first patch is the flash driver. You can find the chip's
> data sheet at http://w
11 matches
Mail list logo
