Virtualbox RTEMS Setup

Joel Sherrill joel.sherrill at OARcorp.com
Thu Jul 19 17:12:22 UTC 2012


On 07/19/2012 12:05 PM, Aric Hunter wrote:
> Fantastic!!!
> I looked into /home/rtems/qemu/install/bin and saw the 
> qemu-system-i386 file that you mentioned, and after the update 
> everything with the i386/pc386 works just fine.
>
> If you have time:
> How do I get qemu-system-arm?
> Is it as simple as another git update?
>
On that virtualbox image, the qemu was pulled from their git
and built. You just need to do their build and let it build everything.
I restricted it to i386 for size.
> Thanks oodles,
> Aric Hunter
>
> On Thu, Jul 19, 2012 at 9:27 AM, Joel Sherrill 
> <joel.sherrill at oarcorp.com <mailto:joel.sherrill at oarcorp.com>> wrote:
>
>     On 07/19/2012 11:25 AM, Aric Hunter wrote:
>>     I tried solution 1) already (PATH=$PATH:/home/rtems/qemu/install/bin)
>>     I haven't tried solution 2.
>>     So, for solution 2, somewhere in the pc386 script it attempts to
>>     run qemu but it should be qemu-system-i386?
>     Yep.
>
>     You could update the rtems-testing git module and type make :)
>
>     ls /home/rtems/qemu/install/bin and see what's there
>
>>     I will look for that.
>>
>>     Thanks for the amazingly quick replies,
>>     Aric Hunter
>>
>>     On Thu, Jul 19, 2012 at 9:10 AM, Joel Sherrill
>>     <joel.sherrill at oarcorp.com <mailto:joel.sherrill at oarcorp.com>> wrote:
>>
>>         Hi
>>
>>         I know this has been answered before but I don't recall which
>>         answer it is:
>>
>>         (1) qemu is not in your PATH. The qemu installation was
>>              left out of setting the PATH in the setenv script
>>         (2) It is really called qemu-system-i386 and the script
>>              needs to use the correct name. qemu renamed this.
>>
>>         -joel
>>
>>
>>         On 07/19/2012 11:02 AM, Aric Hunter wrote:
>>
>>             Hello,
>>
>>             I am attempting to get the RTEMS development station
>>             setup on the Centos virtualbox.
>>             I was following the instructions on the wiki:
>>             http://www.rtems.com/wiki/index.php/Virtual_Machines_for_RTEMS_Development
>>
>>             I got to the section for testing the i386/pc386 without
>>             any problems, but then I tried to do tho the following
>>             command:
>>                     pc386 -i
>>             ./rtems-4.11-work/b-pc386/i386-rtems4.11/c/pc386/testsuites/samples/hello/hello.exe
>>             and got this error:
>>                    
>>             /home/rtems/rtems-4.11-work/rtems-testing/bin/pc386: line
>>             298: type: qemu: not found
>>                     FAILED:  Path appears to be broken (cannot find qemu)
>>
>>             Any ideas as to what I am missing/doing incorrectly?
>>
>>             My ultimate goal is to run lm3s6965 instead of pc386, but
>>             I get the same error with either.
>>
>>             Thanks,
>>             Aric Hunter
>>
>>
>>
>>         -- 
>>         Joel Sherrill, Ph.D.             Director of Research&  
>>         Development
>>         joel.sherrill at OARcorp.com <mailto:joel.sherrill at OARcorp.com>
>>                On-Line Applications Research
>>         Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>             Support Available (256) 722-9985 <tel:%28256%29%20722-9985>
>>
>>
>>
>
>
>     -- 
>     Joel Sherrill, Ph.D.             Director of Research&   Development
>     joel.sherrill at OARcorp.com  <mailto:joel.sherrill at OARcorp.com>         On-Line Applications Research
>     Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>          Support Available(256) 722-9985  <tel:%28256%29%20722-9985>
>
>


-- 
Joel Sherrill, Ph.D.             Director of Research&   Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
     Support Available             (256) 722-9985


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120719/7b76ec80/attachment-0001.html>


More information about the users mailing list