Re: [arm-gnu] GNU Toolchain and Keil ULINK2 HLL debugging
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [arm-gnu] GNU Toolchain and Keil ULINK2 HLL debugging



Hello Carlos,
I am seeing this same issue on a Cortex-M3 target (LPC1769), using the
latest release of the tools, in the same toolset configuration.

It seems to be a problem with the toolchain, as for other example
projects this error does not show up and they work as expected (so the
hw should be fine)

The output from binutils (readelf) seems to be fine as well, no
strange things noticed so far.

Do you have more information to share on this issue, is this a known
problem, is there a patch for it ?

Thanks,
Best Regards
Giancarlo

Re: [arm-gnu] GNU Toolchain and Keil ULINK2 HLL debugging

    * To: arm-gnu@xxxxxxxxxxxxxxxx
    * Subject: Re: [arm-gnu] GNU Toolchain and Keil ULINK2 HLL debugging
    * From: Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx>
    * Date: Tue, 23 Nov 2010 11:27:42 -0500

On 11/23/2010 3:24 AM, Stahl, Michael wrote:
> Hi,
> I have a project which is build with the CodeSourcery G++ Lite GNU
> Toolchain. The compiler option -gdwarf-2 is on.
> Now I create a new uVision4 Project, select the Micro (STM32F103ZE)
> and set up in the OPTION dialog under OUTPUT the name of the elf-file
> at "Name of Executable". Afterwards I choose the ULINK Cortex Debugger
> at the DEBUG tab and select "Load Application at Startup" and "Run to
> main()"
>
> Also I write a ini-file where are the SET SRC commands to all
> directorys of my project.
>
> So after I push the button Start/Stop Debug Session there will be a
> message in the output window: *"*** Warning: corrupted .debug_loc
> section info ignored, locations of local symbols are unknown" and
> "Cannot access Memory*"
>
> The programm stops at main. Every time I push the button Step the
> message "Cannot access Memory" will be come again.
>
> What can I do to do a high-level-language-debugging with ULINK2

The Sourcery G++ IDE supports debugging with a ULINK2, and is able to
debug binaries produced by the Lite version of the tools.

Cheers,
Carlos.
--
Carlos O'Donell
CodeSourcery
carlos@xxxxxxxxxxxxxxxx
(650) 331-3385 x716