I’ve been having problems with the IDE creating system images for a PC104
x86 board (TP400B) from DSP Design. I know that images can be created for
the board long hand (without using the IDE).
I have the IDE installed on my compaq laptop running under both Windows 2000
and Neutrino. I’ve tried both installations and both do the same thing.
I cannot mount the compact flash on the TP400B without errors being
returned. I have used the sample build files with IDE support for the basis
of these images, however on both installations the import seems incomplete
and needs work. After adding the missing files I get the messages:
sh: j_init: tcgetpgrp() failed. Inappropriate I/O control operation
sh: warning won’t have full job control.
I’ve had lots of problems with the IDE in terms of the organisation of files
within the images and it seems that unless the files are in /proc/boot
regardless of the PATH environment setting the image cannot access them.
If anyone has some ideas I would be very grateful as I’ve tried just about
everything during the last two weeks.
Any views or opinions expressed are solely those of the author and do not
necessarily
represent those of VT Group, its holding company or any of its subsidiaries
or associates.
I’ve been having problems with the IDE creating system images for a PC104
x86 board (TP400B) from DSP Design. I know that images can be created for
the board long hand (without using the IDE).
I have the IDE installed on my compaq laptop running under both Windows 2000
and Neutrino. I’ve tried both installations and both do the same thing.
I cannot mount the compact flash on the TP400B without errors being
returned. I have used the sample build files with IDE support for the basis
of these images, however on both installations the import seems incomplete
and needs work. After adding the missing files I get the messages:
What are these errors? Are they the ones below … these don’t
look like mount errors.
sh: j_init: tcgetpgrp() failed. Inappropriate I/O control operation
sh: warning won’t have full job control.
It sounds to me like you have mis-configured your sessions in the build
file (this particular error/warning message). Check and see if you did
a [+session] where you spawn the shell in the Boot Script tab/startup-script.
See the documentation for mkifs for more details on the available flags.
I’ve had lots of problems with the IDE in terms of the organisation of files
within the images and it seems that unless the files are in /proc/boot
regardless of the PATH environment setting the image cannot access them.
There are two locations for the PATH environment variable to be set (and
maybe many more). Proc PATH/Proc LD_LIBRARY_PATH is used for spawning
the executables in the Boot Script/Startup-script but the environment
that is inherited by the programs started in the startup-script can come
from the startup-script location (again refer to mkifs for more details).
If anyone has some ideas I would be very grateful as I’ve tried just about
everything during the last two weeks.
You can certainly post your generated build file (the one
fed to mkifs) and we can comment on it then.
I have resolved the shell error messages and thanks to other threads in
these newsgroups formatted and partitioned the compact flash correctly.
Much of my problem was due to a lack of understanding of what was required
in order to transfer the an image to compact flash. There is a whole in
this respect in the documentation, in that if your target system uses
compact flash and your host is windows then its not straight forward in
getting an image onto it.
My problems were compounded by the fact that although I also have a Neutrino
installation on my laptop and a PC-Card adapter for Compact Flash, my
PC-Card controller isn’t supported by Neutrino.
My final solution was to create two images, the first image boots the target
from floppy and preps the compact flash, also mounting the floppy device and
basic services. Then I insert another floppy with the actual image that I
transfer to the compact flash. During the development stages this is a
painful process and something which really needs addressing. I’ve been
looking for alternative PC104 CPU’s that don’t use Compact Flash, it seems
most manufacturers have moved towards compact flash.
There are lots of posts to these newsgroups that suggest Compact Flash is
not very reliable and not the best media to use. Any suggestions on a PC104
x86 CPU with a reasonably sized mass media device ? A hard disk is not an
option.
Any suggestions on a PC104
x86 CPU with a reasonably sized mass media device ? A hard disk is not an
option.
Thank you,
Simon.
WinSystems PPM-520 - AMD Elan SC520 133 MHz
Includes a Disk-On-Chip socket. See www.m-sys.com for available sizes (16 MB
to 1 GB). I’ve had no compatability issues.
4 serial ports. 10/100 Ethernet. Floppy/hard disk interface. Keyboard/mouse
ports.
Much of my problem was due to a lack of understanding of what was required
in order to transfer the an image to compact flash. There is a whole in
this respect in the documentation, in that if your target system uses
compact flash and your host is windows then its not straight forward in
getting an image onto it.
I’ll take a look at this as I revise the IDE docs.
Thanks for the feedback!
\
Doug Smith
Technical Publications
QNX Software Systems