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.

[OMAP3530] 128 Mb Micron NAND Flash

Other Parts Discussed in Thread: OMAP3530

Hi,


I am using OMAP3530 (X3530BCUS) at 12 Mhz, Micron NAND at GPMC CS0, SMSC9220 at GPMC CS3, Micron Memory at SDRC CS0.
I require to Boot from NAND but am not able to detect the NAND Device ID. The Ethernet and DDR is working properly and I have verified the L3 clock at 166Mhz.

I have noticed that the processor Boot code is trying a flash access and the flash also responds with a busy-wait.
But with x-loader, I see no busy-wait toggle, although all NAND control signals are present correctly.

The GPMC settings as in the x-loader are as follows:

# define M_NAND_GPMC_CONFIG1 0x00001800
# define M_NAND_GPMC_CONFIG2 0x00141400
# define M_NAND_GPMC_CONFIG3 0x00141400
# define M_NAND_GPMC_CONFIG4 0x0F010F01
# define M_NAND_GPMC_CONFIG5 0x010C1414
# define M_NAND_GPMC_CONFIG6 0x1F0F0A80
# define M_NAND_GPMC_CONFIG7 0x00000C44

The NAND Part is:MT29F1G16ABCHC-ET:C
Ethernet Device is: SMSC 9220.
I am using Mistral SDK.

 

Any Idea what might be the problem. The X-loader detects the sys_clock automatically by using the 32k clock. Other than that the GPMC settings are quite common. I cannot declare that the NAND is dead because the boot-code gets the ready-busy to toggle. But when I connect CCS or load x-loader it stops responding.

  • I am using a 12MHz crystal oscillator where as the Evm is using a 26MHz square wave input. Will this have possibly any issues with the GPMC operation.

    I have verified all the control signals on the GPMC, they all look fine.

    If boot code is able to detect the NAND, and I am able to see all the control signals when x-loader is running, why will the NAND not respond with x-loader (ready-busy not toggling).