All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Is it possible to load the uboot.bin file to RAM area instead FLASH?
Date: Sun, 13 Feb 2011 15:37:57 +0100	[thread overview]
Message-ID: <4D57ECC5.7060300@free.fr> (raw)
In-Reply-To: <AANLkTikP361sE+7BK+evG87mAY0fLDgDAqemb==Yetsj@mail.gmail.com>

Le 13/02/2011 15:22, Madhavi Manchala a ?crit :
> On Sun, Feb 13, 2011 at 7:11 PM, Lei Wen<adrian.wenl@gmail.com>  wrote:
>> On Sun, Feb 13, 2011 at 9:30 PM, Madhavi Manchala
>> <madhavi.linux@gmail.com>  wrote:
>>> On Fri, Feb 11, 2011 at 10:27 PM, Wolfgang Denk<wd@denx.de>  wrote:
>>>> Dear Lei Wen,
>>>>
>>>> In message<AANLkTin7zsxVqjKp1Htovf44mtfkNsJR2DF9bSBkTBFR@mail.gmail.com>  you wrote:
>>>>>
>>>>> If your sdram is large enough, or the uboot code is small enough, you don't need
>>>>> the dram init. But begin at the TEXT_BASE still is a must.
>>>>
>>>> Hugh?  You _always_ must make sure the RAM has been initialized first.
>>>>
>>>> Best regards,
>>>>
>>>> Wolfgang Denk
>>>
>>> Dear Wolfgang Denk and Lei,
>>>
>>> Thanks for your information.
>>>
>>> I build one u-boot.bin file for smdk2410 configuration. However, when
>>> I try to load through JTAG, I am seeing the following error.
>>>
>>> invalid download offset u-boot.bin
>>>
>>> Am I doing any thing wrong? I set RAM BASE address as 0x00000000 in
>>> the confiuration file as our board RAM starts from there only. Shall I
>>> need to modify any thing in the config file?
>>>
>> No idea...
>> That info message should not be printed by your uboot.
>> Maybe you should refer to someone expert for your jtag to solve this...
>>
>> Best regads,
>> Lei
>
> Yes, Lei.
>
> I am using J-Link JTAG with J-LinkGDBServer for loading the u-boot.bin
> file on to the board through a .gdbinit script file. One more thing,
> when I looked into the config.h file, I found CONFIG_SYS_LOAD_ADDR
> macro. What is the use of this macro? Is it u-boot load address? I
> also changed this and tested. But, lo luck.

The message is from the loader, which does not care about #defines in 
the source code of the loaded binary.

Apparently, the error message means the loader took "u-boot.bin" to mean 
not a file but an address.

You should double-check your gdb script against the GDB syntax.

> Thanks for your information.
>
> Regards,
> Madhavi M.

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-02-13 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11 15:19 [U-Boot] Is it possible to load the uboot.bin file to RAM area instead FLASH? Madhavi Manchala
2011-02-11 15:29 ` Lei Wen
2011-02-11 16:57   ` Wolfgang Denk
2011-02-13 13:30     ` Madhavi Manchala
2011-02-13 13:41       ` Lei Wen
2011-02-13 14:22         ` Madhavi Manchala
2011-02-13 14:37           ` Albert ARIBAUD [this message]
2011-02-13 16:37           ` Srinath Iyengar
2011-02-14  7:04             ` Madhavi Manchala
2011-02-14  8:46               ` Wolfgang Denk
2011-02-14 10:43                 ` Madhavi Manchala
2011-02-14 13:53                   ` Wolfgang Denk

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=4D57ECC5.7060300@free.fr \
    --to=albert.aribaud@free.fr \
    --cc=u-boot@lists.denx.de \
    /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.