Fwd: JTAG error with arm-rtems-gdb

[Mario Palomares]

---------- Forwarded message ---------
De: Mario Palomares <palomares.mario14 at gmail.com>
Date: dom., 17 may. 2020 a las 18:33
Subject: Re: JTAG error with arm-rtems-gdb
To: Alan Cudmore <alan.cudmore at gmail.com>


Hi Alan,

I have done what you told me (set up the whole environment) and it worked.
First i have to configure the RPI to boot on 64 bit mode (just setting a
parameter on config.txt) and later on could establish GDB connection with
the gdb the aaarch64 toolchain offers. Gdb-multiarch also worked.

It seems the problem is on that amrv8-a53 clusters working in 32 bit mode.
I don´t know if openOCD has support for amv8-a cores working in 32 bit or
if i have to change my configuration file.

Does this make sense to you?

As an alternative in case this doesn´t work i am currently trying to use
the remote debugging through libdebugger but i am experiencing some
problems when building the rtems-libbsd library. Should i ask here or
create another subject?.

Regards,
Mario

El sáb., 16 may. 2020 a las 15:58, Alan Cudmore (<alan.cudmore at gmail.com>)
escribió:

> Hello Mario,
>
> Did you try bringing up the complete bare metal environment in the Bare
> Metal Raspberry Pi 3b JTAG blog entry?
>
> I would verify that that environment with the bare metal Aarch64 examples
> work before trying to get the 32 bit RTEMS binaries to work.
>
> It seems like these should work on the Pi2 with the A53 cores
>
> https://metebalci.com/blog/bare-metal-rpi3-programming/
>
> But the UART example might not work due to the differences between how the
> uarts are used on the Pi2 and 3.
>
>
>
> Does the ARM multiarch GDB work with Aarch64? Maybe try the Aarch64 GDB
> mentioned in the bare metal RPI3 blog entry?
>
>
>
> Alan
>
>
>
>
>
> *From: *Mario Palomares <palomares.mario14 at gmail.com>
> *Sent: *Saturday, May 16, 2020 7:41 AM
> *To: *users at rtems.org
> *Subject: *JTAG error with arm-rtems-gdb
>
>
>
> I am tryining to debug RTEMS programs on mi RPI2 through a JTAG conexion
> with OpenOCD. Right now i have the connection correctly established and i
> can connect through a telnet client. Whenever I try to connect through
> arm-rtems5-gdb i get the following error
>
>
>
> warning: while parsing target description (at line 4): Target description
> specified unknown architecture "aarch64"
> warning: Could not load XML target description; ignoring
> Truncated register 16 in remote 'g' packet
>
>
>
> The configuration file i use for the RPI can be found in this page
>
> https://metebalci.com/blog/bare-metal-raspberry-pi-3b-jtag/. :
>
> I can´t use the configuration file proposed here:
>
>
> https://github.com/ppisa/rpi-utils/blob/master/jtag-debug/rpi2/rpi-jt_usb5.cfg by
> Pavel because my RPI is a RPI2 v1.2 which has the same SoC that the RPI3.
> If i try Pavels configuration file the connection fails.
>
>
>
> I have installed gdb multiarch and tried with it but no luck, when i set
> the architecture to aarch64 i get:
>
>
>
> warning: Architecture rejected target-supplied description
> Truncated register 8 in remote 'g' packet
>
>
>
> Any ideas how to get arround this ?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20200517/70a394e0/attachment.html>