On Tue, 10 Jul 2001 09:48:43 GMT, > ako@box43.gnet.pl > (Andrzej Kocon)
wrote:
On Mon, 09 Jul 2001 11:45:48 +0200, Arve Slenes <> arve@datarespons.no
wrote:
I’m using ver. 6.0 at the moment.
esh is an “embedded shell”.
I know, it was the “&”, i.e., what is the point of starting
esh in background?
A question: Could it be something with PCI vs. ISA drivers, and which
is selected as default?? Is there a difference in the default driver
selected in
ver. 4.2x and 6.0??
Apparently your build script does not contain pci-bios nor any
calls that make use of it (e.g., diskboot), and the problem does not
seem to be driver-related. From the symptoms I would conclude that the
booting fails at a very early stage (decompression or right after)
simply due to the lack of memory, otherwise you would see some
messages from startup-bios (-vvvv). The first memory constraint (<640K
for the compressed image) is met, but I don’t know what is the minimum
for a “bare” image to decompress and start. You could try to indicate
smaller and smaller amounts of memory in the -m parameter of the
startup-bios when booting on a regular PC (keep a separate booting
diskette with no limit set).
OK, as you have perhaps discovered already, by default the
image links at 4M, so you simply can’t boot with 4M, unless you
specify an [image=…] attribute in the image definition, or in the -l
parameter of mkifs (see the doc for the mkifs utility). Now with
[image=1m] I can boot within 4M…
ako
ako
Andrzej Kocon wrote:
On Thu, 05 Jul 2001 11:28:41 +0200, Arve Slenes <> arve@datarespons.no
wrote:
Is it 6.0 or 6.1? I didn’t succeed in booting 6.0 “small”
images with 4 MB (386SX, 486DX). It may be different with 6.1, as the
image is supposed to release some memory no longer needed.
Have you tried without rtc? (What does “esh &” do?)
I recall rebooting happens on PIV systems, and that “some
BIOSes don’t leave the keyboard controller in a properly reset state,
and devc-con will then cause a reboot” (“Boot problem on AMD Elan
SC400 Evaluation Board” on .installation, Jun 27), but these are not
relevant here…
ako
On a regular x86 PC my floppy bootdisk starts up and boot, but…
…when I try to boot the same disk on my single board computer it
resets the board
when showing “Press ESC for alternate OS
…”
What could be the various reasons for this?? Is it again the image size
limit (the current compressed size is around 300k)?? Or is it something
else…
It seems like the system reboots before even startup-bios starts
running.
The build file I used is shown below, and the SBC i used is a PCM-SX
board from WinSystems. With a memory of 4 Megabytes that is…
Here is a link to the datasheet for the board:
http://www.winsystems.com/products/sbcs/pcmsx.htm
Build file used:
start of file
[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys]
[virtual=x86,bios +compress] boot = {
startup-bios -vvvv
PATH=/proc/boot:/bin:/usr/bin procnto -h -vvv
}
[+script] .script = {
devc-ser8250 -e -b9600 &
reopen
display_msg This is a litle boot test for QNX.6
[+session] PATH=/proc/boot esh &
rtc hw &
}
[type=link] /dev/console=/dev/ser2
libc.so
[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so
fs-dos.so
[data=copy]
devc-ser8250
esh
echo
ls
cat
cp
rtc
end of file
Regards.
-Arve
\