[meta-freescale] Booting u-boot from DDR Through JTAG Debugger

[Fabio Estevam]

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