From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Babic Date: Thu, 12 Apr 2012 13:11:57 +0200 Subject: [U-Boot] [PATCH 2/8] i.MX: Add target flashable to offset 0 In-Reply-To: <1334223234-23383-3-git-send-email-timo@exertus.fi> References: <1334223234-23383-1-git-send-email-timo@exertus.fi> <1334223234-23383-3-git-send-email-timo@exertus.fi> Message-ID: <4F86B87D.9000206@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12/04/2012 11:33, Timo Ketola wrote: > .imx image directly from mkimage must be flashed at offset 0x400 into the nand. Thats a little hard with e.g. openocd. > > Signed-off-by: Timo Ketola > --- Hi Timo, > Makefile | 3 +++ > 1 files changed, 3 insertions(+), 0 deletions(-) > > diff --git a/Makefile b/Makefile > index 1446131..b3f1279 100644 > --- a/Makefile > +++ b/Makefile > @@ -410,6 +410,9 @@ $(obj)u-boot.imx: $(obj)u-boot.bin > $(obj)tools/mkimage -n $(CONFIG_IMX_CONFIG) -T imximage \ > -e $(CONFIG_SYS_TEXT_BASE) -d $< $@ > > +$(obj)u-boot-nand.imx: $(obj)u-boot.imx > + dd if=$< of=$@ seek=2 > + I wonder why we need this in u-boot code and to set this rule in the main Makefile. You can always do this after generating u-boot. The rules here are to generate the u-boot.imx. Then the same image can be stored at different addresses. Depending on the i.MX SOC, ofssets can be different (MX5 / MX6 have different offsets for NOR / NAND / oneNAND). Best regards, Stefano Babic -- ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================