From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id B579CE0080C; Fri, 17 Oct 2014 08:26:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message Received: from sip2-98.nexcess.net (iwavesystems.com [207.32.180.10]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 32F95E007B9 for ; Fri, 17 Oct 2014 08:26:19 -0700 (PDT) Received: (qmail 5564 invoked by uid 108); 17 Oct 2014 11:26:18 -0400 Received: from unknown (HELO ?192.168.2.104?) (115.119.206.100) by sip2-98.nexcess.net with SMTP; 17 Oct 2014 11:26:18 -0400 Message-ID: <54413510.1080605@iwavesystems.com> Date: Fri, 17 Oct 2014 20:56:08 +0530 From: ansaris User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Daiane Angolini References: <543FE36A.7050200@iwavesystems.com> <54410CD8.700@iwavesystems.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" , Otavio Salvador Subject: Re: Booting u-boot from DDR Through JTAG Debugger X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2014 15:26:26 -0000 Content-Type: multipart/alternative; boundary="------------050705000904000709000207" --------------050705000904000709000207 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, Sorry for in-convenience. Please find the details below. We are using our imx6 custom board for our development with solo (512MB of RAM) processor. In our custom board there is no USB OTG port. For programming, we are using JTAG debugger. Initially we have used “L3.0.35_4.1.0_130816” (LTIB) release BSP. We have downloaded the u-boot-2008.09 from the LTIB. With our customization in the source code we have generated u-boot.bin and uboot (elf) binary. Using JTAG we have downloaded the u-boot.bin binary or uboot (elf) into the target's RAM and executed. In this case we are able to boot the target and the bootloader console came in the debug port. 1) memory load tftp://192.168.0.1/u-boot.bin bin 0x27800000 2)set cpsr 0xD3 3) set sp 0x200 4)set pc 0x27800bc0 5)go Currently we are using L3.10.17_1.0.0-GA (Yocto dora) release BSP. We have downloaded the u-boot-imx (u-boot.2013.14) from the Yocto. With our customization in the source code we have generated u-boot.imx, u-boot.bin binaries. Using JTAG we have downloaded the u-boot.imx binary into the target's RAM and executed. In this case we are not able to boot the target. We have downloaded the u-boot.bin instead of u-boot.imx but the result is same. 1) memory load tftp://192.168.0.1/u-boot.imx bin 0x17800000 2)set cpsr 0xD3 3) set sp 0x200 4)set pc 0x17800000 5)go Please suggest us. Thank You, Regards, Ansari On Friday 17 October 2014 07:30 PM, Daiane Angolini wrote: > On Fri, Oct 17, 2014 at 9:34 AM, ansaris wrote: >> Hi, >> >> Thanks for your input on our issue. >> >> The problem is, in our custom board there is no USB OTG port. For >> programming, we are using JTAG debugger. >> With Linux-3.0.35 based BSP we are able to program/boot the target. But >> imx-3.10.17 GA based BSP we are not able to boot/program the target. > For me, it's very difficult to really know *which* are the u-boot > you're refering when you say Linux-3.0.35 based BSP or imx-3.10.17 GA > based BSP. So, please, make sure you're using the right padding value > for u-boot.bin versus u-boot.imx, and the right loadaddress for your > imx6 chip. > > In case you're using 3.0.35 BSP/LTIB you're using u-boot-imx, and this > produces a u-boot.imx binary with different padding. In this case, > which version? > In case you're using 3.0.35 BSP/YOCTO as-is you're using u-boot-fslc, > and it produces a u-boot.bin which should not differs. > > > Daiane >> Thank You, >> Regards, >> Ansari >> >> >> On Thursday 16 October 2014 09:37 PM, Otavio Salvador wrote: >> >> On Thu, Oct 16, 2014 at 12:25 PM, ansaris wrote: >> >> We are using linux-3.10.17 BSP(u-boot-3.10 YOCTO) with solo(512MB) processor >> custom imx6 board. >> >> I have downloaded the u-boot.imx(or u-boot.bin) into DDR using JTAG debugger >> to the memory address 0x17800000. >> I have followed the below mentioned steps: >> 1) memory load tftp://192.168.0.1/u-boot.imx bin 0x17800000 >> 2)set cpsr 0xD3 >> 3) set sp 0x200 >> 4)set pc 0x17800000 >> 5)go >> >> But target board is not booting. >> >> We tried the same with linux-3.0 BSP by following steps: >> 1) memory load tftp://192.168.0.1/u-boot.imx bin 0x27800000 >> 2)set cpsr 0xD3 >> 3) set sp 0x200 >> 4)set pc 0x27800bc0 >> 5)go >> >> After this, the target board is booting properly. >> >> Whether any changes required to load and boot 3.10 version u-boot? >> Please suggest us. >> >> Why you don't use USB loader for this? We used it daily and it works very >> well. >> >> >> >> -- >> _______________________________________________ >> meta-freescale mailing list >> meta-freescale@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/meta-freescale >> --------------050705000904000709000207 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

Sorry for in-convenience.  Please find the details below.

We are using our imx6 custom board  for our development with solo (512MB of RAM) processor.
In our custom board there is no USB OTG port.  For programming, we are using JTAG debugger.

Initially we have used “L3.0.35_4.1.0_130816” (LTIB) release BSP.  We have downloaded the u-boot-2008.09 from the LTIB.
With our customization in the source code we have generated u-boot.bin and uboot (elf) binary.
Using JTAG we have downloaded the u-boot.bin binary or uboot (elf) into the target's RAM and executed.
In this case we are able to boot the target and the bootloader console came in the debug port.
1) memory load tftp://192.168.0.1/u-boot.bin bin 0x27800000
2)set cpsr 0xD3
3) set sp 0x200
4)set pc 0x27800bc0
5)go


