Using MPC750/MCP750, QEMUPREP, Or QEMUPPC?

[Joel Sherrill]

On Mon, Jan 23, 2017 at 1:33 PM, DiGiorgio, Joseph <jdigiorg at ball.com>
wrote:

> I am trying to run RTEMS on QEMU using ideally the mpc750 target and as a
> secondary PReP. I have run into a few issues so far and will outline them
> below.
>
>
>
> 1) This is more of a curiosity thing than  something majorly important,
> but is the Power PC 750 target mis-labeled as “mcp750”? All the
> documentation I have come across says “MPC750” and searching for “MCP750”
> via Google pulls up mostly RTEMS documentation and one Motorola document
> that is not available, but cached by Google with headings as “MCP750”, but
> in the body text uses “MPC750”.
>
>
>

The MPC750 was the PowerPC CPU. The MCP750 was a CompactPCI
board from Motorola Computer Group (MCG). Long ago, the semiconductor
parts of Motorola split into On and Freescale (e.g. NXP/Qualcomm). MCG
eventually became part of Emerson.

The documentation online has withered as these transitions happened.
However, these old CompactPCI and VMEbus boards are still fairly
common at places like national science labs and NASA.


> 2) I ideally want to run the 750 target and am able to build RTEMS just
> fine, but cannot find documentation on using that particular target in
> QEMU. If anyone can point me in the right direction, the rest of the issues
> below become less important.
>
>
>

What's your ultimate target HW?


> 3) I decided to try the “qemu” targets for PPC. I found both “qemuppc” and
> “qemuprep” at https://devel.rtems.org/wiki/TBR/BSP and only “qemuprep” at
> https://devel.rtems.org/wiki/TBR/Website/Board_Support_
> Packages#PowerPCBSPs.  I was wary of “qemuprep” since it has question
> marks next to it, so I tried “qemuppc”. That built just fine, but did not
> see any documentation using “qemuppc” RTEMS in QEMU. I was going to adapt
> https://devel.rtems.org/wiki/Developer/Simulators/QEMU/Preparation , but
> did not see a built fakerom bin file.
>
>
>

The rtems-testing git repo has a directory sim-scripts which has a script
for running qemuppc. I will admit to not having personally used it in a long
time but the scripts in this directory ease running various simulators by
attempting to provide a very consistent command line interface.

Also.. qemu can be fickle about a particular target working from one version
to the next. I am not sure it the RSB version has been tested against this.

Anyway.. you have been warned. It worked at one point. and can be
made to work again :)



> 4) I then tried “qemuprep” since it has documentation, but it fails
> building for “fsdosfssync01.exe” (ld returned 1 exit status) See below
> actual output
>
>
>
> So I guess has anyone had success running RTEMS in QEMU using any of the
> above PPC targets or something close enough to the above targets that I can
> get a sample working?
>
>
>

PowerPC psim BSP uses the PowerPC simulator in GDB. It is used for
testing fairly heavily.

I don't see the cause of the failure in this. I have built all BSPs with
all tests
for 4.12 recently and just built 4.11 for powerpc/qemuprep. I did not see
this
failure.

Was there any other hint?  Did you run out of disk space?

What exactly was the configure command

--joel


>
>
> QEMUPReP Build Error Output:
>
>
>
>     Making all in fsdosfssync01
>
>     make[6]: Entering directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep/testsuites/fstests/
> fsdosfssync01'
>
>     powerpc-rtems4.11-gcc -B../../../../../qemuprep/lib/ -specs bsp_specs
> -qrtems -DHAVE_CONFIG_H -I. -I../../../../../../../Source/
> c/src/../../testsuites/fstests/fsdosfssync01 -I..
> -I../../../../../../../Source/c/src/../../testsuites/fstests/../support/include
> -mcpu=powerpc -mmultiple -mstring -mstrict-align -D__ppc_generic -O2 -g
> -Wall -Wmissing-prototypes -Wimplicit-function-declaration
> -Wstrict-prototypes -Wnested-externs -MT init.o -MD -MP -MF .deps/init.Tpo
> -c -o init.o ../../../../../../../Source/c/src/../../testsuites/fstests/
> fsdosfssync01/init.c
>
>     mv -f .deps/init.Tpo .deps/init.Po
>
>     powerpc-rtems4.11-gcc -B../../../../../qemuprep/lib/ -specs bsp_specs
> -qrtems -mcpu=powerpc -mmultiple -mstring -mstrict-align -D__ppc_generic
> -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration
> -Wstrict-prototypes -Wnested-externs    -mcpu=powerpc -mmultiple -mstring
> -mstrict-align -D__ppc_generic   -o fsdosfssync01.exe init.o
>
>     collect2: error: ld returned 1 exit status
>
>     Makefile:618: recipe for target 'fsdosfssync01.exe' failed
>
>     make[6]: *** [fsdosfssync01.exe] Error 1
>
>     make[6]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep/testsuites/fstests/
> fsdosfssync01'
>
>     Makefile:585: recipe for target 'all-local' failed
>
>     make[5]: *** [all-local] Error 1
>
>     make[5]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep/testsuites/fstests'
>
>     Makefile:247: recipe for target 'all' failed
>
>     make[4]: *** [all] Error 2
>
>     make[4]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep/testsuites/fstests'
>
>     Makefile:314: recipe for target 'all-recursive' failed
>
>     make[3]: *** [all-recursive] Error 1
>
>     make[3]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep/testsuites'
>
>     Makefile:425: recipe for target 'all-recursive' failed
>
>     make[2]: *** [all-recursive] Error 1
>
>     make[2]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c/qemuprep'
>
>     Makefile:286: recipe for target 'all-recursive' failed
>
>     make[1]: *** [all-recursive] Error 1
>
>     make[1]: Leaving directory '/home/xubuntu/Development/
> RTEMS/RTEMS_OS/build/powerpc-rtems4.11/c'
>
>     Makefile:410: recipe for target 'all-recursive' failed
>
>     make: *** [all-recursive] Error 1
>
>
>
> - Joey D.
>
>
> This message and any enclosures are intended only for the addressee.
> Please
> notify the sender by email if you are not the intended recipient. If you
> are
> not the intended recipient, you may not use, copy, disclose, or distribute
> this
> message or its contents or enclosures to any other person and any such
> actions
> may be unlawful. Ball reserves the right to monitor and review all
> messages
> and enclosures sent to or from this email address.
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20170123/35beced5/attachment-0002.html>