Search an ifs for bootp

I’am testing bootp at the moment. When the client starts to download the
image it stops and tells me the file is not a valid image. Could someone
post a minimal .bld file that works with bootp or tell me if there is
something else I do wrong?

Thanks!

I guess the problem is that bootp expects the boot image to be either in TAGGED or ELF or a.out formats. The QNX mkifs utility creates a boot image that originally doesn’t correspond to any of them. To make your image compatible with bootp you have to wrap it properly. There are 2 ways to do it. The first one is to use proper filter inside of build file, but unfortunately I haven’t figured out how to do it. The second approach is to apply a filter after you create a boot image. For example, for x86 you do:

mkifsf_elf 3 0x3d0 image.ifs

Where 3 is ELF machine type for x86, the 0x3d0 is your boot image startup offset. To find the offset type dumpifs image.ifs and have a look at Startup-header line.
You have to apply the filter every time you rebuild your image.

I was told that in 6.2.1 all this can be done by mkifs.

Sincerely,

Serge


I’am testing bootp at the moment. When the client starts to download the
image it stops and tells me the file is not a valid image. Could someone
post a minimal .bld file that works with bootp or tell me if there is
something else I do wrong?

Thanks!

It works perfectly now using mkifsf_elf :slight_smile:. Thanks again. I have received
my Qnx 6.2.1 upgrade today so I’ll test if it is able to tag the image
itself…

“Serge Yuschenko” <nospam@forums.openqnx.com> a écrit dans le message de
news: 23939920.1049811772930.JavaMail.fliu@tiger…

I guess the problem is that bootp expects the boot image to be either in
TAGGED or ELF or a.out formats. The QNX mkifs utility creates a boot image

that originally doesn’t correspond to any of them. To make your image
compatible with bootp you have to wrap it properly. There are 2 ways to do
it. The first one is to use proper filter inside of build file, but
unfortunately I haven’t figured out how to do it. The second approach is to
apply a filter after you create a boot image. For example, for x86 you do:

mkifsf_elf 3 0x3d0 image.ifs

Where 3 is ELF machine type for x86, the 0x3d0 is your boot image startup
offset. To find the offset type dumpifs image.ifs and have a look at

Startup-header line.

You have to apply the filter every time you rebuild your image.

I was told that in 6.2.1 all this can be done by mkifs.

Sincerely,

Serge


I’am testing bootp at the moment. When the client starts to download
the
image it stops and tells me the file is not a valid image. Could
someone
post a minimal .bld file that works with bootp or tell me if there is
something else I do wrong?

Thanks!

It works perfectly now using mkifsf_elf > :slight_smile:> . Thanks again. I have received
my Qnx 6.2.1 upgrade today so I’ll test if it is able to tag the image
itself…

Note you can set this automatically by changing the virtual=x86,bios
to virtual=x86,elf in your build file.

\

cburgess@qnx.com

cburgess@qnx.com sed in <b716c8$c0a$2@nntp.qnx.com>:

Note you can set this automatically by changing the virtual=x86,bios
to virtual=x86,elf in your build file.

Does mkifsf_elf on 6.2.1 do the “right thing”?

mkifsf_elf in 6.1.0 didn’t have enough IPL things to
boot ex. over-16MB-memory machines.
(I’ve coded the loadifs 'cuz filter won’t suffice for ELFizing ifs)

kabe

I’m not aware of any changes to mkifsf_elf that would affect things like
this. What wasn’t working?

kabe@sra-tohoku.co.jp wrote:

cburgess@qnx.com > sed in <b716c8$c0a$> 2@nntp.qnx.com> >:

Note you can set this automatically by changing the virtual=x86,bios
to virtual=x86,elf in your build file.

Does mkifsf_elf on 6.2.1 do the “right thing”?

mkifsf_elf in 6.1.0 didn’t have enough IPL things to
boot ex. over-16MB-memory machines.
(I’ve coded the loadifs 'cuz filter won’t suffice for ELFizing ifs)

kabe


cburgess@qnx.com

Colin Burgess <cburgess@qnx.com> wrote:

I’m not aware of any changes to mkifsf_elf that would affect things like
this. What wasn’t working?

Sorry, I was wrong - apparently it was fixed…

kabe@sra-tohoku.co.jp > wrote:
cburgess@qnx.com > sed in <b716c8$c0a$> 2@nntp.qnx.com> >:

Note you can set this automatically by changing the virtual=x86,bios
to virtual=x86,elf in your build file.

Does mkifsf_elf on 6.2.1 do the “right thing”?

mkifsf_elf in 6.1.0 didn’t have enough IPL things to
boot ex. over-16MB-memory machines.
(I’ve coded the loadifs 'cuz filter won’t suffice for ELFizing ifs)

kabe


cburgess@qnx.com


cburgess@qnx.com