<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 26, 2016 at 4:11 PM, Matthew Clark <span dir="ltr"><<a href="mailto:linux.matthew@gmail.com" target="_blank">linux.matthew@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">I've successfully built/run the sparc sim (sis) test examples as described in <div><br></div><div><a href="https://devel.rtems.org/wiki/TBR/UserManual/Quick_Start" target="_blank">https://devel.rtems.org/wiki/TBR/UserManual/Quick_Start</a><br></div><div><br></div></div></blockquote><div><br></div><div>Good job! But you now have learned one of the reasons we use sis in the Quick Start. </div><div>sis is the easiest simulator to actually use. :)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>My target hardware is a Zedboard, Raspberry Pi2 and a basic ML405 (Virtex4), but when I try to re-create the above for the various bsps, including supposed qemu plaftorms like qemuppc, I get all manner of errors, such as</div><div><br></div><div><div>$powerpc-rtems4.11-run ./qemuppc/testsuites/samples/hello/hello.exe</div><div>./qemuppc/testsuites/samples/hello/hello.exe: Caught signal 11 at address 0xffc00014<br></div></div><div><br></div></div></blockquote><div><br></div><div>qemuppc is a PowerPC BSP that runs on the qemu simulator.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>I get nothing for ARM:</div><div><br></div><div>$arm-rtems4.11-run ./xilinx_zynq_a9_qemu/testsuites/samples/hello/hello.exe<br></div><div>$</div><div><br></div></div></blockquote><div><br></div><div>The ARM simulator in gdb does not know how to run this. Qemu is the simulator</div><div>for the xilinx_zynq_a9_qemu BSP.</div><div><br></div><div>You will need to build qemu with the RSB and install it.</div><div><br></div><div>Then there are some easy to use helper scripts in the rtems-testing/sim-scripts</div><div>directory named after the BSP they are invoking a simulator to simulate. So</div><div>you would invoke it as:</div><div><br></div><div>xilinx_zynq_a9_qemu -i hello.exe<br></div><div><br></div><div>-i indicates interactive mode. By default it runs all .exe files on the command</div><div>line with output logged to files.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>though if I tried to run the hello.exe through ARM's GDB, I get a different error:</div><div><br></div><div><div>$ arm-rtems4.11-gdb ./xilinx_zynq_a9_qemu/testsuites/samples/hello/hello.exe</div><div>GNU gdb (GDB) 7.9</div><div>...</div><div>This GDB was configured as "--host=x86_64-linux-gnu --target=arm-rtems4.11".Type "show configuration" for configuration details.</div><div>...</div><div>Reading symbols from ./xilinx_zynq_a9_qemu/testsuites/samples/hello/hello.exe... done.<br></div><div>(gdb) tar sim</div><div>Connected to the simulator.</div><div>(gdb) load </div><div>Loading section .start, size 0x6d8 vma 0x0</div><div>Loading section .text, size 0x2071c vma 0x700</div><div>Loading section .init, size 0xc vma 0x20e1c</div><div>Loading section .fini, size 0xc vma 0x20e28</div><div>Loading section .rodata, size 0x1150 vma 0x20e38</div><div>Loading section .ARM.exidx, size 0x8 vma 0x21f88</div><div>Loading section .eh_frame, size 0x74 vma 0x21f90</div><div>Loading section .init_array, size 0x4 vma 0x22004</div><div>Loading section .fini_array, size 0x4 vma 0x22008</div><div>Loading section .jcr, size 0x4 vma 0x2200c</div><div>Loading section .data, size 0x6d0 vma 0x101400</div><div>Start address 0x40</div><div>Transfer rate: 1127840 bits in <1 sec.</div><div>(gdb) r</div><div>Starting program: xilinx_zynq_a9_qemu/testsuites/samples/hello/hello.exe </div><div>[Inferior 1 (process 42000) exited with code 060]</div></div><div><br></div></div></blockquote><div><br></div><div>Same situation. The run and gdb commands are from the gdb source tree</div><div>and are the same simulator under the hood.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div></div><div>I don't always have access to the target hardware and I wanted to run simple tests in a simulator environment. Am I doing something wrong? If so, what? </div><div><br></div><div>Thanks,</div><div><br></div><div>Matt</div></div>
<br>_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br></blockquote></div><br></div></div>