Image VS Sysinit

QNX Newsgroups (Archives) qdn.public.qnxrtp.embedded
1

Hello All,

I’m having a hard time deciding where to start up services, drivers,
daemons, processes…
Currently, I start drivers in my .boot and daemons and processes in my
sysinit or rc.sysinit…
I’m using PC104 with DOC(DiskOnChip2000)

Opinions would be most appreciated…

If possible, please send replies to brendan@storagequest.com

Thanks,
Brendan

2

Hi,

Make an image that boots the core devices like:

  • devb-doc
  • devc-con
  • slogger
    Use the DOC example buildfile as an guideline.

At the end of the buildfile, you call: sh -c"
/etc/system/sysinit.yourtarget"
there you boot the rest.

This is the way I do it with 48Mb DOC



“Brendan Lelieveld-Amiro” <brendan@storagequest.com> wrote in message
news:anfg93$mht$1@inn.qnx.com…

Hello All,

I’m having a hard time deciding where to start up services, drivers,
daemons, processes…
Currently, I start drivers in my .boot and daemons and processes in my
sysinit or rc.sysinit…
I’m using PC104 with DOC(DiskOnChip2000)

Opinions would be most appreciated…

If possible, please send replies to > brendan@storagequest.com

Thanks,
Brendan

3

Thanks for your help.

I am using the DOC 192Mb, What would be a good place to start up
io-net, netmanager, and inetd.?

Thanks again,
Brendan

“fmartens-2000” <fmartens-2000@planet.nl> wrote in message
news:angopr$ilf$1@inn.qnx.com…

Hi,

Make an image that boots the core devices like:

  • devb-doc
  • devc-con
  • slogger
    Use the DOC example buildfile as an guideline.

At the end of the buildfile, you call: sh -c"
/etc/system/sysinit.yourtarget"
there you boot the rest.

This is the way I do it with 48Mb DOC



“Brendan Lelieveld-Amiro” <> brendan@storagequest.com> > wrote in message
news:anfg93$mht$> 1@inn.qnx.com> …
Hello All,

I’m having a hard time deciding where to start up services, drivers,
daemons, processes…
Currently, I start drivers in my .boot and daemons and processes in my
sysinit or rc.sysinit…
I’m using PC104 with DOC(DiskOnChip2000)

Opinions would be most appreciated…

If possible, please send replies to > brendan@storagequest.com

Thanks,
Brendan
\

4

sysinit

“Brendan Lelieveld-Amiro” <brendan@storagequest.com> wrote in message
news:anhpoq$d58$1@inn.qnx.com…

Thanks for your help.

I am using the DOC 192Mb, What would be a good place to start up
io-net, netmanager, and inetd.?

Thanks again,
Brendan

“fmartens-2000” <> fmartens-2000@planet.nl> > wrote in message
news:angopr$ilf$> 1@inn.qnx.com> …
Hi,

Make an image that boots the core devices like:

  • devb-doc
  • devc-con
  • slogger
    Use the DOC example buildfile as an guideline.

At the end of the buildfile, you call: sh -c"
/etc/system/sysinit.yourtarget"
there you boot the rest.

This is the way I do it with 48Mb DOC



“Brendan Lelieveld-Amiro” <> brendan@storagequest.com> > wrote in message
news:anfg93$mht$> 1@inn.qnx.com> …
Hello All,

I’m having a hard time deciding where to start up services, drivers,
daemons, processes…
Currently, I start drivers in my .boot and daemons and processes in my
sysinit or rc.sysinit…
I’m using PC104 with DOC(DiskOnChip2000)

Opinions would be most appreciated…

If possible, please send replies to > brendan@storagequest.com

Thanks,
Brendan


\

5

Hi…

This is what I do. You should modify and optimize to adapt to your
resources and needs. If you find problems, post them, and someone will
help. NOTE that you will need the beta driver from the DOC web page, and
that their explanations on how to do things supersedes any thing that I
say here. Go to:

http://www.m-sys.com/content/download/OSSupport2.asp?id=7&pid=

(Please notice that you will have to modify a few things (I do not know
which) to make it work in your system/environment).

  1. you have the choice of hooking a hd to your pc104 or a floppy disk.

a. if a floppy disk (assume that you have a qnx ready floppy as per the
docs):

i. mount the floppy:
mount -tqnx4 /dev/fd0 /fs/fd0

ii. modify fd.doc_no_root.tcp.build to reflect your environment such as
the presence of pci bus, devn-* and tcp/ip address, etc…

iii. make the image

mkifs -vv fd.doc_no_root.tcp.build fd.doc_no_root.tcp.ifs

iv. cp fd.doc_no_root.tcp.ifs /fs/fd0/.boot

v. boot from the floppy, you should find the diskOnChip as /doc, and
also you should be able to ftp and telnet to other systems from the pc104.

vi. go to 2.

b. a faster way is to hook an ide hd to your pc104, in which case you
have everything in your hd now. In this case, you have to be careful
when starting the doc driver since it will most probably have to be
device 1 instead of 0. You would start the driver as:


devb-doc doc addr=0xd4000 verbose blk automount=/dev/hd1t77:/doc &
^~

and the diskOnChip would be /doc

  1. modify and ten run the file get.rtp62.doc as:

./get.rtp62.doc ms 10.04.2002

this will generate a file system. Copy this file system onto your
diskOnChip.

  1. generate the images for your doc. You’ll find examples everywhere,
    and two more here. Copy the images to your doc. I usually do:

mkifs -vv doc.all.build doc.all.ifs
mkifs -vv doc.tcp.build doc.tcp.ifs

cp doc.all.ifs /doc/.altboot
cp doc.tcp.ifs /doc/.boot

and you should be good to go.

  1. I can not emphasize enough that you should pay attention to details
    such as which is the device number (depends on whether you have a hd or
    not hooked to your pc104), tcp address, network device driver, io-net
    name, etc.

regards…

Miguel.




Brendan Lelieveld-Amiro wrote:

Hello All,

I’m having a hard time deciding where to start up services, drivers,
daemons, processes…
Currently, I start drivers in my .boot and daemons and processes in my
sysinit or rc.sysinit…
I’m using PC104 with DOC(DiskOnChip2000)

Opinions would be most appreciated…

If possible, please send replies to > brendan@storagequest.com

Thanks,
Brendan