Chris, I would like to ask where should I put rtems-boot hd image needed to
run pc386 on qemu. Should I create some directory under rtems-tools and put
image into it?
2014-06-27 3:34 GMT+02:00 Gedare Bloom :
> On Thu, Jun 26, 2014 at 5:26 PM, Chris Johns wrote:
> > On 27/06/2014 4:09 am, Joel S
On Thu, Jun 26, 2014 at 5:26 PM, Chris Johns wrote:
> On 27/06/2014 4:09 am, Joel Sherrill wrote:
>>
>>
>> See pc386/configure.ac for this
>>
>> RTEMS_BSP_CLEANUP_OPTIONS(1, 1)
>>
>> dnlargument 1 indicates the default value for BSP_PRESS_KEY_FOR_RESET
>> dnlargument 2 indicates the defaul
On 27/06/2014 4:09 am, Joel Sherrill wrote:
See pc386/configure.ac for this
RTEMS_BSP_CLEANUP_OPTIONS(1, 1)
dnlargument 1 indicates the default value for BSP_PRESS_KEY_FOR_RESET
dnlargument 2 indicates the default value for BSP_RESET_BOARD_AT_EXIT
Sounds like the default should change
Gedare, thank you! This was it... I have wrong path to specified hello.exe
when invoking rtems-test... - to another build of rtems with another
config. Now, when pointing to proper rtems build, it is working!
2014-06-26 22:25 GMT+02:00 Gedare Bloom :
> Maybe the rtems-test is finding a differen
Maybe the rtems-test is finding a different version of the compiled hello.exe?
On Thu, Jun 26, 2014 at 4:02 PM, Krzysztof Mięsowicz
wrote:
> I had it configured with BSP_PRESS_KEY_FOR_RESET=0, but I will try it once
> again. It seems like a problem with execute module - when running qemu
> simply
I had it configured with BSP_PRESS_KEY_FOR_RESET=0, but I will try it once
again. It seems like a problem with execute module - when running qemu
simply from command line it works properly, only when running through
rtems-test it waits for key. Maybe Chris would know why this happens?
2014-06-26
On 6/26/2014 12:53 PM, Krzysztof Mięsowicz wrote:
> I checked this behaviour more, and it seems that when I run test
> through rtems-test command and it invokes this qemu-system-i386
> command through execute module, it waits after test completion for key
> press. When I'm starting qemu-system
I checked this behaviour more, and it seems that when I run test through
rtems-test command and it invokes this qemu-system-i386 command through
execute module, it waits after test completion for key press. When I'm
starting qemu-system-i386... simply from command line or through shell
script,
>
> Awesome! Does this work without the -hdb? Just curious what it is
> used for. If it can be avoided, then one less option and user setup
> requirement.
I suppose the answer is yes. Hdb is second hard drive where it looks for
grub.cfg file. When I will be sure about grub.cfg file content I wil
On 6/25/2014 5:48 PM, Chris Johns wrote:
> On 26/06/2014 5:56 am, Krzysztof Mięsowicz wrote:
>> Hi again and sorry for spam. Soon after writing mail to you I found the
>> solution (at least I think so :-D ).
> Thanks for posting the solution. The pc is the only qemu bsp I know of
> with a boot lo
On 26/06/2014 5:56 am, Krzysztof Mięsowicz wrote:
Hi again and sorry for spam. Soon after writing mail to you I found the
solution (at least I think so :-D ).
Thanks for posting the solution. The pc is the only qemu bsp I know of
with a boot loader making it more complex.
I created rtems-b
Hi again and sorry for spam. Soon after writing mail to you I found the
solution (at least I think so :-D ).
I created rtems-boot.img using script from
http://www.rtems.org/wiki/index.php/Building_Grub .
I wrote grub.cfg with following lines:
serial --unit=0 --speed=115200
set root='hd1,msdos1'
t
Hi,
I am currently working on rtems-test integration with qemu (especially
couverture-qemu) for pc386 BSP. Up to now pc386 used two approaches:
1. It used pc386_fda floppy image which boots test.exe from the same
directory
tree:
qemu/
hd/
pc386_fda
test.exe
install/
13 matches
Mail list logo
