6.2.1b release

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the released
    version because
    this worked with the beta.

  2. Flash file systems are mounted, but they are not doing the
    decompression on the
    fly. The .cmp directory/mountpoints are not present. When I
    create non-compressed
    filesystems they work fine. I was not able to get this to work with
    the beta version
    either. I’ve tried to turn on the compression flag via the flashctl
    tool, but that
    doesn’t work either.

Any suggestions would be greatly appreciated.

Chris Fischer wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the released
    version because
    this worked with the beta.

Can you please post your build file where you start the driver.

  1. Flash file systems are mounted, but they are not doing the
    decompression on the
    fly. The .cmp directory/mountpoints are not present. When I
    create non-compressed
    filesystems they work fine. I was not able to get this to work with
    the beta version
    either. I’ve tried to turn on the compression flag via the flashctl
    tool, but that
    doesn’t work either.

If you run the flash driver with the -V option, do you get any output?
If so, then you are running the new flash filesystem which does not have
integrated compression. You will have to use inflator/deflator.

-Jay.

Any suggestions would be greatly appreciated.

Chris Fischer wrote:

“Jay Greig” <> greig@qnx.com> > wrote in message
news:brsihq$hss$> 1@nntp.qnx.com> …


Chris Fischer wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

released

version because
this worked with the beta.

Can you please post your build file where you start the driver.


Here’s the part of the build file:

Can you please post your whole buildfile so that we can try to reproduce
this here using your exact setup.

Network driver

Setup Best Comm (DMA) for on-board ethernet driver

display_msg Starting Bestcomm DMA driver

bestcomm5200

display_msg Starting up on-board ethernet with Large stack and cache -
144.177.209.210

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

display_msg after ionet

waitfor /dev/io-net/en0 4

ifconfig en0 147.177.209.210 netmask 255.255.240.0

display_msg after ifconfig

route add default 147.177.208.1



2. Flash file systems are mounted, but they are not doing the
decompression on the
fly. The .cmp directory/mountpoints are not present. When I
create non-compressed
filesystems they work fine. I was not able to get this to work

with

the beta version
either. I’ve tried to turn on the compression flag via the

flashctl

tool, but that
doesn’t work either.

If you run the flash driver with the -V option, do you get any output?
If so, then you are running the new flash filesystem which does not have
integrated compression. You will have to use inflator/deflator.


With -V I get a:
F3S_VER=3 MTD_VER=2

So, does that mean compression won’t work?
I tried building an efs with FFS2, but that didn’t help.

If you have the source for the flash driver, you should be able to do
the following to get the old flash filesystem (if you really want it):

cd [bsp_root]/src/hardware/flash/boards/[driver]
make clean
make F3S_VER=2 MTD_VER=1 install

-Jay.

Thanks.


-Jay.


Any suggestions would be greatly appreciated.

\

I believe that you may have a case of versionitis between the beta BSP
and the GA version.

The serial driver in the released version should be attaching to
interrupt 65, while your environment shows it to be attached to 0x21 (33).

From what Dave said, the network driver and the startup from the
released package need to go hand-in-hand.

What host system are you developing from (RTP, Windows)? Try installing
the released package on a clean system (as to not blow away your current
working environment) and see if that clears up this problem.

-Jay.

Chris Fischer wrote:

“Dave Green” <> dgreen@qnx.com> > wrote in message
news:brt3oi$5n1$> 1@nntp.qnx.com> …

Chris Fischer <> cfischer@harris.com> > wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.


That makes sense. I’ve tried with the drivers from the beta
version (i.e. devn-ethernet-lite5200evb) and they work fine.


After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.


Here’s the output when I start the net:

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

unable to init dll devn-mpc5200: Function not implemented

Here’s the pidin ir:

pid tid name
1 1 procnto
0 0x80000000 0 — @0x505d8:0x0
1 2 procnto
1 3 procnto
1 4 procnto
1 5 procnto
1 6 procnto
1 7 procnto
1 8 procnto
1 9 procnto
1 10 procnto
2 1 c-uart-lite5200evb
2 2 c-uart-lite5200evb
1 0x21 45836 — =INTR
3 1 proc/boot/slogger
3 2 proc/boot/slogger
4 1 proc/boot/pipe
4 2 proc/boot/pipe
4 3 proc/boot/pipe
5 1 ppc/be/pci-mgt5200
6 1 pc/be/devf-mgt5200
6 2 pc/be/devf-mgt5200
6 3 pc/be/devf-mgt5200
4103 1 proc/boot/ksh
4104 1 proc/boot/io-net
4104 2 proc/boot/io-net
4104 3 proc/boot/io-net
4104 4 proc/boot/io-net
4104 5 proc/boot/io-net
32777 1 proc/boot/pidin

TIA.

\

David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com

“Jay Greig” <greig@qnx.com> wrote in message
news:brsihq$hss$1@nntp.qnx.com

Chris Fischer wrote:
I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the
    released
    version because
    this worked with the beta.

Can you please post your build file where you start the driver.

Here’s the part of the build file:

Network driver

Setup Best Comm (DMA) for on-board ethernet driver

display_msg Starting Bestcomm DMA driver

bestcomm5200

display_msg Starting up on-board ethernet with Large stack and cache -
144.177.209.210

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

display_msg after ionet

waitfor /dev/io-net/en0 4

ifconfig en0 147.177.209.210 netmask 255.255.240.0

display_msg after ifconfig

route add default 147.177.208.1

  1. Flash file systems are mounted, but they are not doing the
    decompression on the
    fly. The .cmp directory/mountpoints are not present. When I
    create non-compressed
    filesystems they work fine. I was not able to get this to work
    with
    the beta version
    either. I’ve tried to turn on the compression flag via the
    flashctl
    tool, but that
    doesn’t work either.

If you run the flash driver with the -V option, do you get any output?
If so, then you are running the new flash filesystem which does not have
integrated compression. You will have to use inflator/deflator.

With -V I get a:
F3S_VER=3 MTD_VER=2

So, does that mean compression won’t work?
I tried building an efs with FFS2, but that didn’t help.

Thanks.

-Jay.


Any suggestions would be greatly appreciated.

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

released

version because
this worked with the beta.

Can you please post your build file where you start the driver.


Here’s the part of the build file:

Can you please post your whole buildfile so that we can try to reproduce
this here using your exact setup.

I’ve appended the complete buildfile to the bottom of this message

Network driver

Setup Best Comm (DMA) for on-board ethernet driver

display_msg Starting Bestcomm DMA driver

bestcomm5200

display_msg Starting up on-board ethernet with Large stack and cache -
144.177.209.210

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

display_msg after ionet

waitfor /dev/io-net/en0 4

ifconfig en0 147.177.209.210 netmask 255.255.240.0

display_msg after ifconfig

route add default 147.177.208.1



2. Flash file systems are mounted, but they are not doing the
decompression on the
fly. The .cmp directory/mountpoints are not present. When I
create non-compressed
filesystems they work fine. I was not able to get this to work

with

the beta version
either. I’ve tried to turn on the compression flag via the

flashctl

tool, but that
doesn’t work either.

If you run the flash driver with the -V option, do you get any output?
If so, then you are running the new flash filesystem which does not have
integrated compression. You will have to use inflator/deflator.


With -V I get a:
F3S_VER=3 MTD_VER=2

So, does that mean compression won’t work?
I tried building an efs with FFS2, but that didn’t help.

If you have the source for the flash driver, you should be able to do
the following to get the old flash filesystem (if you really want it):

cd [bsp_root]/src/hardware/flash/boards/[driver]
make clean
make F3S_VER=2 MTD_VER=1 install

I made it with this, rebuild the ifs. It did not work, I am wondering
if I have to rebuild my efs filesystems as FFS2 filesystems?

(I am also wondering if FFS2/FFS3 is the issue, or is it something
more subtle?).

-Jay.


Thanks.


-Jay.


Any suggestions would be greatly appreciated.

###########################################################################

Neutrino on a Motorola Lite5200 EVB

###########################################################################

[image=0x20000]

[virtual=ppcbe,srec +compress] .bootstrap = {

startup-icecube

startup-icecube-6.2.1b -v

PATH=/proc/boot procnto-600 -v

}

[+script] .script = {

display_msg Welcome to QNX Neutrino on the Motorola Lite5200 EVB

Serial driver for Motorola Lite5200 EVB Version 2.0

devc-psc-uart-lite5200evb -c 132000000 -u 1 -e -F -S -b 115200 &


waitfor /dev/ser1

reopen /dev/ser1

\

These env variables inherited by all the programs which follow

SYSNAME=nto

TERM=qansi

HOME=/

slogger &

pipe

\

PCI driver

pci-mgt5200

display_msg Starting Flash Driver

Flash driver

devf-mgt5200 -s 0xff800000,8M,0,8M,64K

devf-generic -s 0xff800000,8M,0,8M,64K

devf-cmf -s 0xff800000,8M,0,8M,64K -r -b5 -u2 -t1 &

devf-cmf2 -s 0xff800000,8M,0,8M,64K -r -b5 -u2 -t1 &

devf-lite5200evb -s 0xff800000,8M,0,8M,64K -r -b5 -u2 -t1

display_msg Starting Flash Driver2

waitfor /usr/lib

waitfor /bin

waitfor /sbin

waitfor /etc

display_msg Flash Driver Initialized

Network driver

Setup Best Comm (DMA) for on-board ethernet driver

parameters from 6.2.1a motorola build file

display_msg Starting Bestcomm DMA driver

bestcomm5200

bestcomm5200 -n 6 -m ff

bestcomm-task-load-lite5200evb -n 6 -m ff

display_msg Starting up on-board ethernet with Large stack and cache -
144.177.209.210

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

io-net -c1 -ptcpip cache=1 -dethernet-lite5200evb mac=0001af520130

display_msg after ionet

waitfor /dev/io-net/en0 4

ifconfig en0 147.177.209.210 netmask 255.255.240.0

display_msg after ifconfig

route add default 147.177.208.1



\

USB driver

devu-ohci-mgt5200 -a0xf0001000 -i38

#bin/mqueue &

#bin/pipe &

display_msg Start the run control script.

[+session] /proc/boot/ksh /proc/boot/rc

display_msg Starting Shell

[+session] PATH=/proc/boot:/bin:/etc ksh &

}

[type=link] /dev/console=/dev/ser1

