Hi Vladimir, I have built the edk2 firmware using the following toolchains and find that the symbols are loaded correctly using DS5. - gcc-arm-8.3-2019.03-x86_64-aarch64-elf.tar.xz - gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz The above toolchains are available at https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads
So, it looks like the problem you mention may have something to do with the toolchain shipped with Yocto. Regards, Sami Mujawar -----Original Message----- From: Ard Biesheuvel <ard.biesheu...@linaro.org> Sent: 11 December 2019 02:51 PM To: Vladimir Olovyannikov <vladimir.olovyanni...@broadcom.com> Cc: Sami Mujawar <sami.muja...@arm.com>; edk2-devel-groups-io <devel@edk2.groups.io> Subject: Re: Debugging aarch64 edk2 built with gcc-8.x 64-bit arm compiler On Tue, 10 Dec 2019 at 18:25, Vladimir Olovyannikov <vladimir.olovyanni...@broadcom.com> wrote: > > > -----Original Message----- > > From: Ard Biesheuvel <ard.biesheu...@linaro.org> > > Sent: Tuesday, December 10, 2019 9:13 AM > > To: Vladimir Olovyannikov <vladimir.olovyanni...@broadcom.com>; Sami > > Mujawar <sami.muja...@arm.com> > > Cc: edk2-devel-groups-io <devel@edk2.groups.io> > > Subject: Re: Debugging aarch64 edk2 built with gcc-8.x 64-bit arm > > compiler > > > > On Sat, 7 Dec 2019 at 00:50, Vladimir Olovyannikov > > <vladimir.olovyanni...@broadcom.com> wrote: > > > > > > Hi Ard, > > > > > > > > > > > > We are about to switch to the latest Yocto. It is shipped with > > > gcc-8.3 > > aarch64-linux-gnu compiler. > > > > > > We use DS5 for bare metal debugging. > > > > > > When I build edk2 with gcc-7-x/gcc-8.x, DS5 complains on DWARF format. > > > I tried to explicitly set it to DWARF2, but still cannot even get > > > the stack or local variables (even though DS5 does not complain), > > > even for > > > edk2 > > NOOPT build. > > > > > > > > > > > > Using gcc-6.3 from Linaro, I don’t see any issue with DS5 debugging. > > > > > > Am I missing any steps? > > > > > > Build is done with GCC5_AARCH64_PREFIX=aarch64-linux-gnu > > > > > > > > > > > > Another question: it seems that the DS5 scripts limit the path > > > size with > > > 255 > > chars. With a source built by Yocto, it can easily be more than that. > > > > > > Attempt to add symbols for such modules ends up with error message > > > in > > the DS5 command window that it could not add those symbols. > > > > > > Is there a procedure to increase the path length limit? > > > > > > > I have never in my life used a DS-5 to debug EDK2 running on bare > > metal, so unfortunately, I won't be able to help you. > > > How do you normally debug edk2 with DS5? Or, are you using a different > mechanism? > Debugging with DS5 was/is very convenient. > I do my prototyping mainly in QEMU, using GDB for debug. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#52168): https://edk2.groups.io/g/devel/message/52168 Mute This Topic: https://groups.io/mt/67569981/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
