public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2
@ 2012-03-06  3:13 Bud Miljkovic
  2012-03-06  6:42 ` Dirk Behme
  2012-03-06 12:53 ` Fabio Estevam
  0 siblings, 2 replies; 3+ messages in thread
From: Bud Miljkovic @ 2012-03-06  3:13 UTC (permalink / raw)
  To: u-boot

Hi Fabio,

 

I understand, from the MAINTAINERS file list, that you are the
maintainer for the mx53ard board.  I took a copy of the u-boot sources
for the Freescale SABRE Automotive Infotainment board (aka mx53ard
board) from the Freescale site.  As the result I got the u-boot-2009.08
building tree directory along with the associated cross compiler
gcc-4.4.4-glibc-2.11.1-multilib-1.0-1.386 tools.

 

After some trial and error I managed to configure the mx53_ard_dd3.h for
NAND and YAFFS2 support and successfully ran make, resulting in creation
of the following files:

*         u-boot

*         u-boot.bin

*         u-boot.srec

*         u-boot.map

*         u-boot.lds

 

However, I would want to initially boot from SD-card and I would like to
be able to generate an imx image of the u-boot when running make.  I
looked at the Makefile from the Freescale release of u-boot-2009.08 and
saw that it is fairly outdated - it does not support making of
u-boot.imx image.  At the same time I see that the general denx
distribution (u-boot-2011.12) of u-boot sources does have the support
for making u-boot.imx image in its Makefile.  So I am wondering if a
patch that can be applied to the u-boot-2009.08 Freescale u-boot source
that will bring the make tools up to date and able to make u-boot.imx
file does exist?

 

Failing that, is there another way to configure the denx u-boot-2011.12
release to support NAND and YAFFS2 and thus, by successfully compiling,
generate a u-boot.imx image file.

 

Cheers,

Bud Miljkovic

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2
  2012-03-06  3:13 [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2 Bud Miljkovic
@ 2012-03-06  6:42 ` Dirk Behme
  2012-03-06 12:53 ` Fabio Estevam
  1 sibling, 0 replies; 3+ messages in thread
From: Dirk Behme @ 2012-03-06  6:42 UTC (permalink / raw)
  To: u-boot

On 06.03.2012 04:13, Bud Miljkovic wrote:
> Hi Fabio,
> 
>  
> 
> I understand, from the MAINTAINERS file list, that you are the
> maintainer for the mx53ard board.  I took a copy of the u-boot sources
> for the Freescale SABRE Automotive Infotainment board (aka mx53ard
> board) from the Freescale site.  As the result I got the u-boot-2009.08
> building tree directory along with the associated cross compiler
> gcc-4.4.4-glibc-2.11.1-multilib-1.0-1.386 tools.
> 
>  
> 
> After some trial and error I managed to configure the mx53_ard_dd3.h for
> NAND and YAFFS2 support and successfully ran make, resulting in creation
> of the following files:
> 
> *         u-boot
> 
> *         u-boot.bin
> 
> *         u-boot.srec
> 
> *         u-boot.map
> 
> *         u-boot.lds
> 
>  
> 
> However, I would want to initially boot from SD-card and I would like to
> be able to generate an imx image of the u-boot when running make.  I
> looked at the Makefile from the Freescale release of u-boot-2009.08 and
> saw that it is fairly outdated - it does not support making of
> u-boot.imx image.  At the same time I see that the general denx
> distribution (u-boot-2011.12) of u-boot sources does have the support
> for making u-boot.imx image in its Makefile.  So I am wondering if a
> patch that can be applied to the u-boot-2009.08 Freescale u-boot source
> that will bring the make tools up to date and able to make u-boot.imx
> file does exist?

Using the Freescale 2009.08 U-Boot, you have everything you need with 
the generated u-boot.bin. Or in other words: The Freescale U-Boot 
u-boot.bin is from (SD) header point of view the same like the mainline 
u-boot.imx. Or in other words: The Freescale U-Boot uses the 
compiler/assembler to generate the header (see the file flash_header.S). 
The mainline U-Boot uses the mkimage/imximage tool *after* the 
u-boot.bin is generated to put the correct header in front of the 
u-boot.bin resulting in u-boot.imx. I.e. the Freescale U-Boot does 
everything in one step with the compiler/assembler, the mainline U-Boot 
does the same in two steps with an extra tool.

Best regards

Dirk

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2
  2012-03-06  3:13 [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2 Bud Miljkovic
  2012-03-06  6:42 ` Dirk Behme
@ 2012-03-06 12:53 ` Fabio Estevam
  1 sibling, 0 replies; 3+ messages in thread
From: Fabio Estevam @ 2012-03-06 12:53 UTC (permalink / raw)
  To: u-boot

On 3/6/12, Bud Miljkovic <Bud_Miljkovic@trimble.com> wrote:

> However, I would want to initially boot from SD-card and I would like to
> be able to generate an imx image of the u-boot when running make.

Booting from SD card was the only boot method I tested on mx53ard in
mainline U-boot.

All you need to do is:

make mx53ard_config
make u-boot.imx

Then flash u-boot.imx into the SD card as per instructions from
doc/README.imximage

Booting from NAND I haven't tested, but the procedure to generate
u-boot.imx is the same.

Please note that the boot from NAND relies on the mx53 ROM. If you
need to store environment variables in NAND, for example, then you
would need to add support for mx5 nand driver.

Regards,

Fabio Estevam

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-03-06 12:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-06  3:13 [U-Boot] Building imximage for mx53ard board, supporting NAND and YAFFS2 Bud Miljkovic
2012-03-06  6:42 ` Dirk Behme
2012-03-06 12:53 ` Fabio Estevam

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox