<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Mario,</p><p class=MsoNormal>Yes, what you said makes sense. I don’t have enough experience with the GDB and OpenOCD to know if your use case can be made to work. Perhaps someone on the raspberrypi.org bare metal forum would know?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For your inquiry about libdebugger and rtems-libbsd on the Pi: to my knowledge there is not complete libbsd support for the Pi models yet. I would not expect it to compile right now.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please let us know if you make any progress! If you get openOCD debugging to work with the Pi2 1.2 (A53), it will also probably work with the Pi 3 models.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alan</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:palomares.mario14@gmail.com">Mario Palomares</a><br><b>Sent: </b>Sunday, May 17, 2020 12:38 PM<br><b>To: </b><a href="mailto:users@rtems.org">users@rtems.org</a><br><b>Cc: </b><a href="mailto:alan.cudmore@gmail.com">Alan Cudmore</a><br><b>Subject: </b>Fwd: JTAG error with arm-rtems-gdb</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p class=MsoNormal>---------- Forwarded message ---------<br>De: <strong><span style='font-family:"Calibri",sans-serif'>Mario Palomares</span></strong> <<a href="mailto:palomares.mario14@gmail.com">palomares.mario14@gmail.com</a>><br>Date: dom., 17 may. 2020 a las 18:33<br>Subject: Re: JTAG error with arm-rtems-gdb<br>To: Alan Cudmore <<a href="mailto:alan.cudmore@gmail.com">alan.cudmore@gmail.com</a>></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>Hi Alan,</p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I have done what you told me (set up the whole environment) and it worked. </p></div><div><p class=MsoNormal>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.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Does this make sense to you?</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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?.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards, </p></div><div><p class=MsoNormal>Mario</p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>El sáb., 16 may. 2020 a las 15:58, Alan Cudmore (<<a href="mailto:alan.cudmore@gmail.com" target="_blank">alan.cudmore@gmail.com</a>>) escribió:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hello Mario,</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Did you try bringing up the complete bare metal environment in the Bare Metal Raspberry Pi 3b JTAG blog entry?</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I would verify that that environment with the bare metal Aarch64 examples work before trying to get the 32 bit RTEMS binaries to work.</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It seems like these should work on the Pi2 with the A53 cores</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="https://metebalci.com/blog/bare-metal-rpi3-programming/" target="_blank">https://metebalci.com/blog/bare-metal-rpi3-programming/</a></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>But the UART example might not work due to the differences between how the uarts are used on the Pi2 and 3.</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Does the ARM multiarch GDB work with Aarch64? Maybe try the Aarch64 GDB mentioned in the bare metal RPI3 blog entry?</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Alan</p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From: </b><a href="mailto:palomares.mario14@gmail.com" target="_blank">Mario Palomares</a><br><b>Sent: </b>Saturday, May 16, 2020 7:41 AM<br><b>To: </b><a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a><br><b>Subject: </b>JTAG error with arm-rtems-gdb</p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>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</p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>warning: while parsing target description (at line 4): Target description specified unknown architecture "aarch64"<br>warning: Could not load XML target description; ignoring<br>Truncated register 16 in remote 'g' packet</p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>The configuration file i use for the RPI can be found in this page </p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="https://metebalci.com/blog/bare-metal-raspberry-pi-3b-jtag/" target="_blank">https://metebalci.com/blog/bare-metal-raspberry-pi-3b-jtag/</a>. :</p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I can´t use the configuration file proposed here:</p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a href="https://github.com/ppisa/rpi-utils/blob/master/jtag-debug/rpi2/rpi-jt_usb5.cfg" target="_blank">https://github.com/ppisa/rpi-utils/blob/master/jtag-debug/rpi2/rpi-jt_usb5.cfg</a> 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.</p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I have installed gdb multiarch and tried with it but no luck, when i set the architecture to aarch64 i get:</p></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>warning: Architecture rejected target-supplied description<br>Truncated register 8 in remote 'g' packet</p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> </p></div></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Any ideas how to get arround this ?</p></div></div></blockquote></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:4.8pt'> </p><p class=MsoNormal><o:p> </o:p></p></div></body></html>