Currently we are using L3.10.17_1.0.0-GA (Yocto dora) release BSP.  We have downloaded the u-boot-imx (u-boot.2013.14) from the Yocto.
With our customization in the source code we have generated u-boot.imx, u-boot.bin binaries.
Using JTAG we have downloaded the u-boot.imx binary into the target's RAM and executed.
In this case we are not able to boot the target.
We have downloaded the u-boot.bin instead of u-boot.imx but the result is same.
1) memory load tftp://192.168.0.1/u-boot.imx bin 0x17800000
2)set cpsr 0xD3
3) set sp 0x200
4)set pc 0x17800000
5)go


Please suggest us.


Thank You,
Regards,
Ansari



On Friday 17 October 2014 07:30 PM, Daiane Angolini wrote:
On Fri, Oct 17, 2014 at 9:34 AM, ansaris <ansaris@iwavesystems.com> wrote:

Hi,

Thanks for your input on our issue.

The problem is, in our custom board there is no USB OTG port.  For
programming, we are using JTAG debugger.
With Linux-3.0.35 based BSP we are able to program/boot the target.  But
imx-3.10.17 GA based BSP we are not able to boot/program the target.

For me, it's very difficult to really know *which* are the u-boot
you're refering when you say Linux-3.0.35 based BSP or imx-3.10.17 GA
based BSP. So, please, make sure you're using the right padding value
for u-boot.bin versus u-boot.imx, and the right loadaddress for your
imx6 chip.

In case you're using 3.0.35 BSP/LTIB you're using u-boot-imx, and this
produces a u-boot.imx binary with different padding. In this case,
which version?
In case you're using 3.0.35 BSP/YOCTO as-is you're using u-boot-fslc,
and it produces a u-boot.bin which should not differs.


Daiane

Thank You,
Regards,
Ansari


On Thursday 16 October 2014 09:37 PM, Otavio Salvador wrote:

On Thu, Oct 16, 2014 at 12:25 PM, ansaris <ansaris@iwavesystems.com> wrote:

We are using linux-3.10.17 BSP(u-boot-3.10 YOCTO) with solo(512MB) processor
custom imx6 board.

I have downloaded the u-boot.imx(or u-boot.bin) into DDR using JTAG debugger
to the memory address 0x17800000.
I have followed the below mentioned steps:
1) memory load tftp://192.168.0.1/u-boot.imx bin 0x17800000
2)set cpsr 0xD3
3) set sp 0x200
4)set pc 0x17800000
5)go

But target board is not booting.

We tried the same with linux-3.0 BSP by following steps:
1) memory load tftp://192.168.0.1/u-boot.imx bin 0x27800000
2)set cpsr 0xD3
3) set sp 0x200
4)set pc 0x27800bc0
5)go

After this, the target board is booting properly.

Whether any changes required to load and boot 3.10 version u-boot?
Please suggest us.

Why you don't use USB loader for this? We used it daily and it works very
well.



--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale



    

    

  


--------------050705000904000709000207--