Hi Pali,
On 23/08/22 11:00, Pali Rohár wrote:
> On Wednesday 17 August 2022 08:17:36 Stefan Roese wrote:
>> On 10.08.22 14:46, Pali Rohár wrote:
>>> mbus driver is initialized from arch_cpu_init() callback which is called
>>> before relocation. This driver stores lot of functions and structure
On 10.08.22 14:46, Pali Rohár wrote:
mbus driver is initialized from arch_cpu_init() callback which is called
before relocation. This driver stores lot of functions and structure
pointers into global variables, so it is data position dependent.
Therefore after relocations all pointers are
Hi Pali,
On Mon, Aug 22, 2022 at 4:00 PM Pali Rohár wrote:
>
> On Wednesday 17 August 2022 08:17:36 Stefan Roese wrote:
> > On 10.08.22 14:46, Pali Rohár wrote:
> > > mbus driver is initialized from arch_cpu_init() callback which is called
> > > before relocation. This driver stores lot of
On Wednesday 17 August 2022 08:17:36 Stefan Roese wrote:
> On 10.08.22 14:46, Pali Rohár wrote:
> > mbus driver is initialized from arch_cpu_init() callback which is called
> > before relocation. This driver stores lot of functions and structure
> > pointers into global variables, so it is data
On 10.08.22 14:46, Pali Rohár wrote:
mbus driver is initialized from arch_cpu_init() callback which is called
before relocation. This driver stores lot of functions and structure
pointers into global variables, so it is data position dependent.
Therefore after relocations all pointers are
Hi Pali,
On 11/08/22 00:46, Pali Rohár wrote:
> mbus driver is initialized from arch_cpu_init() callback which is called
> before relocation. This driver stores lot of functions and structure
> pointers into global variables, so it is data position dependent.
>
> Therefore after relocations all
mbus driver is initialized from arch_cpu_init() callback which is called
before relocation. This driver stores lot of functions and structure
pointers into global variables, so it is data position dependent.
Therefore after relocations all pointers are invalid and driver does not
work anymore as
Hi Peng,
On Wed, 13 Oct 2021 at 03:18, Peng Fan (OSS) wrote:
>
> From: Peng Fan
>
> U-Boot binary is quite large with more options enabled, it not hurt
> on real silicon with high performance. But on simulation platform,
> it is quite slow to relocate the U-Boot binary to new address,
> so
From: Peng Fan
U-Boot binary is quite large with more options enabled, it not hurt
on real silicon with high performance. But on simulation platform,
it is quite slow to relocate the U-Boot binary to new address,
so let's support skipping relocation.
Users could use 'gd->flags |=
On Mon, 2020-09-07 at 22:24 +0300, Yusuf Altıparmak wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the
> content is safe.
>
>
> Hello,
>
> I want to modify U-boot to relocate itself to
Hello,
I want to modify U-boot to relocate itself to on-board SRAM of chip (T1042
demo board) instead of DRAM.
At first, there is call list in u-boot/common/board_f.c and it has a line
to call dram_init. I will change this line with my custom sram_init
function.
[image: Capture.PNG]
The
On Wed, Jul 15, 2020 at 10:49:05PM +0530, Rayagonda Kokatanur wrote:
> From: Bharat Kumar Reddy Gooty
>
> By default relocation happens to a higher address of DDR,
> i.e, DDR start + DDR size.
>
> U-Boot shall be used to collect the ramdump.
> Restrict U-Boot to use only the 16MB memory, so
From: Bharat Kumar Reddy Gooty
By default relocation happens to a higher address of DDR,
i.e, DDR start + DDR size.
U-Boot shall be used to collect the ramdump.
Restrict U-Boot to use only the 16MB memory, so that this
memory can be reserved. Limit relocation to happen within
16MB memory, start
From: Bharat Kumar Reddy Gooty
By default relocation happens to a higher address of DDR,
i.e, DDR start + DDR size.
U-Boot shall be used to collect the ramdump.
Restrict U-Boot to use only the 16MB memory, so that this
memory can be reserved. Limit relocation to happen within
16MB memory, start
On Mon, Jun 29, 2020 at 10:56 PM Simon Glass wrote:
>
> Hi Rayagonda,
>
> On Fri, 26 Jun 2020 at 04:21, Rayagonda Kokatanur
> wrote:
> >
> > On Fri, Jun 26, 2020 at 6:42 AM Simon Glass wrote:
> > >
> > > On Wed, 10 Jun 2020 at 04:42, Rayagonda Kokatanur
> > > wrote:
> > > >
> > > > From:
Hi Rayagonda,
On Fri, 26 Jun 2020 at 04:21, Rayagonda Kokatanur
wrote:
>
> On Fri, Jun 26, 2020 at 6:42 AM Simon Glass wrote:
> >
> > On Wed, 10 Jun 2020 at 04:42, Rayagonda Kokatanur
> > wrote:
> > >
> > > From: Bharat Kumar Reddy Gooty
> > >
> > > By default re-location happens to higher
On Fri, Jun 26, 2020 at 6:42 AM Simon Glass wrote:
>
> On Wed, 10 Jun 2020 at 04:42, Rayagonda Kokatanur
> wrote:
> >
> > From: Bharat Kumar Reddy Gooty
> >
> > By default re-location happens to higher address of DDR,
>
> relocation happens to a higher address
Thank you, will fix it.
>
> >
On Wed, 10 Jun 2020 at 04:42, Rayagonda Kokatanur
wrote:
>
> From: Bharat Kumar Reddy Gooty
>
> By default re-location happens to higher address of DDR,
relocation happens to a higher address
> i.e, DDR start + DDR size.
>
> Limit re-location to happen within 16MB memory,
> start 0xFF00_
From: Bharat Kumar Reddy Gooty
By default re-location happens to higher address of DDR,
i.e, DDR start + DDR size.
Limit re-location to happen within 16MB memory,
start 0xFF00_ and end 0x1__
Signed-off-by: Bharat Kumar Reddy Gooty
Signed-off-by: Rayagonda Kokatanur
---
From: Bharat Kumar Reddy Gooty
By default re-location happens to higher address of DDR,
i.e, DDR start + DDR size.
Limit re-location to happen within 16MB memory,
start 0xFF00_ and end 0x1__
Signed-off-by: Bharat Kumar Reddy Gooty
Signed-off-by: Rayagonda Kokatanur
---
From: Bharat Kumar Reddy Gooty
By default re-location happens to higher address of DDR,
i.e, DDR start + DDR size.
Limit re-location to happen within 16MB memory,
start 0xFF00_ and end 0x1__
Signed-off-by: Bharat Kumar Reddy Gooty
Signed-off-by: Rayagonda Kokatanur
---
all I can about u-boot.
--
View this message in context:
http://u-boot.10912.n7.nabble.com/U-Boot-Relocation-Address-and-GPIO-Bank-Access-tp270310.html
Sent from the U-Boot mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot
On Wed, Oct 21, 2015 at 08:44:15AM +, Joakim Tjernlund wrote:
> On Tue, 2015-10-20 at 17:21 -0400, Tom Rini wrote:
> > On Tue, Oct 20, 2015 at 04:06:51PM -0500, Andy Fleming wrote:
> > > On Fri, Oct 16, 2015 at 8:14 AM, Joakim Tjernlund
> > > wrote:
> > > > On
On Wed, 2015-10-21 at 09:12 -0400, Tom Rini wrote:
> On Wed, Oct 21, 2015 at 08:44:15AM +, Joakim Tjernlund wrote:
> > On Tue, 2015-10-20 at 17:21 -0400, Tom Rini wrote:
> > > On Tue, Oct 20, 2015 at 04:06:51PM -0500, Andy Fleming wrote:
> > > > On Fri, Oct 16, 2015 at 8:14 AM, Joakim
On Tue, 2015-10-20 at 17:21 -0400, Tom Rini wrote:
> On Tue, Oct 20, 2015 at 04:06:51PM -0500, Andy Fleming wrote:
> > On Fri, Oct 16, 2015 at 8:14 AM, Joakim Tjernlund
> > wrote:
> > > On Fri, 2015-10-16 at 07:47 -0400, Tom Rini wrote:
> > > > On Fri, Oct 16, 2015
On Tue, Oct 20, 2015 at 04:06:51PM -0500, Andy Fleming wrote:
> On Fri, Oct 16, 2015 at 8:14 AM, Joakim Tjernlund
> wrote:
> > On Fri, 2015-10-16 at 07:47 -0400, Tom Rini wrote:
> >> On Fri, Oct 16, 2015 at 06:55:58AM +, Joakim Tjernlund wrote:
> >> > On Thu,
On Fri, Oct 16, 2015 at 8:14 AM, Joakim Tjernlund
wrote:
> On Fri, 2015-10-16 at 07:47 -0400, Tom Rini wrote:
>> On Fri, Oct 16, 2015 at 06:55:58AM +, Joakim Tjernlund wrote:
>> > On Thu, 2015-10-15 at 17:58 -0400, Tom Rini wrote:
>> > > On Thu, Oct 15, 2015 at
On Thu, 2015-10-15 at 17:58 -0400, Tom Rini wrote:
> On Thu, Oct 15, 2015 at 03:56:09PM +, Joakim Tjernlund wrote:
> > On Tue, 2015-10-06 at 11:17 +, Joakim Tjernlund wrote:
> > > On Thu, 2015-10-01 at 08:57 +, Joakim Tjernlund wrote:
> > > > On Wed, 2015-09-30 at 21:35 +0200, Marek
On Fri, Oct 16, 2015 at 06:55:58AM +, Joakim Tjernlund wrote:
> On Thu, 2015-10-15 at 17:58 -0400, Tom Rini wrote:
> > On Thu, Oct 15, 2015 at 03:56:09PM +, Joakim Tjernlund wrote:
> > > On Tue, 2015-10-06 at 11:17 +, Joakim Tjernlund wrote:
> > > > On Thu, 2015-10-01 at 08:57 +,
On Fri, 2015-10-16 at 07:47 -0400, Tom Rini wrote:
> On Fri, Oct 16, 2015 at 06:55:58AM +, Joakim Tjernlund wrote:
> > On Thu, 2015-10-15 at 17:58 -0400, Tom Rini wrote:
> > > On Thu, Oct 15, 2015 at 03:56:09PM +, Joakim Tjernlund wrote:
> > > > On Tue, 2015-10-06 at 11:17 +, Joakim
On Tue, 2015-10-06 at 11:17 +, Joakim Tjernlund wrote:
> On Thu, 2015-10-01 at 08:57 +, Joakim Tjernlund wrote:
> > On Wed, 2015-09-30 at 21:35 +0200, Marek Vasut wrote:
> > > On Wednesday, September 30, 2015 at 08:24:10 PM, Andy Fleming wrote:
> > >
> > > Hi!
> > >
> > > > On Thu, Oct
On Thu, Oct 15, 2015 at 03:56:09PM +, Joakim Tjernlund wrote:
> On Tue, 2015-10-06 at 11:17 +, Joakim Tjernlund wrote:
> > On Thu, 2015-10-01 at 08:57 +, Joakim Tjernlund wrote:
> > > On Wed, 2015-09-30 at 21:35 +0200, Marek Vasut wrote:
> > > > On Wednesday, September 30, 2015 at
On Thu, 2015-10-01 at 08:57 +, Joakim Tjernlund wrote:
> On Wed, 2015-09-30 at 21:35 +0200, Marek Vasut wrote:
> > On Wednesday, September 30, 2015 at 08:24:10 PM, Andy Fleming wrote:
> >
> > Hi!
> >
> > > On Thu, Oct 23, 2014 at 8:10 AM, Wolfgang Denk wrote:
> > > > Dear
Dear Andy,
In message
you wrote:
>
> At the very least, I would want the fix in
> arch/powerpc/cpu/mpc85xx/u-boot.lds. :)
Well, I observed the problems on MPC5200 ...
Best regards,
Wolfgang Denk
--
DENX Software
On Thu, Oct 1, 2015 at 9:18 AM, Wolfgang Denk wrote:
> Dear Andy,
>
> In message
>
Dear Andy,
In message
On Wed, 2015-09-30 at 21:35 +0200, Marek Vasut wrote:
> On Wednesday, September 30, 2015 at 08:24:10 PM, Andy Fleming wrote:
>
> Hi!
>
> > On Thu, Oct 23, 2014 at 8:10 AM, Wolfgang Denk wrote:
> > > Dear Joakim, dear Dirk,
> > >
> > > In message c1257d7a.0024d...@transmode.se>
On Thu, Oct 23, 2014 at 8:10 AM, Wolfgang Denk wrote:
> Dear Joakim, dear Dirk,
>
> In message
> you
> wrote:
>>
>> Ouch, that was a nasty surprise.
>
> Indeed.
>
>> > In my original mail I referenced this
On Wednesday, September 30, 2015 at 08:24:10 PM, Andy Fleming wrote:
Hi!
> On Thu, Oct 23, 2014 at 8:10 AM, Wolfgang Denk wrote:
> > Dear Joakim, dear Dirk,
> >
> > In message you wrote:
> >> Ouch, that was a nasty surprise.
> >
> > Indeed.
> >
> >> > In my original mail I
Hi All,
I am porting the u-boot for a customized board based on MPC885 processor.
Initially we used u-boot v2010 for this board and it's works fine so i only
porting our board patch to u-boot 2013 but the relocation seems hang
nothing is dipslayed after debug print New stack pointer is
Hi Stefano,
On Thu, Feb 5, 2015 at 1:24 PM, Priebe, Sebastian
sebastian.pri...@cadcon.de wrote:
Hello,
I'm using a custom board with iMX35 CPU (ARM1136).
After I updated to version 2015.01 the relocation doesn't work anymore.
I turned on CONFIG_DEBUG and the last output I saw was:
Hi Fabio,
On Wed, 11 Feb 2015 11:55:04 -0200
Fabio Estevam feste...@gmail.com wrote:
...
I don't have a mx35pdk handy to look into this, but it would be nice
to get mx35 back to life in U-boot.
Magnus,
I suspect that mx31 is also broken. Could you please test mx31pdk with
U-boot 2015.01?
Hi Fabio,
On 11/02/2015 14:55, Fabio Estevam wrote:
Hi Stefano,
On Thu, Feb 5, 2015 at 1:24 PM, Priebe, Sebastian
sebastian.pri...@cadcon.de wrote:
Hello,
I'm using a custom board with iMX35 CPU (ARM1136).
After I updated to version 2015.01 the relocation doesn't work anymore.
I turned
Hello Albert,
thanks for your answer.
I tried to look up some information in the iMX35 reference manual but couldn't
find anything. It doesn't say anything about the exception vectors. Can you
point me at any direction where to look for information?
What is the consequence of skipping the
Hello Sebastian,
Cc:ing Stefano since he's the i.MX custodian.
On Fri, 6 Feb 2015 09:38:17 +, Priebe, Sebastian
sebastian.pri...@cadcon.de wrote:
Hello Albert,
thanks for your answer.
I tried to look up some information in the iMX35 reference manual but
couldn't find anything. It
Hello,
I'm using a custom board with iMX35 CPU (ARM1136).
After I updated to version 2015.01 the relocation doesn't work anymore.
I turned on CONFIG_DEBUG and the last output I saw was:
Relocating to 83f89000, new gd at 83e84ec8, sp at 83e84ea0
I recognized the new function relocate_vectors.
Hello Sebastian,
On Thu, 5 Feb 2015 15:24:40 +, Priebe, Sebastian
sebastian.pri...@cadcon.de wrote:
Hello,
I'm using a custom board with iMX35 CPU (ARM1136).
After I updated to version 2015.01 the relocation doesn't work anymore.
I turned on CONFIG_DEBUG and the last output I saw was:
On 23 Oct 2014, w...@denx.de wrote:
Given that GCC 4.9.1 apparently solves this issue I wonder which
approach we should take?
Should we blacklist GCC 4.8.x (and 4.9.0) like the kernel folks are
doing [1] ?
[1] https://lkml.org/lkml/2014/10/10/272
My understanding is this is for a
Hello Wolfgang,
2014-10-22 18:56 GMT+02:00 Wolfgang Denk w...@denx.de:
Dear Dirk,
In message
CANVMifLGzKz+=-k-e9_ssxbxpypdg1yqexc-tscapi7wvxq...@mail.gmail.com you
wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but
Hello Wolfgang,
2014-10-22 18:56 GMT+02:00 Wolfgang Denk w...@denx.de:
Dear Dirk,
In message
CANVMifLGzKz+=-k-e9_ssxbxpypdg1yqexc-tscapi7wvxq...@mail.gmail.com you
wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing
Dear Joakim, dear Dirk,
In message
of14c3d470.864842b6-onc1257d7a.002471ac-c1257d7a.0024d...@transmode.se you
wrote:
Ouch, that was a nasty surprise.
Indeed.
In my original mail I referenced this potential solution, at least it
worked for me:
Hello Wolfgang,
2014-10-23 15:10 GMT+02:00 Wolfgang Denk w...@denx.de:
Given that GCC 4.9.1 apparently solves this issue I wonder which
approach we should take?
Should we blacklist GCC 4.8.x (and 4.9.0) like the kernel folks are
doing [1] ?
[1] https://lkml.org/lkml/2014/10/10/272
Hi,
I'm trying to track down a syntax error issue that gets triggered
when erasing the U-Boot image in NOR flash. Symptoms look like this:
= print update
update=protect off 0xfc00 +${filesize};erase 0xfc00
+${filesize};cp.b 20 0xfc00 ${filesize};protect on
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but sadly got no feedback):
In my latest u-boot builds I had some strange behaviour that I finally
tracked down to not fixed up flash addresses in relocated u-boot.
These addresses come
Dear Dirk,
In message CANVMifLGzKz+=-k-e9_ssxbxpypdg1yqexc-tscapi7wvxq...@mail.gmail.com
you wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but sadly got no feedback):
Thanks a lot for this pointer.
So there a three
On Wed, Oct 22, 2014 at 2:56 PM, Wolfgang Denk w...@denx.de wrote:
So there a three things to notice:
1. Do not use gcc 4.8 and u-boot at the moment.
2. You might not notice that you have a problem until you erase u-boot
from flash (and get your cache flushed).
3. Handling relro properly
On Wed, Oct 22, 2014 at 06:56:11PM +0200, Wolfgang Denk wrote:
Dear Dirk,
In message
CANVMifLGzKz+=-k-e9_ssxbxpypdg1yqexc-tscapi7wvxq...@mail.gmail.com you
wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but sadly
Dear Tom,
In message 20141022172811.GD25506@bill-the-cat you wrote:
Is this ARM or PowerPC? The kernel has blacklisted 4.8.x for ARM in
some cases, and this may or may not be related (see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D58854)
This is on PowerPC (MPC5200, i. e. the TQM5200S
Hi!
In message
CANVMifLGzKz+=-k-e9_ssxbxpypdg1yqexc-tscapi7wvxq...@mail.gmail.com you
wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but sadly got no feedback):
Thanks a lot for this pointer.
So there
On Wednesday, October 22, 2014 at 11:27:42 PM, Pavel Machek wrote:
Hi!
In message CANVMifLGzKz+=-K-E9_sSXBxpYPdG1YqEXc-
tscapi7wvxq...@mail.gmail.com you wrote:
I had exactly the same behaviour some time ago and tracked it down to
this (and posted it on the mailing list, but
On Wed 2014-10-22 23:46:45, Marek Vasut wrote:
On Wednesday, October 22, 2014 at 11:27:42 PM, Pavel Machek wrote:
Hi!
In message CANVMifLGzKz+=-K-E9_sSXBxpYPdG1YqEXc-
tscapi7wvxq...@mail.gmail.com you wrote:
I had exactly the same behaviour some time ago and tracked it down to
On Wednesday, October 22, 2014 at 11:57:39 PM, Pavel Machek wrote:
On Wed 2014-10-22 23:46:45, Marek Vasut wrote:
On Wednesday, October 22, 2014 at 11:27:42 PM, Pavel Machek wrote:
Hi!
In message CANVMifLGzKz+=-K-E9_sSXBxpYPdG1YqEXc-
tscapi7wvxq...@mail.gmail.com you wrote:
Dear Chris,
In message CAFOYHZCtPSJRvL8asB9O6dUPtNHZSE_gUd=n8+6hyqsnyhd...@mail.gmail.com
you wrote:
Do you mean the address or the value? FYI the 77fb addresses are
what I believe to be the correct relocated address. It's the f0d0
address for NetArpWaitTimerStart that I believe is
Chris Packham judge.pack...@gmail.com wrote on 2014/09/09 01:07:51:
From: Chris Packham judge.pack...@gmail.com
To: Joakim Tjernlund joakim.tjernl...@transmode.se,
Cc: u-boot u-boot@lists.denx.de
Date: 2014/09/09 01:08
Subject: Re: [U-Boot] relocation problem on powerpc
Hi Jocke
Here's some more info from a build without any of my modifications.
$ git describe
v2014.10-rc2-12-g0b703db
$ powerpc-e500-linux-gnu-gcc --version
powerpc-e500-linux-gnu-gcc (Gentoo 4.6.3-r1 p1.9, pie-0.5.2) 4.6.3
$ grep
Joakim Tjernlund/Transmode wrote on 2014/09/09 14:30:13:
From: Joakim Tjernlund/Transmode
To:
Cc: Chris Packham judge.pack...@gmail.com, u-boot
u-boot@lists.denx.de
Date: 2014/09/09 14:30
Subject: Re: [U-Boot] relocation problem on powerpc
Here's some more info from a build without
Subject: Re: [U-Boot] relocation problem on powerpc
Here's some more info from a build without any of my modifications.
$ git describe
v2014.10-rc2-12-g0b703db
$ powerpc-e500-linux-gnu-gcc --version
powerpc-e500-linux-gnu-gcc (Gentoo 4.6.3-r1 p1.9, pie-0.5.2) 4.6.3
There are some disadvantages to living in a weird timezone, mostly
that you end up having conversations with yourself.
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham judge.pack...@gmail.com
wrote:
Hi All,
I have come across what I think is a relocation problem for powerpc.
I've
There are some disadvantages to living in a weird timezone, mostly
that you end up having conversations with yourself.
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham
judge.pack...@gmail.com
wrote:
Hi All,
I have come across what I think is a relocation problem for powerpc.
Dear Chris,
In message CAFOYHZASBbTctq4fRJNX2e8=r_ocwosodnq5r80wga1gfzg...@mail.gmail.com
you wrote:
...
Which yields the following output
NetArpWaitTimerStart = 0
NetArpWaitTimerStart = f0d0
NetArpWaitTry = 1
NetArpWaitTry = 7ffb0058
NetArpWaitTxPacketSize = 42
On Mon, Sep 8, 2014 at 9:04 PM, Joakim Tjernlund
joakim.tjernl...@transmode.se wrote:
There are some disadvantages to living in a weird timezone, mostly
that you end up having conversations with yourself.
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham judge.pack...@gmail.com
wrote:
Hi All,
Hi Wolfgang,
On Tue, Sep 9, 2014 at 8:21 AM, Wolfgang Denk w...@denx.de wrote:
Dear Chris,
In message
CAFOYHZASBbTctq4fRJNX2e8=r_ocwosodnq5r80wga1gfzg...@mail.gmail.com you
wrote:
...
Which yields the following output
NetArpWaitTimerStart = 0
NetArpWaitTimerStart = f0d0
Hi Jocke,
On Tue, Sep 9, 2014 at 12:22 AM, Joakim Tjernlund
joakim.tjernl...@transmode.se wrote:
There are some disadvantages to living in a weird timezone, mostly
that you end up having conversations with yourself.
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham
judge.pack...@gmail.com
Hi All,
I have come across what I think is a relocation problem for powerpc.
I've added the following to ArpTimeoutCheck
+ printf(NetArpWaitTimerStart = %ld\n, NetArpWaitTimerStart);
+ printf(NetArpWaitTimerStart = %p\n, NetArpWaitTimerStart);
+ printf(NetArpWaitTry = %d\n,
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham judge.pack...@gmail.com wrote:
Hi All,
I have come across what I think is a relocation problem for powerpc.
I've added the following to ArpTimeoutCheck
+ printf(NetArpWaitTimerStart = %ld\n, NetArpWaitTimerStart);
+
There are some disadvantages to living in a weird timezone, mostly
that you end up having conversations with yourself.
On Mon, Sep 8, 2014 at 4:32 PM, Chris Packham judge.pack...@gmail.com wrote:
Hi All,
I have come across what I think is a relocation problem for powerpc.
I've added the
Dear tiger...@via-alliance.com,
In message fe7aded5c2218b4786c09cd97dc4c49fe20...@exchbj02.viatech.com.bj you
wrote:
Relocation will always happen, and there is no provision for avoiding
it.
...
Then no relocation, it seemed OK.
You used the correct phrase: it seemed. Except that you broke
Hi, Denk:
You used the correct phrase: it seemed. Except that you broke a
number of really important things. If you do not understand what
rlocation is needed for, then please gop back and read it in the
archives. This has been discussed many times before.
For example:
Most ARM SOC platform
Dear tiger...@via-alliance.com,
In message fe7aded5c2218b4786c09cd97dc4c49fe20...@exchbj02.viatech.com.bj you
wrote:
You used the correct phrase: it seemed. Except that you broke a
number of really important things. If you do not understand what
rlocation is needed for, then please gop
Hi, Albert:
Relocation will always happen, and there is no provision for avoiding
it.
I have ever tried to del these code in crt0.S :
ldr sp, [r8, #GD_START_ADDR_SP] /* r8 =
gd-start_addr_sp */
bic sp, sp, #7 /* 8-byte alignment for ABI compliance
*/
ldr
Hi,
Can anyone please explain how relocation address is calculated in uboot ?
Also, I want to know whether relocation will happen or not when uboot is
running from RAM already? If yes, then can it be disabled ?
Thank you,
--
View this message in context:
Hi mahsmak,
On Fri, 14 Mar 2014 06:38:34 -0700 (PDT), mahsmak
kshamim...@gmail.com wrote:
Hi,
Can anyone please explain how relocation address is calculated in uboot ?
U-Boot tries to relocate itself as high in RAM as possible so that the
lower area is available to e.g. the Linux kernel it
Dear JagannadhaSutradharudu Teki,
In message loom.20120629t174245-...@post.gmane.org you wrote:
Does anyone having any idea about this issue. [u-boot
XIP is not working because of this relocation issue]
I have still debugging able to find some solution but needs
some to clarify.
Please read
Hi Albert,
I have observed an issue regarding u-boot relocation, it's working with
_TEXT_BASE address but
for other address in DDR it's not working. Stops at relocation offset.
I was trying this on both QEMU as well as real target.
Here are my findings:
-
VExpress
On Tue, Jun 19, 2012 at 09:06:48PM +0530, jagan wrote:
Hi Albert,
I have observed an issue regarding u-boot relocation, it's working with
_TEXT_BASE address but
for other address in DDR it's not working. Stops at relocation offset.
I was trying this on both QEMU as well as real target
Hi Jagan,
On 06/19/2012 08:36 AM, jagan wrote:
Hi Albert,
I have observed an issue regarding u-boot relocation, it's working with
_TEXT_BASE address but
for other address in DDR it's not working. Stops at relocation offset.
This is not quite clear to me. What's working and what's not working
HI,
One quick question,
I have a partition on emmc which has a logo.bmp.
I need to copy it to the ram in u-boot and pass that
address to frame buffer.
How should i go about the copying.
Thanks,
--
Cheers!!
Allen
Note: please add me in cc as am not subscribed to the list.
Dear Allen Pais,
In message caomdws+gf7sk4sbhyxnpptpkhhxsua3nzjg+rnlz2p39cg9...@mail.gmail.com
you wrote:
I have a partition on emmc which has a logo.bmp.
I need to copy it to the ram in u-boot and pass that
address to frame buffer.
How should i go about the copying.
Use mmc
Dear Reinhard,
finally I found the relocation problem.
Make sure that at91bootstrap loads the full u-boot image (u-boot
became larger quite a bit due to relocation and other changes).
That was the solution!
I left the old at91bootstrap from in-circuit on the board. This one only
copies 256k
Dear Marcel, Dear Reinhard,
I have the same problem with my board and the actual u-boot-atmel (git
from 5th Aug. 2011). It even looks like I am using the same board.
It is a in-circuit ICnova SAM9G45 OEM on a ADB1000 with a 5 display.
Actually I use the u-boot from in-circuit, which is a patched
Dear Marcel, Dear Reinhard,
sorry I forgot to mention, that this is in reply to
http://lists.denx.de/pipermail/u-boot/2011-January/084499.html
I have the same problem with my board and the actual u-boot-atmel (git
from 5th Aug. 2011). It even looks like I am using the same board.
It is a
Dear Cajus Hahn,
Dear Marcel, Dear Reinhard,
I have the same problem with my board and the actual u-boot-atmel (git
from 5th Aug. 2011). It even looks like I am using the same board.
It is a in-circuit ICnova SAM9G45 OEM on a ADB1000 with a 5 display.
Actually I use the u-boot from
Dear Cajus Hahn,
Dear Marcel, Dear Reinhard,
sorry I forgot to mention, that this is in reply to
http://lists.denx.de/pipermail/u-boot/2011-January/084499.html
I suppose you have not followed the steps I pointed out then?
I have the same problem with my board and the actual u-boot-atmel
Hi Reinhard,
Dear Cajus Hahn,
Dear Marcel, Dear Reinhard,
sorry I forgot to mention, that this is in reply to
http://lists.denx.de/pipermail/u-boot/2011-January/084499.html
I suppose you have not followed the steps I pointed out then?
I have the same problem with my board and the
Hi,
(Is there documentation about this somewhere? - I couldn't find it). I
assume your board is hanging during relocation.
You could try putting this function back (but without the __ prefix)
void dram_init_banksize(void)
{
gd-bd-bi_dram[0].start = CONFIG_SYS_SDRAM_BASE;
Le 26/12/2010 22:09, Marcel a écrit :
relocation Offset is: 0409e000
How is 0409e000 near top of my RAM ?
How does it get this value ?
This is an offset, a difference of addresses, not an absolute address.
And since it is rather big, it means the original and relocated
locations are far
Dear Marcel,
Hi,
I updated my u-boot-usb to continue my work on the SAM9 USB parts, but got
stuck with the following issue :
There seems to be a new relocation scheme. I also added some stuff to make it
detect the SDRAM, but than I get stuck.
int dram_init(void)
{
Dear Marcel,
On Sunday, December 26, 2010 02:38:04 pm Reinhard Meyer wrote:
Dear Marcel,
Hi,
I updated my u-boot-usb to continue my work on the SAM9 USB parts, but
got stuck with the following issue :
There seems to be a new relocation scheme. I also added some stuff to
make it detect
Hello,
1) If a code section (from an abolutely linked executable) is linked
at address x but is instead loaded at address y would it still
execute fine? Considereding the absolute branching, gloab variable
access etc.
2) If not, then how does u-boot work after relocation? All the uboot
code
Le 22/09/2010 19:10, Rajat Jain a écrit :
Hello,
1) If a code section (from an abolutely linked executable) is linked
at address x but is instead loaded at address y would it still
execute fine? Considereding the absolute branching, gloab variable
access etc.
This question has no definite
1 - 100 of 154 matches
Mail list logo