[U-Boot] Antw: Re: How to start U-Boot for i.MX31 NAND out of RedBoot (out of RAM)
Wolfgang Denk
wd at denx.de
Tue Jul 14 13:13:57 CEST 2009
Dear "Ulrich Gerster",
In message <4A5C71DA0200004D00014C8A at hochblauen.ba-loerrach.de> you wrote:
>
> I can ping my linux host and I'm able to download a binary file via TFTP into RAM.
> But I'm not able to ping the boad with u-boot from my linux host. In my config-file I
> defined CONFIG_NETMASK and CONFIG_IPADDR. What could be wrong?
Nothing is wrong. That's expected and documented behaviour.
> Another strange thing is the nand driver. I build my u-boot with:
> #define CONFIG_MX31_NAND 1
> #define CONFIG_CMD_NAND
> #define CONFIG_SYS_NO_FLASH 1
> #define CONFIG_ENV_IS_IN_NAND 1
> #define CONFIG_SYS_NAND_BASE CS0_BASE
> #define CONFIG_SYS_MAX_NAND_DEVICE 1
> #define CONFIG_SYS_NAND_MAX_CHIPS 1
>
> If I then try to get "flinfo" information u-boot jumps to the next command line and prints nothing.
Seems you don't have NOR flash on your board, then (or no driver
configured for it).
> If I try "nand info" I get information about nand device 0.
OK.
> Another strange thing is that I can't read from nand flash but I can write.
That's indeed strange. How do you know you can write then when you
cannot read the data back for verification?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
When all else fails, read the instructions.
More information about the U-Boot
mailing list