Hello,

...

...

...

Wolfgang Denk wd@denx.de 14.07.09 13.22 Uhr >>>

Dear "Ulrich Gerster",

In message 4A5C71DA0200004D00014C8A@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?

Your're right. I only use NAND Flash. At the moment I'm starting u-boot out of RAM using RedBoot. I'm assuming that U-Boot is writing something to the NAND Flash because if I enter a commad in U-Boot like "saveenv" or "nand write" my RedBoot is not working anymore after that. I have to reprogramm RedBoot in the Flash before I can boot it again.

Thanks for helping. Best Regards Ulrich Gerster