<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>The patches I used are in rtems/c/src/lib/libbsp/arm/lm3s69xx/*.patch<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Make sure you’re not using an ELF file. My understanding is that the qemu-system-arm requires a binary image of the code to be run, not a file requiring re-location.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Running the hello example gave me the following:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>grunzasr@stm32dbg% qemu-system-arm -nographic -M lm3s6965evb -kernel hello.ralf<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText> *** HELLO WORLD TEST ***<o:p></o:p></p><p class=MsoPlainText> Hello World<o:p></o:p></p><p class=MsoPlainText> *** END OF HELLO WORLD TEST ***<o:p></o:p></p><p class=MsoPlainText> qemu: hardware error: gic_dist_writeb: Bad offset 4f0<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The hardware error is caused by the BSP not having “a proper board reset”.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The build created the following files:<o:p></o:p></p><p class=MsoPlainText>grunzasr@stm32dbg% ls -l<o:p></o:p></p><p class=MsoPlainText>total 2888<o:p></o:p></p><p class=MsoPlainText>-rwxrwxr-x 1 grunzasr grunzasr 79032 May 8 16:36 hello.bin*<o:p></o:p></p><p class=MsoPlainText>-rwxrwxr-x 1 grunzasr grunzasr 2711472 May 8 16:35 hello.exe*<o:p></o:p></p><p class=MsoPlainText>-rw-rw-r-- 1 grunzasr grunzasr 28045 May 8 16:35 hello.num<o:p></o:p></p><p class=MsoPlainText>-rwxrwxr-x 1 grunzasr grunzasr 79032 May 8 16:35 hello.ralf*<o:p></o:p></p><p class=MsoPlainText>-rw-rw-r-- 1 grunzasr grunzasr 37040 May 8 16:35 test.o<o:p></o:p></p><p class=MsoPlainText>grunzasr@stm32dbg% file hello.exe<o:p></o:p></p><p class=MsoPlainText>hello.exe: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, not stripped grunzasr@stm32dbg% file hello.ralf<o:p></o:p></p><p class=MsoPlainText>hello.ralf: data<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I’m not sure what the .ralf extension is supposed to mean but if you watch the build you’ll see that the .ralf file is the result of running arm-*-objcopy on the .exe (ELF) file with the binary output option; therefore, the .ralf file is a binary file.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Steven G<o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> rtems-users-bounces@rtems.org [mailto:rtems-users-bounces@rtems.org] <b>On Behalf Of </b>Aric Hunter<br><b>Sent:</b> Thursday, July 19, 2012 5:36 PM<br><b>To:</b> rtems-users@rtems.org<br><b>Subject:</b> Re: Virtualbox RTEMS Setup<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I installed qemu-system-arm and attempted to test the lm3s6965 with a test file in the pc386 testsuite and got this error.<o:p></o:p></p><div><p class=MsoNormal><br>lm3s6965 -v -i hello.exe<br>Default program to run is<br>Using qemu-system-arm<br>qemu-system-arm is /usr/local/bin/qemu-system-arm<br>TESTS TO RUN: hello.exe<br>INTERACTIVE runtest hello.exe single 0<br>qemu-system-arm -nographic -M lm3s6965evb -kernel hello.exe<br>qemu: fatal: Bad mode 1c<o:p></o:p></p><div><p class=MsoNormal>R00=00000000 R01=0000007f R02=00000000 R03=00000000<br>R04=00890089 R05=00000000 R06=00000000 R07=00000000<br>R08=00000000 R09=00000000 R10=00000000 R11=00000000<br>R12=00000000 R13=464c457f R14=00000000 R15=00010118<br>PSR=00000173 ---- T svc32<br>Aborted (core dumped)<br><br>what patches are you talking about for lm3s6965?<br>I see some binpatch files, but not much else.<br><br> <o:p></o:p></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><o:p> </o:p></p><div><p class=MsoNormal>On Thu, Jul 19, 2012 at 10:28 AM, Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>On Thu, Jul 19, 2012 at 1:12 PM, Joel Sherrill<br><<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>> wrote:<br>> On 07/19/2012 12:05 PM, Aric Hunter wrote:<br>><br>> Fantastic!!!<br>> I looked into /home/rtems/qemu/install/bin and saw the qemu-system-i386 file<br>> that you mentioned, and after the update everything with the i386/pc386<br>> works just fine.<br>><br>> If you have time:<br>> How do I get qemu-system-arm?<br>> Is it as simple as another git update?<br>><br>> On that virtualbox image, the qemu was pulled from their git<br>> and built. You just need to do their build and let it build everything.<br>> I restricted it to i386 for size.<br>><o:p></o:p></p></div><p class=MsoNormal>IIRC for lm3sxx there are some patches for qemu in the bsp directory..<br>not sure if they are still necessary.<o:p></o:p></p><div><div><p class=MsoNormal><br>> Thanks oodles,<br>> Aric Hunter<br>><br>> On Thu, Jul 19, 2012 at 9:27 AM, Joel Sherrill <<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>><br>> wrote:<br>>><br>>> On 07/19/2012 11:25 AM, Aric Hunter wrote:<br>>><br>>> I tried solution 1) already (PATH=$PATH:/home/rtems/qemu/install/bin)<br>>> I haven't tried solution 2.<br>>> So, for solution 2, somewhere in the pc386 script it attempts to run qemu<br>>> but it should be qemu-system-i386?<br>>><br>>> Yep.<br>>><br>>> You could update the rtems-testing git module and type make :)<br>>><br>>> ls /home/rtems/qemu/install/bin and see what's there<br>>><br>>> I will look for that.<br>>><br>>> Thanks for the amazingly quick replies,<br>>> Aric Hunter<br>>><br>>> On Thu, Jul 19, 2012 at 9:10 AM, Joel Sherrill <<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>><br>>> wrote:<br>>>><br>>>> Hi<br>>>><br>>>> I know this has been answered before but I don't recall which<br>>>> answer it is:<br>>>><br>>>> (1) qemu is not in your PATH. The qemu installation was<br>>>> left out of setting the PATH in the setenv script<br>>>> (2) It is really called qemu-system-i386 and the script<br>>>> needs to use the correct name. qemu renamed this.<br>>>><br>>>> -joel<br>>>><br>>>><br>>>> On 07/19/2012 11:02 AM, Aric Hunter wrote:<br>>>>><br>>>>> Hello,<br>>>>><br>>>>> I am attempting to get the RTEMS development station setup on the Centos<br>>>>> virtualbox.<br>>>>> I was following the instructions on the wiki:<br>>>>><br>>>>> <a href="http://www.rtems.com/wiki/index.php/Virtual_Machines_for_RTEMS_Development" target="_blank">http://www.rtems.com/wiki/index.php/Virtual_Machines_for_RTEMS_Development</a><br>>>>><br>>>>> I got to the section for testing the i386/pc386 without any problems,<br>>>>> but then I tried to do tho the following command:<br>>>>> pc386 -i<br>>>>> ./rtems-4.11-work/b-pc386/i386-rtems4.11/c/pc386/testsuites/samples/hello/hello.exe<br>>>>> and got this error:<br>>>>> /home/rtems/rtems-4.11-work/rtems-testing/bin/pc386: line 298:<br>>>>> type: qemu: not found<br>>>>> FAILED: Path appears to be broken (cannot find qemu)<br>>>>><br>>>>> Any ideas as to what I am missing/doing incorrectly?<br>>>>><br>>>>> My ultimate goal is to run lm3s6965 instead of pc386, but I get the same<br>>>>> error with either.<br>>>>><br>>>>> Thanks,<br>>>>> Aric Hunter<br>>>><br>>>><br>>>><br>>>> --<br>>>> Joel Sherrill, Ph.D. Director of Research& Development<br>>>> <a href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research<br>>>> Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>>>> Support Available <a href="tel:%28256%29%20722-9985" target="_blank">(256) 722-9985</a><br>>>><br>>>><br>>><br>>><br>>><br>>> --<br>>> Joel Sherrill, Ph.D. Director of Research& Development<br>>> <a href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research<br>>> Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>>> Support Available <a href="tel:%28256%29%20722-9985" target="_blank">(256) 722-9985</a><br>>><br>><br>><br>><br>> --<br>> Joel Sherrill, Ph.D. Director of Research& Development<br>> <a href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research<br>> Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>> Support Available <a href="tel:%28256%29%20722-9985" target="_blank">(256) 722-9985</a><br>><br>><o:p></o:p></p></div></div><div><div><p class=MsoNormal>> _______________________________________________<br>> rtems-users mailing list<br>> <a href="mailto:rtems-users@rtems.org" target="_blank">rtems-users@rtems.org</a><br>> <a href="http://www.rtems.org/mailman/listinfo/rtems-users" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-users</a><br>><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>