[U-Boot] adding NAND support for omap4 (based on pandaboard)

Gupta, Pekon pekon at ti.com
Thu Nov 28 13:11:04 CET 2013


From: Abraham V. [mailto:abraham.varricatt at vvdntech.com] 

> 1. Added NAND as a configuration option in boards.cfg
> 
Yes this is correct ..

[...]

> 2. Added NAND support in omap4_common.h configuration file
>  as below (Just copied the lines from am335x_evm.h
> --- a/include/configs/omap4_common.h
> +++ b/include/configs/omap4_common.h
> 
These changes look ok.. 

[...]

> 3. Edited omap4_panda.h to prevent a compilation error
>  (The ENV gets setup as NAND thanks to earlier change);
> 
This should be in include/configs/omap4_common.h itself
#if defined(CONFIG_NAND)
	#undef CONFIG_ENV_IS_NOWHERE
	#define CONFIG_ENV_IS_IN_NAND
#endif

[...]

> 4. Copied over 2 header files from arch-omap3 to arch-omap4
>  (since they are from the same processor family, I'm hoping it will work)
> cp arch/arm/include/asm/arch-omap3/mem.h \
		 arch/arm/include/asm/arch-omap4/mem.h

I'm about to send the patch for fixing this..  However you can proceed
Like this for now..

> cp arch/arm/include/asm/arch-omap3/omap_gpmc.h 
		arch/arm/include/asm/arch-omap4/omap_gpmc.h

This should not be required if you pull in my below patch-set
http://lists.denx.de/pipermail/u-boot/2013-November/167696.html

[...]

> 5. Edited cpu.h to add a few structure members needed
>  for BCH error correction (compiler complains they are missing otherwise);
> 
Again, this should not be required if you pull in patch mentioned above

[...]

> 6. Adding a #define in omap.h to allow NAND driver to compile
> (The value of ELM_BASE was copied over from
> arch/arm/include/asm/arch-am33xx/hardware.h)
> 
Please double check the OMAP4 TRM, ELM_BASE shouldn't change though.

[...]

> With the above, I'm able to compile u-boot.img, but am
>  having trouble with the SPL. Here's where the build fails,
> 
Please pull in my above patch-set mentioned above, and it should
Solve this compilation issue.. 
The patch is compile clean as tested with ./MAKEALL -s omap4 


> Any suggestions on how I could fix this? I can't seem to figure out how
>  SPL is built and am not sure where to start.
Plz pull the patch mentioned above, and much of things should be cleaned up
http://lists.denx.de/pipermail/u-boot/2013-November/167696.html


>  Assuming that we can solve
>  this issue, I can submit a proper patch after running it on real hardware
> (which should arrive in about 2 - 4 weeks).
Thanks..

> Puzzled,
?? why ?? Its ok, you will figure the solution :-)
(Also plz send plain text emails on u-boot maillist, no HTML please).


with regards, pekon


More information about the U-Boot mailing list