[U-Boot] Antw: Re: How to start U-Boot for i.MX31 NAND out of RedBoot (out of RAM)
Hello.
Magnus Lilja lilja.magnus@gmail.com 09.07.09 19.08 Uhr >>>
I made the defines you mentioned above and build the image with make mx31guf_config (it's quite similar to the PDK board). Then I loaded the resulting u-boot.bin to 0x81000000 and tried to "run 0x81000000". The "run" command is with caches and MMU tured off. I get absolutely no output on the console and I have to reset the board. What could be the problem? How can I debug this?
Did you define CONFIG_SKIP_RELOCATE_UBOOT? If so, that may be the problem (although I'm not 100% sure) if TEXT_BASE is not 0x81000000 (in your board config.mk). For most i.MX31 boards TEXT_BASE is 0x87f00000.
That was the point. Now I'm able to boot u-boot out of the RAM. It's working well but I have some issues.
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?
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. If I try "nand info" I get information about nand device 0. Another strange thing is that I can't read from nand flash but I can write.
Do you have any suggestions?
Thanks. Ulrich Gerster
Hi
2009/7/14 Ulrich Gerster gersteru@dhbw-loerrach.de:
Hello.
Magnus Lilja lilja.magnus@gmail.com 09.07.09 19.08 Uhr >>>
I made the defines you mentioned above and build the image with make mx31guf_config (it's quite similar to the PDK board). Then I loaded the resulting u-boot.bin to 0x81000000 and tried to "run 0x81000000". The "run" command is with caches and MMU tured off. I get absolutely no output on the console and I have to reset the board. What could be the problem? How can I debug this?
Did you define CONFIG_SKIP_RELOCATE_UBOOT? If so, that may be the problem (although I'm not 100% sure) if TEXT_BASE is not 0x81000000 (in your board config.mk). For most i.MX31 boards TEXT_BASE is 0x87f00000.
That was the point. Now I'm able to boot u-boot out of the RAM. It's working well but I have some issues.
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 here. As far as I know, the networking in U-boot is not running in background, i.e it's only on/enabled when u-boot itself issues a ping-command, tftp or something similar.
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. If I try "nand info" I get information about nand device 0. Another strange thing is that I can't read from nand flash but I can write.
Do you have any suggestions?
The only i.MX31 NAND driver I've used in U-boot is the one I submitted to the list last year but it was rejected. Other people have sent updated drivers (I think there was a i.MX27 driver posted not long ago), but I haven't tried these. Even so, the CONFIG_SYS_NAND_BASE looks incorrect but I don't know if that's the only problem.
Regards, Magnus Lilja
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?
Best regards,
Wolfgang Denk
participants (3)
-
Magnus Lilja -
Ulrich Gerster -
Wolfgang Denk