From: ansaris <ansaris@iwavesystems.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Booting u-boot from DDR Through JTAG Debugger
Date: Fri, 17 Oct 2014 21:39:32 +0530 [thread overview]
Message-ID: <54413F3C.7020506@iwavesystems.com> (raw)
In-Reply-To: <CAOMZO5Cvq76+eh5ZRDCZ8E4Qk8EJi9gViFmcD+mpqyxHrXzwDQ@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2014-10-17 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 15:25 Booting u-boot from DDR Through JTAG Debugger ansaris
2014-10-16 16:07 ` Otavio Salvador
2014-10-17 12:34 ` ansaris
2014-10-17 14:00 ` Daiane Angolini
2014-10-17 14:26 ` Fabio Estevam
2014-10-17 15:26 ` ansaris
2014-10-17 15:29 ` Fabio Estevam
2014-10-17 16:09 ` ansaris [this message]
2014-10-17 18:56 ` Fabio Estevam
2014-10-20 6:48 ` ansaris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54413F3C.7020506@iwavesystems.com \
--to=ansaris@iwavesystems.com \
--cc=festevam@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.