Simulator for MPC5200

Joel Sherrill joel.sherrill at OARcorp.com
Wed Aug 8 13:52:58 UTC 2012


On 08/08/2012 08:19 AM, Gedare Bloom wrote:
>
>
> On Tue, Aug 7, 2012 at 8:09 PM, Gedare Bloom <gedare at rtems.org 
> <mailto:gedare at rtems.org>> wrote:
>
>
>
>     On Tue, Aug 7, 2012 at 6:20 PM, Binkowski, Cassio
>     <cassioiks at gmail.com <mailto:cassioiks at gmail.com>> wrote:
>
>
>
>         On Tue, Aug 7, 2012 at 4:33 PM, Joel Sherrill
>         <joel.sherrill at oarcorp.com <mailto:joel.sherrill at oarcorp.com>>
>         wrote:
>
>             On 08/07/2012 02:30 PM, Binkowski, Cassio wrote:
>>             Thank you Steven!
>>             I was able to get it from your tips.
>>
>>             Now, another doubt. I know the following won't do it for
>>             PowerPC:
>>
>>             ~/qemu/install/bin/qemu-system-i386 -M pc -m 128    
>>             -boot a -fda /home/rtems/qemu/pc386_fda -hda
>>             fat:/home/rtems/qemu/hd/ -serial stdio --no-reboot
>>
>>             Besides using *qemu-system-ppc* and *-M prep*, what else
>>             do I have to change to make it work?
>>             I know that I'll have to change the -FDA term, but I
>>             don't what to change it for.
>>             Does anybody know this?
>>
>             Check out rtems-testing from git. There is a directory in
>             there called
>             sim-scripts which has wrappers for almost all of the
>             simulators
>             we know you can run RTEMS on. You are looking for "qemuppc" :)
>
>         :)
>
>         Got it.
>
>         It generates and error on line 227:
>
>         227. type ${runBSP}
>         228. check_status $? "Path appears to be broken (cannot find
>         ${runBSP})"
>
>         runBSP is declared in line 168:
>
>         168. runBSP=qemu-system-ppc
>
>         Am I missing something?
>         P.S: The file "qemu-system-ppc" is in the same directory level
>         as the script and I'm passing the following parameters
>         "./qemuppc -i test.exe"
>
>     Put "." in your PATH or install qemu-system-ppc to a location in
>     your PATH. The latter is a better option.
>
> I should add that putting "." in your PATH is a security risk. It is 
> much better to install the binary to the appropriate location (which 
> most likely is /usr/local/bin and already in your PATH).
>

The simulator needs to be in your PATH.

It is not invoked that way. You invoke all of the scripts in sim-scripts 
the same way.

BSP [options] EXE

For some the .exe is OK to run because the target simulator directly 
runs ELF. For others,
you need to use the .ralf (RTEMS Application Loadable File) which is in 
the random format
needed for the target BSP.

Usually you want something like this:

qemuppc -i FILE.exe

The -i says run it interactively. Otherwise, it just runs and captures 
output in a log file
for later examination. These scripts are used for batch testing and 
coverage testing.


