Porting from an Executive Loop

QNX Newsgroups (Archives) qdn.public.porting
1

Is it realistic to talk of “porting” a system which ran in an executive loop
to a QNX platform? We have outgrown our current controller (Intel 80C196)
and are thinking of making the leap to a real-time operating system, but
there is some concern that not only do we need to learn QNX, but that the
entire software must be re-invented from the ground up. Are there any tools
or techniques on how to do this?
Thanks,
Elise

2

Depending on the requirement of the program you could just
“port” it as his and run it a low priority. If the machine isn’t expected
to
run anything else it might not be a problem. This isn’t
the best solution but I could be a first step for you.

If you lean toward real-time operation system that means
in the long run you should build your software accordingly,
otherwise stick to DOS :wink:

There is no simple technic to turn an polling process into a real-time
friendly one. There are guide lines but I would got as far as
call it a technic :wink:

In most cases the program doesn’t need to be rewritten from
the ground-up. I all depends on what the program does.

If you want more detail information, give more details about
your program.

Is it realistic to talk of “porting” a system which ran in an executive
loop
to a QNX platform? We have outgrown our current controller (Intel 80C196)
and are thinking of making the leap to a real-time operating system, but
there is some concern that not only do we need to learn QNX, but that the
entire software must be re-invented from the ground up. Are there any
tools
or techniques on how to do this?
Thanks,
Elise

3

I agree with everything that Mario says here. I would
suggest the following course of action.

  1. Setup QNX and become familiar with it. Try some
    simple message passing programs.

  2. Design, Design, Design.
    This is the hard part. Figure out how you should
    redesign your product. Then review it, get a second
    opinion, and review it again.

  3. Port,
    At this point, a lot of your previous code may be
    dropped into your new modules.




    Previously, Mario Charest wrote in qdn.public.porting:

Depending on the requirement of the program you could just
“port” it as his and run it a low priority. If the machine isn’t expected
to
run anything else it might not be a problem. This isn’t
the best solution but I could be a first step for you.

If you lean toward real-time operation system that means
in the long run you should build your software accordingly,
otherwise stick to DOS > :wink:

There is no simple technic to turn an polling process into a real-time
friendly one. There are guide lines but I would got as far as
call it a technic > :wink:

In most cases the program doesn’t need to be rewritten from
the ground-up. I all depends on what the program does.

If you want more detail information, give more details about
your program.

  • Mario


    “E. Adams” <> elise.adams@rflelect.com> > wrote in message
    news:90lna7$5me$> 1@inn.qnx.com> …
    Is it realistic to talk of “porting” a system which ran in an executive
    loop
    to a QNX platform? We have outgrown our current controller (Intel 80C196)
    and are thinking of making the leap to a real-time operating system, but
    there is some concern that not only do we need to learn QNX, but that the
    entire software must be re-invented from the ground up. Are there any
    tools
    or techniques on how to do this?
    Thanks,
    Elise



    \

–
Mitchell Schoenbrun --------- maschoen@pobox.com