<div dir="ltr">AFAIK no one has ever booted RTEMS on a PC using the -kernel option.<div><br></div><div>Use the boot floppy in rtems-testing git repo and the pc386 script in</div><div>sim-scripts in that repo. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 7:40 PM, Saeed Ehteshamifar <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><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"><span style="font-size:12.8px">What qemu command are you using?</span></blockquote></span><div><b>-kernel </b></div><div>I haven't tried booting RTEMS via grub. How should I make a grub-bootable QEMU disk image? The process seems to be a bit tricky; I followed several guides on the Internet but none is working. Is there any guide on rtems wiki?<br></div><div><br></div><div>Update about kernel config options:</div><div>I tried configuring with <b>BSP_ENABLE_VGA=0 BSP_ENABLE_COM1_COM4=1 BSP_USE_COM1_AS_CONSOLE=1</b></div><div>and I got the following (still no output to stdio but booting source changes!):</div><div><img src="cid:ii_155517fb4bc49293" alt="Inline image 1" width="472" height="183"><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 7:50 PM, Joel Sherrill <span dir="ltr"><<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Chris might have broken this with his recent changes. But more likely....</div><div><br></div>What qemu command are you using?<br><br>I think Gedare's problem was that his grubmenu was not updated to this:<div><br></div><div><div>kernel= (hd0,0)/test.exe --console=/dev/com1</div></div><div><br></div><div>Before Chris' recent changes, the line would have read:</div><div><br></div><div><div>kernel= (hd0,0)/test.exe --console=com1</div></div><div><br></div><div>Notice the missing "/dev/" on --console. It greatly simplified the boot</div><div>argument parsing but requires boot args to be updated. </div><div><br></div><div>I asked for Gedare's opinion on another thread as to whether we need</div><div>to keep backwards compatibility but I don't think he has answered.</div><div><br></div><div>--joel</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Jun 14, 2016 at 11:22 AM, Saeed Ehteshamifar <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">I've just seen Gedare's problem with this also, which was unfortunately unsolved. :(</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 14, 2016 at 6:20 PM, Saeed Ehteshamifar <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>It seems that USE_COM1_AS_CONSOLE=1 is not effective for me. I'm configuring RTEMS with this option (bsp: pc386) and as a result, in my BSP install directory (specified by --prefix), I have:</div><div><b>./i386-rtems4.12/pc386/lib/include/bspopts.h:#define USE_COM1_AS_CONSOLE 1<br></b></div><div><b><br></b></div><div>However, when I run the hello example, nothing is output to the screen:</div><div><b>qemu-system-i386 -kernel $(find . -name hello.exe) -serial stdio -monitor null -nographic<br></b></div><div><b><br></b></div><div>Below is a screenshot of QEMU, which suggests that both Console and printk are using /dev/vgacons. Does this imply that the USE_COM... is taken as not effective?</div><div>And how should I correctly configure RTEMS to put the output to COM1 for pc386?</div><div><br></div><div><br></div><div><img src="cid:ii_1554fb0ba2dbaa31" alt="Inline image 1" width="454" height="262"><br></div><div><br></div><div>Thanks!</div><div><br></div><div>Best Regards,</div><div>Saeed</div></div>
</blockquote></div><br></div>
</div></div><br></div></div>_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org" target="_blank">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>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>