MLO doesn't launch u-boot in NAND NOK

Hi,

Please post a log of your steps and explain what exactly are you trying to do.

Best regards,
Miroslav

Hello

i just want to be able to start linux from NAND (it is OK from SD card)

i programmed the MLO and the u-boot in nand. MLO starts but i never get access to u-boot (las printf is the one of MLO). 

thank for your help

Thank you for the clarification. Please let me know which version of the Sitara SDK you are using and if you are following the NAND layout shown here: http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide#NAND_Layout

Best regards,
Miroslav

Hello

thanks for your reply

I use SDK from Pengwyn SILICA, based on EVM board (u-boot-2012.10-psp05.06.00.00). Yes the laytout is exactly the one described in your link.

-U-boot starts well if we boot on SD-card

-MLO fails to start u-boot if we boot on NAND

Have you any idea ?

regards

Hello

do you know how i can generate the symbol file for SPL ( used in http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_uboot_linux_debug_with_ccsv5 link )?

I try to run the SPL to understand my NAND boot problem

regards

Trichet,

Only the last two SDK releases are supported here (v6.0 and v7.0). Your version of the SDK is really old and probably has a lot of bugs that have been fixed since then. At least try to update your U-Boot. As far as I can remember, your U-Boot requires you to manually set the ECC scheme before you write to the NAND flash. In later U-Boots, the default ECC scheme is BCH8 and it is automatically handled.

Best regards,
Miroslav

Hi

thanks for the reply

I don't think i have a NAND access problem, as every u-boot commands to load to/from NAND work well. I can load the u-boot in RAM and starts it with u-boot commands.

The pengwyn board use SDK based files and can boot from NAND.

Do you know how i can generate symbols file for SPL (what option to add to the generation ?) ?

regards

trichet christophe said:

Do you know how i can generate symbols file for SPL (what option to add to the generation ?) ?

The file is auto-generated when you build u-boot. Its name is just "u-boot" and it is located inside u-boot's root folder.

Best regards,
Miroslav

thanks for the reply,

i have a problem setting hardware breakpoint : i do Run -> Load -> Load Symbols -> uboot, then i set a HW breakpoint and i have the message no code is associated with "....board.c"

1° have you any idea of how to deal with this error ?

2) do we need to have something in the following section to be able to boot from NAND ?

->0x00260000-> ENV start
|            |
|            |
|            |-->0x0027FFFF-> ENV end

thanks

regards

1) Post this question to the Code Composer forum.

2) No, if the ENV section is empty, the U-Boot will use its built-in variables (assuming that your U-Boot has built-in variables). These are usually defined inside <u-boot>/include/configs/am335x_evm.h.

Best regards,
Miroslav

Hi

thanks for your reply

i tried another configuration : Boot Over UART (described in http://processors.wiki.ti.com/index.php/AM335x_U-Boot_User%27s_Guide#Boot_Over_UART)

The boad start the Xmodem download of SPL, but then i have no C char printed and no file transfert is possible any more

What may happen ?

regards

Boot Over UART

Hi,

Here are my successful steps, verified on the AM335x GP EVM. I'm using picocom.

1. Build U-Boot:

2. Save the generated MLO.byteswap and u-boot.img and also the u-boot-spl.bin from the ./spl folder.

3. Set the EVM switches for UART boot (1-5: 10000)

4. Start picocom from the folder containing the UART boot images (board is OFF):
# picocom -b 115200 /dev/ttyS0 --send-cmd "sx -vv"

5. Press CTRL+A; CTRL+S; to send the u-boot-spl.bin file via UART and then start the board.

6. After transfer is complete press CTRL+A; CTRL+S; to send the u-boot.img file.

7. After transfer is complete interrupt the boot sequence to enter U-Boot mode.

8. Transfer more files if needed.

IMPORTANT: Depending on whether you're using kermit or ymodem mode use one of these two U-Boot commands to load the image files to RAM:

loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)

Best regards,
Miroslav