DiskOnChip booting problems with rtp

Hi

I’ve been using neutrino 2.0 (developing under codewarrior on win95) for a
while now running on my target machine which is a PC/104 486 card with an
8meg DOC. I’ve used fdisk and dinit for partitioning and creating a qnx4
file system and copied my boot image to /doc/.boot

Fine - all worked fine and dandy.

I’ve now changed my development platform to RTP and tweaked my image
buildfile accordingly. I can run the diskonchip driver fine, fdisk ( set
loader and boot etc), dinit etc - I’ve even got qnet running for
transferring all my files over to the mounted filesystem.

One problem - i’ve got my new image file copied over to doc/.boot , power
cycle the board and… nothing

It looks like the bootloader is failing somewhere - I get a BIOS message
‘Booting Operating System…’ and a flashing cursor and thats it. I know the
boot image is ok as it boots from it when on floppy. I don’t even get the
‘Press Esc for alternate OS…’ message so its getting stuck b4 that.

Is there something I’m missing, has there been a major change in fdisk
between Neutrino2.0 and RTP? Its the only thing I can think of really thats
different.

Any clues anyone?

Regards

Jim

Whats the size of the boot image?

Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
{ Hi
{
{ I’ve been using neutrino 2.0 (developing under codewarrior on win95) for a
{ while now running on my target machine which is a PC/104 486 card with an
{ 8meg DOC. I’ve used fdisk and dinit for partitioning and creating a qnx4
{ file system and copied my boot image to /doc/.boot
{
{ Fine - all worked fine and dandy.
{
{ I’ve now changed my development platform to RTP and tweaked my image
{ buildfile accordingly. I can run the diskonchip driver fine, fdisk ( set
{ loader and boot etc), dinit etc - I’ve even got qnet running for
{ transferring all my files over to the mounted filesystem.
{
{ One problem - i’ve got my new image file copied over to doc/.boot , power
{ cycle the board and… nothing
{
{ It looks like the bootloader is failing somewhere - I get a BIOS message
{ ‘Booting Operating System…’ and a flashing cursor and thats it. I know the
{ boot image is ok as it boots from it when on floppy. I don’t even get the
{ ‘Press Esc for alternate OS…’ message so its getting stuck b4 that.
{
{ Is there something I’m missing, has there been a major change in fdisk
{ between Neutrino2.0 and RTP? Its the only thing I can think of really thats
{ different.
{
{ Any clues anyone?
{
{ Regards
{
{ Jim
{
{
{


Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

Basically the situation now is that I’ve used one of my old neutrino 2.0
boot images (on floppy) which just has fdisk/dinit on and i’ve run both of
these on the device so that i have an empty qnx4 filesystem as built by
neutrino 2.0.

I’ve then used my boot image created on RTP to get qnet running and copied
all the required libraries/binaries to the mounted filesystem on the
diskonchip. Finally copied the RTP created boot image to /diskonchip/.boot
and it boots.

Looks like something fishy between neutrino 2.0 and RTP versions of
fdisk/dinit maybe??

600568 - I don’t think its a memory problem - i dont think its getting as
far as trying to boot from my image…


Pat Ford wrote in message …

Whats the size of the boot image?

Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
{ Hi
{
{ I’ve been using neutrino 2.0 (developing under codewarrior on win95) for a
{ while now running on my target machine which is a PC/104 486 card with an
{ 8meg DOC. I’ve used fdisk and dinit for partitioning and creating a qnx4
{ file system and copied my boot image to /doc/.boot
{
{ Fine - all worked fine and dandy.
{
{ I’ve now changed my development platform to RTP and tweaked my image
{ buildfile accordingly. I can run the diskonchip driver fine, fdisk ( set
{ loader and boot etc), dinit etc - I’ve even got qnet running for
{ transferring all my files over to the mounted filesystem.
{
{ One problem - i’ve got my new image file copied over to doc/.boot , power
{ cycle the board and… nothing
{
{ It looks like the bootloader is failing somewhere - I get a BIOS message
{ ‘Booting Operating System…’ and a flashing cursor and thats it. I know the
{ boot image is ok as it boots from it when on floppy. I don’t even get the
{ ‘Press Esc for alternate OS…’ message so its getting stuck b4 that.
{
{ Is there something I’m missing, has there been a major change in fdisk
{ between Neutrino2.0 and RTP? Its the only thing I can think of really thats
{ different.
{
{ Any clues anyone?
{
{ Regards
{
{ Jim
{
{
{


Pat Ford email: > pford@qnx.com
QNX Software Systems, Ltd. WWW: > http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8

Just wanted to check the obvious things first, can you bring a Qnx 4.25 session up and do the dinit/format thing there?

Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
{ 600568 - I don’t think its a memory problem - i dont think its getting as
{ far as trying to boot from my image…
{
{
{ Pat Ford wrote in message …
{ > Whats the size of the boot image?
{ >
{ >Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
{ >{ Hi
{ >{
{ >{ I’ve been using neutrino 2.0 (developing under codewarrior on win95) for a
{ >{ while now running on my target machine which is a PC/104 486 card with an
{ >{ 8meg DOC. I’ve used fdisk and dinit for partitioning and creating a qnx4
{ >{ file system and copied my boot image to /doc/.boot
{ >{
{ >{ Fine - all worked fine and dandy.
{ >{
{ >{ I’ve now changed my development platform to RTP and tweaked my image
{ >{ buildfile accordingly. I can run the diskonchip driver fine, fdisk ( set
{ >{ loader and boot etc), dinit etc - I’ve even got qnet running for
{ >{ transferring all my files over to the mounted filesystem.
{ >{
{ >{ One problem - i’ve got my new image file copied over to doc/.boot , power
{ >{ cycle the board and… nothing
{ >{
{ >{ It looks like the bootloader is failing somewhere - I get a BIOS message
{ >{ ‘Booting Operating System…’ and a flashing cursor and thats it. I know the
{ >{ boot image is ok as it boots from it when on floppy. I don’t even get the
{ >{ ‘Press Esc for alternate OS…’ message so its getting stuck b4 that.
{ >{
{ >{ Is there something I’m missing, has there been a major change in fdisk
{ >{ between Neutrino2.0 and RTP? Its the only thing I can think of really thats
{ >{ different.
{ >{
{ >{ Any clues anyone?
{ >{
{ >{ Regards
{ >{
{ >{ Jim
{ >{
{ >{
{ >{
{ >
{ >–
{ >Pat Ford email: pford@qnx.com
{ >QNX Software Systems, Ltd. WWW: http://www.qnx.com
{ >(613) 591-0931 (voice) mail: 175 Terence Matthews
{ >(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
{ >
{
{
{
{


Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8