On 11:48 Fri 24 Apr , alfred steele wrote:
> Thanks !
>
> > which ICE do you use?
> I use the the BDI3000. Could there be something wrong with the
> U-boot image or the way u-boot doing a partial u-boot initialization.
> The fact is that it does not even show the entry point/reset vector
> a
Dear alfred steele,
In message <528f13590904240907v16449286t30b8c1b238da9...@mail.gmail.com> you
wrote:
>
> I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
> succesfully using this gdb to a great extent. However, when i try my
> vanilla u-boot image with debug, i get a
Thanks !
> which ICE do you use?
I use the the BDI3000. Could there be something wrong with the
U-boot image or the way u-boot doing a partial u-boot initialization.
The fact is that it does not even show the entry point/reset vector
address in startup. Could it be that my uboot elf image isn't
On 11:07 Fri 24 Apr , alfred steele wrote:
> Hi,
> I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
> succesfully using this gdb to a great extent. However, when i try my
> vanilla u-boot image with debug, i get a "segfault".
which ICE do you use?
>
> $ arm-elf-gdb
Hi,
I am trying to debug u-boot using arm-elf-gdb on the PDK board. I have been
succesfully using this gdb to a great extent. However, when i try my
vanilla u-boot image with debug, i get a "segfault".
$ arm-elf-gdb u-boot
GNU gdb 5.3 (eCosCentric)
Copyright 2002 Free Software Foundation, Inc.
GD
5 matches
Mail list logo