I would like to specify our proble.
We need to install QNX in 486 without CD driver. The PC has the following
parameters:
CPU Type: 80486DX2-S, Co-Processor: Installed
CPU Clock: 66 MHz Base Memory: 640 K
Extended Memory: 15360 K Cache Memory: 256 K
We only have Primary Master with LBA mode and have neither DMA, no PCI.
We have created a required image, "dinit"ed it into a floppy diskette and we
can boot our PC from the floppy. But we cannot boot from the PC. We used
different loaders, tried bios16m.boot instead of bios.boot, included
[image=1m] before our bootstrap, etc. Each time the PC started to boot
process, we saw lines
Boot Partition 1?1
Hit Esc for .altboot
then after 30 dots the PC went to reset.
When instead of bios.boot we include into our image nobios.boot, after 30
dots the PC became frosen (instead of resetting). So, the problem is in
bios.boot?
The universal utility bios.boot is used for 386, 486, Pentium with different
types of bios.
We tried to input some options to bios.boot and boot in *.bld file, but we
cannot create image. What should we do?
In QNX 4.25 boot utility has options -O (old bios!), -P, etc. What about
boot in RTP?
Does it understand “old” bios?
Please, help us. Serguei.
“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:9u3bus$kpl$1@inn.qnx.com…
I’m not from QSSL but I do not believe that this is a loader problem. It
sounds to me like the loader did it’s thing. It sounds to me like your
build image has a problem. But I will be very interested to see what
solves
this problem.
I have an embedded system with problems of rebooting itself. But it does
get much further along and it doesn’t always reset at the exact same
place.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“Serguei Lapine” <> slapine@mitectelecom.com> > wrote in message
news:9u3afv$jve$> 1@inn.qnx.com> …
Hello Joe,
Of cause, we have read all the articles from the site you gave us. It
helped
to understand the booting process better, but it does not resolve our
problem.
When we use the default loader, we can see lines
Boot Partition 1?1
Hit Esc for .altboot
then about 20-30 dots and the PC goes to reset;
when we use another loaders (ipl-diskpc2-flop, etc), we cannot see the
second line, as
after Boot Partition 1?1
we got a new screen with message PRESS A KEY TO REBOOT.
We have changed our 486 for Pentium, booted it from floppy drive with
our
QNX image, erased all the previous partitions, created QNX partition for
all
HD, mounted it, copied our image as .boot and PC became rebootable - no
problem.
We returned to our 486, repeated the same procedure, but we failed
again:
the same 20-30 dots (when we booted from the floppy, we saw about 60
dots
before the information from startup-bios appeared - we used the verbous
option) and then restart. Does it mean that it fails during work of
bios.boot?
We looked through a pile of documents, used some proposals (for example,
we
removed compression option, used all available loaders: ipl-diskpc1,
ipl-diskpc1-flop, ipl-diskpc2, ipl-diskpc2-flop, tried to use
bios16m.boot
instead of bios.boot, added line
[image=1m]
before
[virtual=x86,bios + compress] boot={
etc.) but the result was the same.
In a case I give you parameters of our PC:
CPU Type: 80486DX2-S, Co-Processor: Installed
CPU Clock: 66 MHz Base Memory: 640 K
Extended Memory: 15360 K Cache Memory: 256 K
Please, help us. Serguei.
“Hardware Support Account” <> hw@qnx.com> > wrote in message
news:9tj6q8$a76$> 1@nntp.qnx.com> …
Hi,
When you are trying to boot your system, at what point does it fail?
Have you look at the Embedding SDK docs?
http://qdn.qnx.com/support/docs/embedding_sdk_en/index.html
Regards,
Joe
Serguei Lapine <> slapine@mitectelecom.com> > wrote:
We have a problem - we cannot make our target (x86) bootable.
We have to run some ATE application developed in PhAB in a PC with
486
processor, 16 MB operation memory and 520 MB in HD. Our bios does
not
allow to use CD.
We created a build file, created ifs-image using mkifs, created
bottable
floppy
diskette using dinit. We can boot from the floppy, we can copy all
required
files from /proc/boot to our HD, but we cannot reboot from the HD.
We tried different methods: we use different images, we copied them
in
.boot
or .altboot, we changed loaders (pc1, pc2, pc2-flop), we used
different
options
in dinit and fdisk. No luck…
Of course, we looked through a hugh pile of QNX’s documents and
could
not
find a right answer. It is very strange: the QNX should use in
embedded
systems
but the company did not describe clearly how to make the simplest
embedded
system bootable!
In a case I apply here the main parts of two our *.bld files.
File1:
[search=/bin:/sbin:/lib:/lib/dll:/boot/sys:/usr/bin:/usr/lib:/usr/sbin:/usr/
photon/bin:.]
[virtual=x86,bios +compress] .bootstrap = {
startup-bios
PATH=/proc/boot:/bin:/usr/photon/bin
LD_LIBRARY_PATH=proc/boot:/usr/lib:/lib procnto
PATH=/proc/boot procnto
}
[+script] .script = {
seedres
devc-con -e -n4 &
reopen /dev/con1
devb-eide &
devb-fdc &
devc-pty &
[+session] esh &
}
[type=link] /tmp=/dev/shmem
[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so
[type=link] /usr/lib/libcam.so.2=/proc/boot/libcam.so
libc.so
libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so
devc-con
devb-eide
devb-fdc
devc-par
devc-pty
and etc.
We can boot from the floppy, among /dev we have hd0 with a raw
partition
with > the copied files .boot, .inodes, etc.
File2:
Everything is the same, but instead of
devb-eide &
we use
devb-eide automount=hd0t77:/ &
waitfor /dev 10
In such a case in /dev we have hd0 with a raw partition and copied
files
.boot, etc. and hd0t77 with 2 partitions (both NonQNX). We tried dd
removing
non QNX partition, then created QNX bootable partition using fdisk
or
created QNX partition using dinid -h /dev/hdot77 (sometimes with
some
additional
parameters), but resilt was the same. We could not boot from the
target.
Please, help us. Serguei Lapine, e-mail:
slapine@mitectelecom.com
[/quote]
>