> -Gedare
>
>         Regards
>
>
>>             Thanks
>>
>>             On Tue, Aug 7, 2012 at 9:49 AM, Steven Grunza
>>             <sgrunza at ctdi.com <mailto:sgrunza at ctdi.com>> wrote:
>>
>>                 Looks like you tried to configure within the qemu
>>                 source directory.  I usually build in a separate
>>                 directory.
>>
>>                 mkdir b-qemu
>>
>>                 cd b-qemu
>>
>>                 ../qemu.git/configure --target-list="ppc-softmmu"
>>                 --prefix=/usr/local/bin
>>
>>                 Install prefix    /usr/local/bin
>>
>>                 BIOS directory    /usr/local/bin/share/qemu
>>
>>                 binary directory  /usr/local/bin/bin
>>
>>                 library directory /usr/local/bin/lib
>>
>>                 include directory /usr/local/bin/include
>>
>>                 config directory  /usr/local/bin/etc
>>
>>                 Manual directory  /usr/local/bin/share/man
>>
>>                 ELF interp prefix /usr/gnemul/qemu-%M
>>
>>                 Source path       /home/grunzasr/qemu.git
>>
>>                 C compiler        gcc
>>
>>                 Host C compiler   gcc
>>
>>                 CFLAGS            -O2 -D_FORTIFY_SOURCE=2 -g
>>
>>                 QEMU_CFLAGS       -fPIE -DPIE -m64 -D_GNU_SOURCE
>>                 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
>>                 -Wstrict-prototypes -Wredundant-decls -Wall -Wundef
>>
>>                 -Wwrite-strings -Wmissing-prototypes
>>                 -fno-strict-aliasing  -Werror -fstack-protector-all
>>                 -Wendif-labels -Wmissing-include-dirs -Wnested-externs
>>
>>                 -Wformat-security -Wformat-y2k -Winit-self
>>                 -Wold-style-definition -I/usr/include/libpng12
>>
>>                 LDFLAGS           -Wl,--warn-common -Wl,-z,relro
>>                 -Wl,-z,now -pie -m64 -g
>>
>>                 make              make
>>
>>                 install           install
>>
>>                 python            python
>>
>>                 smbd              /usr/sbin/smbd
>>
>>                 host CPU          x86_64
>>
>>                 host big endian   no
>>
>>                 target list       ppc-softmmu
>>
>>                 tcg debug enabled no
>>
>>                 Mon debug enabled no
>>
>>                 gprof enabled     no
>>
>>                 sparse enabled    no
>>
>>                 strip binaries    yes
>>
>>                 profiler          no
>>
>>                 static build      no
>>
>>                 -Werror enabled   yes
>>
>>                 SDL support       yes
>>
>>                 curses support    yes
>>
>>                 curl support      no
>>
>>                 mingw32 support   no
>>
>>                 Audio drivers     oss
>>
>>                 Extra audio cards ac97 es1370 sb16 hda
>>
>>                 Block whitelist
>>
>>                 Mixer emulation   no
>>
>>                 VirtFS support    no
>>
>>                 VNC support       yes
>>
>>                 VNC TLS support   no
>>
>>                 VNC SASL support  no
>>
>>                 VNC JPEG support  yes
>>
>>                 VNC PNG support   yes
>>
>>                 xen support       no
>>
>>                 brlapi support    no
>>
>>                 bluez  support    no
>>
>>                 Documentation     yes
>>
>>                 NPTL support      yes
>>
>>                 GUEST_BASE        yes
>>
>>                 PIE               yes
>>
>>                 vde support       no
>>
>>                 Linux AIO support no
>>
>>                 ATTR/XATTR support yes
>>
>>                 Install blobs     yes
>>
>>                 KVM support       yes
>>
>>                 TCG interpreter   no
>>
>>                 fdt support       no
>>
>>                 preadv support    no
>>
>>                 fdatasync         yes
>>
>>                 madvise           yes
>>
>>                 posix_madvise     yes
>>
>>                 uuid support      no
>>
>>                 libcap-ng support no
>>
>>                 vhost-net support yes
>>
>>                 Trace backend     nop
>>
>>                 Trace output file trace-<pid>
>>
>>                 spice support     no
>>
>>                 rbd support       no
>>
>>                 xfsctl support    no
>>
>>                 nss used          no
>>
>>                 usb net redir     no
>>
>>                 OpenGL support    yes
>>
>>                 libiscsi support  no
>>
>>                 build guest agent yes
>>
>>                 coroutine backend ucontext
>>
>>                 grunzasr at stm32dbg% ls -FC
>>
>>                 config-host.ld   config.log  libdis/       libhw32/ 
>>                 libuser/        Makefile@  ppc-softmmu/    
>>                 qdict-test-data.txt@  roms/
>>
>>                 config-host.mak  libcacard/  libdis-user/  libhw64/ 
>>                 linux-headers/  pc-bios/   qapi-generated/ 
>>                 QMP/                  tests/
>>
>>                 grunzasr at stm32dbg%
>>
>>                 I don’t know if the code will build but the “make” is
>>                 currently running…
>>
>>                 *From:*rtems-users-bounces at rtems.org
>>                 <mailto:rtems-users-bounces at rtems.org>
>>                 [mailto:rtems-users-bounces at rtems.org
>>                 <mailto:rtems-users-bounces at rtems.org>] *On Behalf Of
>>                 *Binkowski, Cassio
>>                 *Sent:* Tuesday, August 07, 2012 6:54 AM
>>                 *To:* Joel Sherrill
>>                 *Cc:* rtems-users at rtems.org
>>                 <mailto:rtems-users at rtems.org>
>>                 *Subject:* Re: Simulator for MPC5200
>>
>>                 Ok. Downloaded the tools.
>>
>>                 I'm trying to build Qemu for PowerPC now. I run the
>>                 following line, as I found in the Notes file inside
>>                 QEMU directory:
>>
>>                 ./configure --target-list="ppc-softmmu"
>>                 --prefix=/home/rtems/qemu/install >c.log 2>&1 ; echo $?
>>
>>                 ... and get this:
>>
>>                 head: cannot open `/root/Desktop/rtems\'' for
>>                 reading: No such file or directory
>>
>>                 head: cannot open `Home/qemu/qemu/VERSION' for
>>                 reading: No such file or directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.dis': No such file or directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.dis': No such file or directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/linux-headers/asm-x86': No such file
>>                 or directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.target': No such file or
>>                 directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.hw': No such file or directory
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.hw': No such file or directory
>>
>>                 ./configure: line 3876: [: too many arguments
>>
>>                 ln: creating symbolic link
>>                 `Home/qemu/qemu/Makefile.user': No such file or directory
>>
>>                 Has anyone had this before?
>>
>>                 Best regards
>>
>>
>
>
>             -- 
>             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>
>
>
>
>         _______________________________________________
>         rtems-users mailing list
>         rtems-users at rtems.org <mailto:rtems-users at rtems.org>
>         http://www.rtems.org/mailman/listinfo/rtems-users
>
>
>


-- 
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/20120808/f3cd8cab/attachment-0001.html>


More information about the users mailing list