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
Sent: Saturday, May 16, 2020 7:41 AM
To: users@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 

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 ?

 

_______________________________________________
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Reply via email to