This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM3352: NAND flash boot

Part Number: AM3352


Tool/software: Linux

Hi,

Hardware: AM3352+NAND Flash(MT29F16G08ABACA)

Software:ti-sdk-am335x-evm-08.00.00.00

sysboot pins[0:15] = 0010 0000 0000 0000 0010

1.The customer can boot from sd card successfully

2.After enter uboot, he flash MLO and u-boot.img to nand flash

U-boot#mmc rescan

U-boot#nand erase 0x0 0x80000

U-boot#fatload mmc 0 0x82000000 mlo

U-boot#nand write 0x82000000 0x0 0x80000

U-boot#nand erase 0x80000 0x100000

U-boot#fatload mmc 0 0x82000000 u-boot.img

U-boot#nand write 0x82000000 0x8000 0x100000

He pulled out sd card after power off and then power again, serial port output CCCC all the time, nand bootup failure.

Can we use MLO which can boot from SD card and flash the same one directly to nand? If not, how to modify?

  • Hi,

    Please follow 

    Also please note that SDK 08.00.00.00 is obsolete and no longer supported by TI.

  • Hi,

    Thanks for quick reply. Could you please give some advise about that question? The link you shared seems has nothing with the question.

  • Sorry, the link did not copy correctly into the post. Here it is:

    processors.wiki.ti.com/index.php

  • Hi,

    The cusomer has referred to the link. And still failed to boot up from nand.

    Is it necessary to compile image file separately from SD card and nand flash? The customer has compared the am335x_evm_config and am335x_evm_nandboot_config configurations, and that two MLO are exactly the same.

    If configuration in am335x_evm.h does not match the actual nand flash, will it cause the rom code keep output CCC all the time?

  • Hi,

    Please help give some suggestions related to the above question.

  • Hello,

    As Biser mentioned earlier, we do not support SDK 08.00.00.00. Using the latest PSDK Linux, I was able to boot from NAND and I have attached my console log. I used the same images (MLO + u-boot.img) for NAND and SD card boot. Also, I used the following page as a reference for the boot switch configuration.

    Regards,
    Krunal

    mtdparts 
    
    device nand0 <nand.0>, # parts = 10
     #: name                size            offset          mask_flags
     0: NAND.SPL            0x00020000      0x00000000      0
     1: NAND.SPL.backup1    0x00020000      0x00020000      0
     2: NAND.SPL.backup2    0x00020000      0x00040000      0
     3: NAND.SPL.backup3    0x00020000      0x00060000      0
     4: NAND.u-boot-spl-os  0x00040000      0x00080000      0
     5: NAND.u-boot         0x00100000      0x000c0000      0
     6: NAND.u-boot-env     0x00020000      0x001c0000      0
     7: NAND.u-boot-env.backup10x00020000   0x001e0000      0
     8: NAND.kernel         0x00800000      0x00200000      0
     9: NAND.file-system    0x0f600000      0x00a00000      0
    
    active partition: nand0,0 - (NAND.SPL) 0x00020000 @ 0x00000000
    
    defaults:
    mtdids  : nand0=nand.0
    mtdparts: mtdparts=nand.0:128k(NAND.SPL),128k(NAND.SPL.backup1),128k(NAND.SPL.backup2),128k(NAND.SPL.backup3),256k(NAND.u-boot-spl-os),1m(NAND.u-boot),128k(NAND.u-boot-env),128k(NAND.u-boot-env.backup1),8m(NAND.kernel),-(NAND.file)
    => mmc rescan
    => fatload mmc 0 0x82000000 MLO
    110700 bytes read in 9 ms (11.7 MiB/s)
    => nand erase 0x0 0x20000
    
    NAND erase: device 0 offset 0x0, size 0x20000
    Erasing at 0x0 -- 100% complete.
    OK
    => nand write 0x82000000 0x0 0x20000
    
    NAND write: device 0 offset 0x0, size 0x20000
     131072 bytes written: OK
    => mmc rescan
    => fatload mmc 0 0x82000000 u-boot.img
    647952 bytes read in 43 ms (14.4 MiB/s)
    => nand erase 0xc0000 0xa0000
    
    NAND erase: device 0 offset 0xc0000, size 0xa0000
    Erasing at 0x140000 -- 100% complete.
    OK
    => nand write 0x82000000 0xc0000 0xa0000
    
    NAND write: device 0 offset 0xc0000, size 0xa0000
     655360 bytes written: OK
    => 
    => 
    U-Boot SPL 2018.01-g313dcd69c2 (Dec 16 2018 - 09:01:09)
    Trying to boot from NAND
    
    
    U-Boot 2018.01-g313dcd69c2 (Dec 16 2018 - 09:01:09 +0000)
    
    CPU  : AM335X-GP rev 2.1
    Model: TI AM335x EVM
    DRAM:  1 GiB
    NAND:  256 MiB
    MMC:   OMAP SD/MMC: 0
    <ethaddr> not set. Validating first E-fuse MAC
    Net:   cpsw, usb_ether
    Hit any key to stop autoboot:  0 
    => 
    

  • Hi Krunal,

    Thanks for your reply! I know the sdk the customer used dose not support any more and i will suggest the customer to use the latest sdk. In addtion, please help follow this post if the customer has another related question.

  • Hi Nancy,

    In the meantime, I will be closing the thread but if the customer has any follow up question, please feel free to open the thread.

    Regards,
    Krunal