Dear Henrik Nordström,
In message <1354059376.5475.6.ca...@home.hno.se> you wrote:
>
> > How am I going to script gdb to figure out the relocation address when
> > I'm just running it on the image to get symbols, not actually
> > connecting to the target?
>
> It can be calculated from ram si
Dear Scott,
In message <1354054951.2317.14@tyr> you wrote:
>
> > > vary after code changed. In the early debug phase it would be
> > easier to handle
> > > if the relocation address does not change per build.
> >
> > No, it is not.
>
> Maybe not for you, but for some of us it definitely would m
tis 2012-11-27 klockan 16:22 -0600 skrev Scott Wood:
> How am I going to script gdb to figure out the relocation address when
> I'm just running it on the image to get symbols, not actually
> connecting to the target?
It can be calculated from ram size and size of your u-boot binary
including
On 11/21/2012 02:22:32 AM, Wolfgang Denk wrote:
Dear Tetsuyuki Kobayashi,
In message <1353476660-18018-1-git-send-email-k...@kmckk.co.jp> you
wrote:
>
> U-Boot from NOR flash relocates itself to RAM erea. The relocation
address is
> calaculated at runtime to get maxium contiguous space to l
Dear Tetsuyuki Kobayashi,
In message <1353476660-18018-1-git-send-email-k...@kmckk.co.jp> you wrote:
>
> U-Boot from NOR flash relocates itself to RAM erea. The relocation address is
> calaculated at runtime to get maxium contiguous space to load kernel. So it
> may
> vary after code changed. In
Hello,
U-Boot from NOR flash relocates itself to RAM erea. The relocation address is
calaculated at runtime to get maxium contiguous space to load kernel. So it may
vary after code changed. In the early debug phase it would be easier to handle
if the relocation address does not change per build.
6 matches
Mail list logo