[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so.2

[type=link] /tmp=/dev/shmem

[type=link] /bin/sh=/proc/boot/ksh

[type=link] /bin/cat=/proc/boot/cat

#[type=link] /usr/local/bin/netconfig=/proc/boot/netconfig

[perms=+r,+x]

[+keeplinked]

libc.so

fpemu.so.2

libm.so.2

[data=c]

devc-psc-uart-lite5200evb

pci-mgt5200

uncomment for Network driver

libsocket.so.2

npm-tcpip.so

libdma-bestcomm5200.so.1

devn-mpc5200.so

#devn-mpc5201.so

#devn-ne2000.so

devn-ethernet-lite5200evb.so

#netconfig

uncomment for Network driver

bestcomm5200

bestcomm-task-load-lite5200evb

io-net

ifconfig

ping

uncomment for Flash driver

devf-mgt5200

#devf-generic

#devf-cmf

#devf-lite5200evb

flashctl

- added 12/16/03 -cmf

flashcmp

libz.so.2

uncomment for USB driver

devu-ohci-mgt5200

usb

general commands

12/16/03 added cat -cmf

cat

cp

ls

pidin

ksh

pci

pipe

slogger

sloginfo

slay

uncomment for Network driver

#[search="${QNX_TARGET}/ppcbe/lib/dll"]

#devn-mpc5200.so

#search="${QNX_TARGET}/ppcbe/usr/bin"]

#evn-mpc5201.so


\

12/16/03 added scripts -cmf

/proc/boot/bootup.ksh = {

if [[ -a /etc/bootup.ksh ]]; then

/etc/bootup.ksh

fi

}



/proc/boot/rc = {

/etc/bootup.ksh is gone.

if [[ ! -e /etc/bootup.ksh ]]; then

ln -s /etc/bootup.config.ksh /etc/bootup.ksh

fi

This gives you a shell in case

/etc/rc is gone.

if [[ -e /etc/rc ]]; then

exec /proc/boot/ksh /etc/rc

else

/etc/bootup.ksh

while /bin/true; do

/proc/boot/ksh

done

/bin/shutdown -v -S system

fi

}



###########################################################################

Interrupt Assignments

---------------------

###########################################################################

Critical Interrupts

###########################################################################

vector: 0

trigger: programmable - level or edge, active high or low

device: External Interrupt 0 - #UART 1_4

vector: 1

trigger: level, active high

device: slice timer interrupt 1

vector: 2

trigger: level, active high

device: HI Int - cascade vector for any peripheral interrupts programmed

to assert a HI interrupt condition

vector: 3

trigger: level, active high

device: CCS wakeup - a wake up from deep sleep mode has occurred

############################################################################

Main Interrupts

############################################################################

vector: 4

trigger: level, active high

device: slice timer interrupt 2 - hard coded as an SMI interrupt

vector: 5

trigger: programmable - level or edge, active high or low

device: External interrupt 1 - MOST_INTREQ

vector: 6

trigger: programmable - level or edge, active high or low

device: External Interrupt 2 - #UART 5_8

vector: 7

trigger: programmable - level or edge, active high or low

device: External interrupt 3 - CPLD_INT_REQ

vector: 8

trigger: level, active high

device: LO Int - cascade vector for any peripheral interrupts programmed

to assert a LO interrupt condition

vector: 9

trigger: level, active high

device: RTC periodic interrupt

vector: 10

trigger: level, active high

device: RTC stopwatch interrupt

vector: 11

trigger: level, active high

device: cascade vector for 8 standard GPIO interrupts

vector: 12

trigger: level, active high

device: cascade vector for 8 wake-up GPIO interrupts

vector: 13

trigger: level, active high

device: internal general purpose timer 0

vector: 14

trigger: level, active high

device: internal general purpose timer 1

vector: 15

trigger: level, active high

device: internal general purpose timer 2

vector: 16

trigger: level, active high

device: internal general purpose timer 3

vector: 17

trigger: level, active high

device: internal general purpose timer 4

vector: 18

trigger: level, active high

device: internal general purpose timer 5

vector: 19

trigger: level, active high

device: internal general purpose timer 6

vector: 20

trigger: level, active high

device: internal general purpose timer 7

###########################################################################

Peripheral Interrupts

###########################################################################

vector: 32

trigger: level, active high

device: SmartComm interrupt - fixed as highest priority peripheral

interrupt, and fixed to generate HI Int

vector: 33

trigger: level, active high

device: Programmable Serial Controller (PSC) 1

vector: 34

trigger: level, active high

device: PSC 2

vector: 35

trigger: level, active high

device: PSC 3

vector: 36

trigger: level, active high

device: IrDA

vector: 37

trigger: level, active high

device: Ethernet

vector: 38

trigger: level, active high

device: USB

vector: 39

trigger: level, active high

device: ATA

vector: 40

trigger: level, active high

device: PCI controller

vector: 41

trigger: level, active high

device: PCI SC Initiator Rx

vector: 42

trigger: level, active high

device: PCI SC Initiator Tx

vector: 43

trigger: N/A

device: Reserved

vector: 44

trigger: N/A

device: Reserved

vector: 45

trigger: level, active high

device: SPI modf

vector: 46

trigger: level, active high

device: SPI spif

vector: 47

trigger: level, active high

device: I2C 1

vector: 48

trigger: level, active high

device: I2C 2

vector: 49

trigger: level, active high

device: CAN 1

vector: 50

trigger: level, active high

device: CAN 2

vector: 51

trigger: level, active high

device: IR_Rx

vector: 52

trigger: level, active high

device: IR_Tx

vector: 53

trigger: level, active high

device: XLB Arbiter

###########################################################################

GPIO Interrupts

###########################################################################

vector: 64

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 0

vector: 65

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 1

vector: 66

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 2

vector: 67

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 3

vector: 68

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 4

vector: 69

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 5

vector: 70

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 6

vector: 71

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Simple Interrupt GPIO 7

vector: 72

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 0

vector: 73

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 1

vector: 74

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 2

vector: 75

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 3

vector: 76

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 4

vector: 77

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 5

vector: 78

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 6

vector: 79

trigger: programmable - any transition, rising edge, falling edge, or

pulse (any 2 transitions)

device: Wake up Interrupt GPIO 7

############################################################################

Smartcomm Interrupts

###########################################################################

vector: 80

trigger: level, active high

device: SmartComm - Execution Unit 7 Interrupt

vector: 81

trigger: level, active high

device: SmartComm - Execution Unit 6 Interrupt

vector: 82

trigger: level, active high

device: SmartComm - Execution Unit 5 Interrupt

vector: 83

trigger: level, active high

device: SmartComm - Execution Unit 4 Interrupt

vector: 84

trigger: level, active high

device: SmartComm - Execution Unit 3 Interrupt

vector: 85

trigger: level, active high

device: SmartComm - Execution Unit 2 Interrupt

vector: 86

trigger: level, active high

device: SmartComm - Execution Unit 1 Interrupt

vector: 87

trigger: level, active high

device: SmartComm - Execution Unit 0 Interrupt

vector: 88

trigger: level, active high

device: SmartComm - Task 15 Interrupt

vector: 89

trigger: level, active high

device: SmartComm - Task 14 Interrupt

vector: 90

trigger: level, active high

device: SmartComm - Task 13 Interrupt

vector: 91

trigger: level, active high

device: SmartComm - Task 12 Interrupt

vector: 92

trigger: level, active high

device: SmartComm - Task 11 Interrupt

vector: 93

trigger: level, active high

device: SmartComm - Task 10 Interrupt

vector: 94

trigger: level, active high

device: SmartComm - Task 9 Interrupt

vector: 95

trigger: level, active high

device: SmartComm - Task 8 Interrupt

vector: 96

trigger: level, active high

device: SmartComm - Task 7 Interrupt

vector: 97

trigger: level, active high

device: SmartComm - Task 6 Interrupt

vector: 98

trigger: level, active high

device: SmartComm - Task 5 Interrupt

vector: 99

trigger: level, active high

device: SmartComm - Task 4 Interrupt

vector: 100

trigger: level, active high

device: SmartComm - Task 3 Interrupt

vector: 101

trigger: level, active high

device: SmartComm - Task 2 Interrupt

vector: 102

trigger: level, active high

device: SmartComm - Task 1 Interrupt

vector: 103

trigger: level, active high

device: SmartComm - Task 0 Interrupt

vector: 104

trigger: level, active high

device: SmartComm - Timer 7 Interrupt

vector: 105

trigger: level, active high

device: SmartComm - Timer 6 Interrupt

vector: 106

trigger: level, active high

device: SmartComm - Timer 5 Interrupt

vector: 107

trigger: level, active high

device: SmartComm - Timer 4 Interrupt

vector: 108

trigger: level, active high

device: SmartComm - Timer 3 Interrupt

vector: 109

trigger: level, active high

device: SmartComm - Timer 2 Interrupt

vector: 110

trigger: level, active high

device: SmartComm - Timer 1 Interrupt

############################################################################

Chris Fischer <cfischer@harris.com> wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.



I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.

After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.

David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com

“Dave Green” <dgreen@qnx.com> wrote in message
news:brt3oi$5n1$1@nntp.qnx.com

Chris Fischer <> cfischer@harris.com> > wrote:
I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.



I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.

That makes sense. I’ve tried with the drivers from the beta
version (i.e. devn-ethernet-lite5200evb) and they work fine.

After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.

Here’s the output when I start the net:

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

unable to init dll devn-mpc5200: Function not implemented

Here’s the pidin ir:

pid tid name
1 1 procnto
0 0x80000000 0 — @0x505d8:0x0
1 2 procnto
1 3 procnto
1 4 procnto
1 5 procnto
1 6 procnto
1 7 procnto
1 8 procnto
1 9 procnto
1 10 procnto
2 1 c-uart-lite5200evb
2 2 c-uart-lite5200evb
1 0x21 45836 — =INTR
3 1 proc/boot/slogger
3 2 proc/boot/slogger
4 1 proc/boot/pipe
4 2 proc/boot/pipe
4 3 proc/boot/pipe
5 1 ppc/be/pci-mgt5200
6 1 pc/be/devf-mgt5200
6 2 pc/be/devf-mgt5200
6 3 pc/be/devf-mgt5200
4103 1 proc/boot/ksh
4104 1 proc/boot/io-net
4104 2 proc/boot/io-net
4104 3 proc/boot/io-net
4104 4 proc/boot/io-net
4104 5 proc/boot/io-net
32777 1 proc/boot/pidin

TIA.

David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com

Chris Fischer <cfischer@harris.com> wrote:

“Dave Green” <> dgreen@qnx.com> > wrote in message
news:brt3oi$5n1$> 1@nntp.qnx.com> …
Chris Fischer <> cfischer@harris.com> > wrote:
I’m relatively new to QNX, and I am trying to get the 6.2.1B version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.



I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.

That makes sense. I’ve tried with the drivers from the beta
version (i.e. devn-ethernet-lite5200evb) and they work fine.

OK, if the old network driver works, that indicates to me that
you’re still using an old startup as well. I’d suggest using the
latest startup-icecube, and all the latest drivers that came with
the GA version of the BSP.

After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.

Here’s the output when I start the net:

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

unable to init dll devn-mpc5200: Function not implemented

Here’s the pidin ir:

pid tid name
1 1 procnto
0 0x80000000 0 — @0x505d8:0x0
1 2 procnto
1 3 procnto
1 4 procnto
1 5 procnto
1 6 procnto
1 7 procnto
1 8 procnto
1 9 procnto
1 10 procnto
2 1 c-uart-lite5200evb
2 2 c-uart-lite5200evb
1 0x21 45836 — =INTR
3 1 proc/boot/slogger
3 2 proc/boot/slogger
4 1 proc/boot/pipe
4 2 proc/boot/pipe
4 3 proc/boot/pipe
5 1 ppc/be/pci-mgt5200
6 1 pc/be/devf-mgt5200
6 2 pc/be/devf-mgt5200
6 3 pc/be/devf-mgt5200
4103 1 proc/boot/ksh
4104 1 proc/boot/io-net
4104 2 proc/boot/io-net
4104 3 proc/boot/io-net
4104 4 proc/boot/io-net
4104 5 proc/boot/io-net
32777 1 proc/boot/pidin

TIA.

\

David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com

David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com

I did as you suggested, and the network now works. Thanks.

It’s not immediately obvious to me which devc-* I should be running.
I don’t see the one that came with the icecube.build file -
devc-serpscx-nodma
(plus the nodma scares me).

Which devc is recommended for the icecube board?


“Jay Greig” <greig@qnx.com> wrote in message
news:brt8rk$akr$1@nntp.qnx.com

I believe that you may have a case of versionitis between the beta BSP
and the GA version.

The serial driver in the released version should be attaching to
interrupt 65, while your environment shows it to be attached to 0x21 (33).

From what Dave said, the network driver and the startup from the
released package need to go hand-in-hand.

What host system are you developing from (RTP, Windows)? Try installing
the released package on a clean system (as to not blow away your current
working environment) and see if that clears up this problem.

-Jay.

Chris Fischer wrote:
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:brt3oi$5n1$> 1@nntp.qnx.com> …

Chris Fischer <> cfischer@harris.com> > wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B
version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.


That makes sense. I’ve tried with the drivers from the beta
version (i.e. devn-ethernet-lite5200evb) and they work fine.


After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.


Here’s the output when I start the net:

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

unable to init dll devn-mpc5200: Function not implemented

Here’s the pidin ir:

pid tid name
1 1 procnto
0 0x80000000 0 — @0x505d8:0x0
1 2 procnto
1 3 procnto
1 4 procnto
1 5 procnto
1 6 procnto
1 7 procnto
1 8 procnto
1 9 procnto
1 10 procnto
2 1 c-uart-lite5200evb
2 2 c-uart-lite5200evb
1 0x21 45836 — =INTR
3 1 proc/boot/slogger
3 2 proc/boot/slogger
4 1 proc/boot/pipe
4 2 proc/boot/pipe
4 3 proc/boot/pipe
5 1 ppc/be/pci-mgt5200
6 1 pc/be/devf-mgt5200
6 2 pc/be/devf-mgt5200
6 3 pc/be/devf-mgt5200
4103 1 proc/boot/ksh
4104 1 proc/boot/io-net
4104 2 proc/boot/io-net
4104 3 proc/boot/io-net
4104 4 proc/boot/io-net
4104 5 proc/boot/io-net
32777 1 proc/boot/pidin

TIA.

\

David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com
\

Chris Fischer <cfischer@harris.com> wrote:

I did as you suggested, and the network now works. Thanks.

It’s not immediately obvious to me which devc-* I should be running.
I don’t see the one that came with the icecube.build file -
devc-serpscx-nodma
(plus the nodma scares me).

Which devc is recommended for the icecube board?

devc-serpsc:

devc-serpsc -c 132000000 -u 1 -e -F -S -b 115200 0xf0002000,65 &

“Jay Greig” <> greig@qnx.com> > wrote in message
news:brt8rk$akr$> 1@nntp.qnx.com> …
I believe that you may have a case of versionitis between the beta BSP
and the GA version.

The serial driver in the released version should be attaching to
interrupt 65, while your environment shows it to be attached to 0x21 (33).

From what Dave said, the network driver and the startup from the
released package need to go hand-in-hand.

What host system are you developing from (RTP, Windows)? Try installing
the released package on a clean system (as to not blow away your current
working environment) and see if that clears up this problem.

-Jay.

Chris Fischer wrote:
“Dave Green” <> dgreen@qnx.com> > wrote in message
news:brt3oi$5n1$> 1@nntp.qnx.com> …

Chris Fischer <> cfischer@harris.com> > wrote:

I’m relatively new to QNX, and I am trying to get the 6.2.1B
version
(released, not
beta) running. This is with the Icecube Eval Board.

Another question, what is the revision of the board? Are you booting
out of flash, or from the dbug monitor?

I am used the Icecube (not the Icecube+), with 8MB of flash.
I am booting from the dbug monitor.

I’ve got 2 major problems:

  1. Network doesn’t start. I get the message “unable to init dll
    devn-mpc5200 - function
    not implemented”. It almost seems like a problem in the

Can you post the output from sloginfo once the board boots.

Sloginfo said this:

sloginfo

Time Sev Major Minor Args
Jan 03 20:43:54 5 14 0 tcpip starting
Jan 03 20:43:54 3 14 0 Using pseudo random generator. See
“random” on
Jan 03 20:43:54 5 10 0 InterruptAttachEvent failed

The latest startup-icecube, which shipped with this BSP, has re-mapped
various interrupt vectors. However, the network driver that shipped
with the BSP took this into account, and the default interrupt vectors
programmed into the driver were changed accordingly. The network
driver uses two interrupts. In the old BSP, they were 37 and 100.
In the new BSP, they are 69 and 140.


That makes sense. I’ve tried with the drivers from the beta
version (i.e. devn-ethernet-lite5200evb) and they work fine.


After starting the network driver, can you please post the output
of ‘pidin ir’? This should indicate whether the problem is that an older
network driver is being used with the new startup, or that an old
startup is being used with a new network driver, or that the problem
is something else altogether.


Here’s the output when I start the net:

io-net -c1 -ptcpip cache=1 -dmpc5200 mac=0001af520130 -v

unable to init dll devn-mpc5200: Function not implemented

Here’s the pidin ir:

pid tid name
1 1 procnto
0 0x80000000 0 — @0x505d8:0x0
1 2 procnto
1 3 procnto
1 4 procnto
1 5 procnto
1 6 procnto
1 7 procnto
1 8 procnto
1 9 procnto
1 10 procnto
2 1 c-uart-lite5200evb
2 2 c-uart-lite5200evb
1 0x21 45836 — =INTR
3 1 proc/boot/slogger
3 2 proc/boot/slogger
4 1 proc/boot/pipe
4 2 proc/boot/pipe
4 3 proc/boot/pipe
5 1 ppc/be/pci-mgt5200
6 1 pc/be/devf-mgt5200
6 2 pc/be/devf-mgt5200
6 3 pc/be/devf-mgt5200
4103 1 proc/boot/ksh
4104 1 proc/boot/io-net
4104 2 proc/boot/io-net
4104 3 proc/boot/io-net
4104 4 proc/boot/io-net
4104 5 proc/boot/io-net
32777 1 proc/boot/pidin

TIA.

\

David Green (> dgreen@qnx.com> )
QNX Software Systems Ltd.
http://www.qnx.com

\

David Green (dgreen@qnx.com)
QNX Software Systems Ltd.
http://www.qnx.com