Booting u-boot from DDR Through JTAG Debugger

Booting u-boot from DDR Through JTAG Debugger

[ansaris]

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

Hi,

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.


Thank You,
Regards,
Ansari

[-- Attachment #2: Type: text/html, Size: 1320 bytes --]

Re: Booting u-boot from DDR Through JTAG Debugger

[Otavio Salvador]

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.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Booting u-boot from DDR Through JTAG Debugger

[ansaris]

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

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.

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.
>


[-- Attachment #2: Type: text/html, Size: 2144 bytes --]

Re: Booting u-boot from DDR Through JTAG Debugger

[Daiane Angolini]

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
>

Re: Booting u-boot from DDR Through JTAG Debugger

[Fabio Estevam]

On Fri, Oct 17, 2014 at 11:00 AM, Daiane Angolini <daiane.list@gmail.com> wrote:

> 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.

It's the opposite: with u-boot-fslc you should use u-boot.imx, the old
2009.08 produced a u-boot.bin.

Re: Booting u-boot from DDR Through JTAG Debugger

[ansaris]

[-- Attachment #1: Type: text/plain, Size: 3837 bytes --]

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
>>


[-- Attachment #2: Type: text/html, Size: 5216 bytes --]

Re: Booting u-boot from DDR Through JTAG Debugger

[Fabio Estevam]

On Fri, Oct 17, 2014 at 12:26 PM, ansaris <ansaris@iwavesystems.com> wrote:
> 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

Why are the load address different?

By the way, this is a bit off topic in this list.

Re: Booting u-boot from DDR Through JTAG Debugger

[ansaris]

[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]

Hi,

We came to know with System.map file, that the TEXT_BASE & start address 
are below respectively

u-boot-2008.09 (LTIB)
================
0x27800000, 0x27800bc0

u-boot-imx (Yocto)
============
0x17800000, 0x17800000

Please suggest us.


Thank You,
Regards,
Ansari

On Friday 17 October 2014 08:59 PM, Fabio Estevam wrote:
> On Fri, Oct 17, 2014 at 12:26 PM, ansaris <ansaris@iwavesystems.com> wrote:
>> 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
> Why are the load address different?
>
> By the way, this is a bit off topic in this list.
>


[-- Attachment #2: Type: text/html, Size: 2728 bytes --]

Re: Booting u-boot from DDR Through JTAG Debugger

[Fabio Estevam]

On Fri, Oct 17, 2014 at 1:09 PM, ansaris <ansaris@iwavesystems.com> wrote:
> Hi,
>
> We came to know with System.map file, that the TEXT_BASE & start address are
> below respectively
>
> u-boot-2008.09 (LTIB)
> ================
> 0x27800000, 0x27800bc0
>
> u-boot-imx (Yocto)
> ============
> 0x17800000, 0x17800000
>
> Please suggest us.

Instead of booting via JTAG: why don't you flash the u-boot binary
into some bootable media like SD/MMC/NOR/SPI?

Re: Booting u-boot from DDR Through JTAG Debugger

[ansaris]

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

Hi

We have SPI NOR flash and eMMC on board. But for first time programming 
we have to use either MFG tool or JTAG. In our custom board, USB OTG 
port is not available and so we could not use MFG tool and forced to use 
JTAG.

Thank You,
Regards,
Ansari



On Saturday 18 October 2014 12:26 AM, Fabio Estevam wrote:
> On Fri, Oct 17, 2014 at 1:09 PM, ansaris <ansaris@iwavesystems.com> wrote:
>> Hi,
>>
>> We came to know with System.map file, that the TEXT_BASE & start address are
>> below respectively
>>
>> u-boot-2008.09 (LTIB)
>> ================
>> 0x27800000, 0x27800bc0
>>
>> u-boot-imx (Yocto)
>> ============
>> 0x17800000, 0x17800000
>>
>> Please suggest us.
> Instead of booting via JTAG: why don't you flash the u-boot binary
> into some bootable media like SD/MMC/NOR/SPI?
>


[-- Attachment #2: Type: text/html, Size: 1583 bytes --]