Hello,
I'm trying to debug U-Boot (version: imx_v2014.04_3.14.28_1.0.0_ga) for
a custom board with a BDI3000.
So far I can connect to the target and I see the U-Boot code at the
correct location, but after reset the PC is at 0x1ffa870c which is
somewhere outside of U-Boot. Here the state after
Hi
In reply to this, can anyone please suggest me, how to debug the
fw_printenv code in u-boot?
I am using buildroot-2014.02, which used uboot-tools-2014.01. But I am
having few custom changes in uboot-2010.03, those I want to use, in
tools-2014.01 I can see as of now, the code fails on fw_printen
Dear Mirko Banchi,
In message <857d4443-39b6-43b0-b269-bb6ce7c9a...@gmail.com> you wrote:
>
> > Could you please explain which information you consider missing in
> > these sections of the manual?
> >
> > 10.1. Debugging of U-Boot
> >
> >10.1.1. Debugging of U-Boot Before Relocation
> >
Il giorno 30/ago/2011, alle ore 14.55, Wolfgang Denk ha scritto:
> Dear Mirko Banchi,
>
> In message <659acfbd-2b5d-4f28-89bf-5473d90ad...@gmail.com> you wrote:
>> Hi all, could someone write briefly the steps needed to debug u-boot with
>> BDI2000? I can-t find documentation about it. On-line
Dear Mirko Banchi,
In message <659acfbd-2b5d-4f28-89bf-5473d90ad...@gmail.com> you wrote:
> Hi all, could someone write briefly the steps needed to debug u-boot with
> BDI2000? I can-t find documentation about it. On-line docs specify only how
> to proceed with gdb after that the host bdi is up
> To set up the BDI2000 please refer to the Abatron manual.
This was the missing step :)
Thank you Stefano!
Mirko
--
Mirko Banchi
e-mail:mk.ban...@gmail.com
id-jabber: mk.ban...@jabber.org
PGP key fingerprint:
308F BFB1 4E67 2522 C88E
DC69 7631 52ED 32A5 6456
_
On 08/30/2011 01:59 PM, Mirko Banchi wrote:
> Hi all, could someone write briefly the steps needed to debug u-boot
> with BDI2000? I can-t find documentation about it. On-line docs
> specify only how to proceed with gdb after that the host bdi is up
> and configured.
http://www.denx.de/wiki/view/D
Hi all, could someone write briefly the steps needed to debug u-boot with
BDI2000? I can-t find documentation about it. On-line docs specify only how to
proceed with gdb after that the host bdi is up and configured.
Thank you all!
Mirko
--
Mirko Banchi
e-mail:mk.ban...@gmail.com
id-jabber
Dear Mark Fanara,
In message you
wrote:
> As my target board is PowerPC based (and therefore skipping relocation
> is not possible), I need help with my previously enumerated questions.
>
> 1) In section 10.4, Tips and Tricks, it says "To prevent GDB from
> jumping around in the code when tryin
As my target board is PowerPC based (and therefore skipping relocation
is not possible), I need help with my previously enumerated questions.
1) In section 10.4, Tips and Tricks, it says "To prevent GDB from
jumping around in the code when trying to single step, i. e. when it
seems as if the code
Dear Wolfgang Denk,
Yes, it is true.
Currently only for ARMs and i386.
Best Regards,
Alan
On 5/27/10, Wolfgang Denk wrote:
> Dear Alan Carvalho de Assis,
>
> In message
> you wrote:
>> Hi Mark,
>>
>> On 5/27/10, Mark Fanara wrote:
>> ...
>> >
>> > 2) I am using a bdi3000. Is there no way to
Dear Alan Carvalho de Assis,
In message you
wrote:
> Hi Mark,
>
> On 5/27/10, Mark Fanara wrote:
> ...
> >
> > 2) I am using a bdi3000. Is there no way to build u-boot so that it is
> > directly loaded to RAM by the debugger and does not relocate itself?
> >
>
> #define CONFIG_SKIP_RELOCATE_U
Hi Mark,
On 5/27/10, Mark Fanara wrote:
...
>
> 2) I am using a bdi3000. Is there no way to build u-boot so that it is
> directly loaded to RAM by the debugger and does not relocate itself?
>
#define CONFIG_SKIP_RELOCATE_UBOOT
BRs,
Alan
___
U-Boot ma
I have read section 10 of the manual which describes debugging u-boot
and have further questions.
1) In section 10.4, Tips and Tricks, it says "To prevent GDB from
jumping around in the code when trying to single step, i. e. when it
seems as if the code is not executing line by line, you can recom
Dear =?iso-8859-1?Q?Bj=F8rnar_Syverstad?=,
In message <3f466ddf09a55d46858fc39b22de56f23a30259...@pat.prediktor.no> you
wrote:
>
> I am trying to debug the u-boot with help of gdb + eclipse. Useing the
> phy3250_config.
>
> The problem is that when debugging, the listed source code seems to be o
Hello,
I am trying to debug the u-boot with help of gdb + eclipse. Useing the
phy3250_config.
The problem is that when debugging, the listed source code seems to be out of
sync.
The debugger pointer in the source code, seems not to point to the correct
source code.
The assembler windows shows
Dear "Dunda, Matthias",
In message
<569685f045b85741820d0265e0d2999d019cf...@tddhh01.hh.thales-naval.de> you wrote:
>
> Then, I calculate the RAM address for the symbols as described in
> DULG-10.1.2.:
>
> RAM is 512 MB --> 0x2000
> Monitor Len according to board specific file is 256k --
Hi again,
following up on my other message, I split them up into seperate messages, as
I think there are different reasons.
When I start the target from the BDI shell with "RESET RUN" and wait until
the "Hit any key to stop autoboot" message appears, I can then attach to the
target :
Remote debu
Hi,
I'm having trouble debugging U-Boot (version 2008.10) with a BDI2000 on
an Embedded Planet EP8248 board (MPC8248 processor). According to
"Embedded Linux Primer" by Christopher Hanin, early U-Boot debugging
must be done using hardware breakpoints, because it is running out of
flash at that po
Hello,
I have a board with MPC852T, SDRAM and FLASH.
I have been successful to get the console up and debug the FLASH and SDRAM
connections.
Now the SDRAM passes all the memory tests in SLOW mode also.
The current problem I am facing is that relocate_code is being called from
the lib_ppc/board.c
a
20 matches
Mail list logo
