Renesas SystemH-AMANDA network

QNX Newsgroups (Archives) qdn.public.qnxrtp.sh4
1

Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with QNX
6.2.1B (also tried with A, without the Power Management supplement). The
network chipset is a SMC91c110, as mentioned in your documentation. I
installed the IPL in flash, and QNX runs fine, until I try setting up the
network. I don’t use the Amanda board yet, because and I want to set up the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I added the
verbose flag and modified the mac address.

io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the irq 2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other hosts and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping it from
other hosts on the same network. One thing I am not sure of is how to set
the MAC address properly. MAC addresses aren’t supposed to be written in the
chipset ? I set up the Sandpoint PPC eval board the same way before this
one, so I assumed it would be as easy to do but it doesn’t seem like it…

Here is my build file, I barely modified the default version from the BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also. In the
Step 8, in the instructions to load an OS image using the qconn target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14 the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…

Regards,
Marc Labbé

2

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the larger
change wound up not taking place yet, for firmware version reasons, but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) | SIRQ(1) | INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <marc.labbe@mindready.com> wrote:

Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with QNX
6.2.1B (also tried with A, without the Power Management supplement). The
network chipset is a SMC91c110, as mentioned in your documentation. I
installed the IPL in flash, and QNX runs fine, until I try setting up the
network. I don’t use the Amanda board yet, because and I want to set up the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I added the
verbose flag and modified the mac address.

io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the irq 2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other hosts and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping it from
other hosts on the same network. One thing I am not sure of is how to set
the MAC address properly. MAC addresses aren’t supposed to be written in the
chipset ? I set up the Sandpoint PPC eval board the same way before this
one, so I assumed it would be as easy to do but it doesn’t seem like it…

Here is my build file, I barely modified the default version from the BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also. In the
Step 8, in the instructions to load an OS image using the qconn target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14 the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…

–

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

3

Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the version I
have ? I will try re-compiling the whole thing, maybe there is mismatch
between the src and the bin package I installed.

Marc

Dave Green <dgreen@qnx.com> wrote in message
news:bjkr94$hv$1@nntp.qnx.com…

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the larger
change wound up not taking place yet, for firmware version reasons, but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) | SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with QNX
6.2.1B (also tried with A, without the Power Management supplement). The
network chipset is a SMC91c110, as mentioned in your documentation. I
installed the IPL in flash, and QNX runs fine, until I try setting up
the
network. I don’t use the Amanda board yet, because and I want to set up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I added
the
verbose flag and modified the mac address.

io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping it
from
other hosts on the same network. One thing I am not sure of is how to
set
the MAC address properly. MAC addresses aren’t supposed to be written in
the
chipset ? I set up the Sandpoint PPC eval board the same way before this
one, so I assumed it would be as easy to do but it doesn’t seem like
it…

Here is my build file, I barely modified the default version from the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also. In
the
Step 8, in the instructions to load an OS image using the qconn target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14 the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

4

Marc Labbe <marc.labbe@mindready.com> wrote:

Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the version I
have ? I will try re-compiling the whole thing, maybe there is mismatch
between the src and the bin package I installed.

Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the larger
change wound up not taking place yet, for firmware version reasons, but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) | SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with QNX
6.2.1B (also tried with A, without the Power Management supplement). The
network chipset is a SMC91c110, as mentioned in your documentation. I
installed the IPL in flash, and QNX runs fine, until I try setting up
the
network. I don’t use the Amanda board yet, because and I want to set up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I added
the
verbose flag and modified the mac address.

io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping it
from
other hosts on the same network. One thing I am not sure of is how to
set
the MAC address properly. MAC addresses aren’t supposed to be written in
the
chipset ? I set up the Sandpoint PPC eval board the same way before this
one, so I assumed it would be as easy to do but it doesn’t seem like
it…

Here is my build file, I barely modified the default version from the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also. In
the
Step 8, in the instructions to load an OS image using the qconn target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14 the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

5

Marc,

I’m attempting to install and test the same package that you have,
but I need to find one of the builders to obtain a licence number.
In the meantime, I’ve built an image from our internal CVS repository,
and tested the networking, using both the tiny and full tcpip stacks,
and it works OK for me. I did notice that io-net takes a while to
set up before ifconfig can be run, but I didn’t experience any hangs.

Could I e-mail you a binary boot image to try, just to eliminate possible
hardware/firmware issues on your board?


Dave Green <dgreen@qnx.com> wrote:

Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the version I
have ? I will try re-compiling the whole thing, maybe there is mismatch
between the src and the bin package I installed.



Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the larger
change wound up not taking place yet, for firmware version reasons, but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) | SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with QNX
6.2.1B (also tried with A, without the Power Management supplement). The
network chipset is a SMC91c110, as mentioned in your documentation. I
installed the IPL in flash, and QNX runs fine, until I try setting up
the
network. I don’t use the Amanda board yet, because and I want to set up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I added
the
verbose flag and modified the mac address.

io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping it
from
other hosts on the same network. One thing I am not sure of is how to
set
the MAC address properly. MAC addresses aren’t supposed to be written in
the
chipset ? I set up the Sandpoint PPC eval board the same way before this
one, so I assumed it would be as easy to do but it doesn’t seem like
it…

Here is my build file, I barely modified the default version from the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also. In
the
Step 8, in the instructions to load an OS image using the qconn target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14 the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

–

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

6

Could I e-mail you a binary boot image to try, just to eliminate possible
hardware/firmware issues on your board?
of course, send it to the email adress in the header of this message.

BTW, the systemh-asb BSP packages I use were sent to my superior Pascal
Levesque a few weeks ago. If you need the license / registration numbers for
the support, I could send them to you privately. I used the public lines
because I am used to it and, you proved it, it’s ususally fast and reliable.

Here are the packages names:
systemh-asb_bin-6[1].2.1-bld6.qpr
systemh-asb_src-6[1].2.1-bld6.qpr

Marc Labbé
Software Designer
Mindready Solutions inc.
Tel: (514) 339-1394 x2170
Fax: (514) 339-1376


Dave Green <dgreen@qnx.com> wrote in message
news:bjl0rt$74m$1@nntp.qnx.com…

Marc,

I’m attempting to install and test the same package that you have,
but I need to find one of the builders to obtain a licence number.
In the meantime, I’ve built an image from our internal CVS repository,
and tested the networking, using both the tiny and full tcpip stacks,
and it works OK for me. I did notice that io-net takes a while to
set up before ifconfig can be run, but I didn’t experience any hangs.

Could I e-mail you a binary boot image to try, just to eliminate possible
hardware/firmware issues on your board?


Dave Green <> dgreen@qnx.com> > wrote:
Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the
version I
have ? I will try re-compiling the whole thing, maybe there is mismatch
between the src and the bin package I installed.


Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the
larger
change wound up not taking place yet, for firmware version reasons,
but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) |
SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with
QNX
6.2.1B (also tried with A, without the Power Management supplement).
The
network chipset is a SMC91c110, as mentioned in your documentation.
I
installed the IPL in flash, and QNX runs fine, until I try setting
up
the
network. I don’t use the Amanda board yet, because and I want to set
up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the
boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I
added
the
verbose flag and modified the mac address.

io-net -dsmc9000

mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the
irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following
commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other
    hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping
it
from
other hosts on the same network. One thing I am not sure of is how
to
set
the MAC address properly. MAC addresses aren’t supposed to be
written in
the
chipset ? I set up the Sandpoint PPC eval board the same way before
this
one, so I assumed it would be as easy to do but it doesn’t seem like
it…

Here is my build file, I barely modified the default version from
the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also.
In
the
Step 8, in the instructions to load an OS image using the qconn
target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14
the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

–

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

7

Marc,

I think I’ve determined what’s happening - there is a ROM containing firmware
for the FPGA interrupt controller on the board, which the SMC9000 uses.
Most of the boards that we have here contain firmware version 01. With
this firmware, networking works fine. However, we have a version 02
firmware ROM here, and when I put that into the previously working
board, it hangs soon after starting the network driver.

I’d expect that your board has a V02 ROM (seated in position U7
on the backplane board).

We (QNX) will need to contact Renesas to determine exactly what’s
changed between firmware versions, so we’ll know how to work around
this, and support either version of firmware.

In the meantime, I’d suggest starting the driver and attaching
to irq 0x2000 (the OS timer interrupt). The network performance
may be slower, but at least networking will work while we get
this issue resolved.

io-net -dsmc9000 ioport=0x13010300,irq=0x2000,mac=xxxxxxxxxxxx -ptcpip

waitfor /dev/io-net

ifconfig en0 x.x.x.x


Marc Labbe <marc.labbe@mindready.com> wrote:

Could I e-mail you a binary boot image to try, just to eliminate possible
hardware/firmware issues on your board?
of course, send it to the email adress in the header of this message.

BTW, the systemh-asb BSP packages I use were sent to my superior Pascal
Levesque a few weeks ago. If you need the license / registration numbers for
the support, I could send them to you privately. I used the public lines
because I am used to it and, you proved it, it’s ususally fast and reliable.

Here are the packages names:
systemh-asb_bin-6[1].2.1-bld6.qpr
systemh-asb_src-6[1].2.1-bld6.qpr

Marc Labbe
Software Designer
Mindready Solutions inc.
Tel: (514) 339-1394 x2170
Fax: (514) 339-1376



Dave Green <> dgreen@qnx.com> > wrote in message
news:bjl0rt$74m$> 1@nntp.qnx.com> …
Marc,

I’m attempting to install and test the same package that you have,
but I need to find one of the builders to obtain a licence number.
In the meantime, I’ve built an image from our internal CVS repository,
and tested the networking, using both the tiny and full tcpip stacks,
and it works OK for me. I did notice that io-net takes a while to
set up before ifconfig can be run, but I didn’t experience any hangs.

Could I e-mail you a binary boot image to try, just to eliminate possible
hardware/firmware issues on your board?


Dave Green <> dgreen@qnx.com> > wrote:
Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the
version I
have ? I will try re-compiling the whole thing, maybe there is mismatch
between the src and the bin package I installed.


Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the startup
for this board, as part of a larger overall change. However, the
larger
change wound up not taking place yet, for firmware version reasons,
but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) |
SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA with
QNX
6.2.1B (also tried with A, without the Power Management supplement).
The
network chipset is a SMC91c110, as mentioned in your documentation.
I
installed the IPL in flash, and QNX runs fine, until I try setting
up
the
network. I don’t use the Amanda board yet, because and I want to set
up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or the
boot
script, it froze after a little while. Before freezing, it shows the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the OS
Running…” section of the systemH-ASB BSP documents to which I
added
the
verbose flag and modified the mac address.

io-net -dsmc9000

mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes the
irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following
commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with other
    hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I ping
it
from
other hosts on the same network. One thing I am not sure of is how
to
set
the MAC address properly. MAC addresses aren’t supposed to be
written in
the
chipset ? I set up the Sandpoint PPC eval board the same way before
this
one, so I assumed it would be as easy to do but it doesn’t seem like
it…

Here is my build file, I barely modified the default version from
the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000 mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation also.
In
the
Step 8, in the instructions to load an OS image using the qconn
target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in 14
the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

–

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

8

Dave,

the tag on the ROM seated at U7 has the number D001681_23_V02 on it, so your
probably on the right track.

Also, your suggestion to use the timer interrupt worked ! Could this affect
the system’s performance if I use the same interrupt in my applications
working with timers ?

Keep me posted when you are able to provide us with a solution to the
problem. If possible, contact me directly @mindready to make sure I get the
update as soon as its ready. Do you need me to send a report using the
official support lines for this ?

Thanks again !

Marc

Dave Green <dgreen@qnx.com> wrote in message
news:bjl2kf$93b$1@nntp.qnx.com…

Marc,

I think I’ve determined what’s happening - there is a ROM containing
firmware
for the FPGA interrupt controller on the board, which the SMC9000 uses.
Most of the boards that we have here contain firmware version 01. With
this firmware, networking works fine. However, we have a version 02
firmware ROM here, and when I put that into the previously working
board, it hangs soon after starting the network driver.

I’d expect that your board has a V02 ROM (seated in position U7
on the backplane board).

We (QNX) will need to contact Renesas to determine exactly what’s
changed between firmware versions, so we’ll know how to work around
this, and support either version of firmware.

In the meantime, I’d suggest starting the driver and attaching
to irq 0x2000 (the OS timer interrupt). The network performance
may be slower, but at least networking will work while we get
this issue resolved.

io-net -dsmc9000 ioport=0x13010300,irq=0x2000,mac=xxxxxxxxxxxx -ptcpip

waitfor /dev/io-net

ifconfig en0 x.x.x.x


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Could I e-mail you a binary boot image to try, just to eliminate
possible
hardware/firmware issues on your board?
of course, send it to the email adress in the header of this message.

BTW, the systemh-asb BSP packages I use were sent to my superior Pascal
Levesque a few weeks ago. If you need the license / registration numbers
for
the support, I could send them to you privately. I used the public lines
because I am used to it and, you proved it, it’s ususally fast and
reliable.

Here are the packages names:
systemh-asb_bin-6[1].2.1-bld6.qpr
systemh-asb_src-6[1].2.1-bld6.qpr

Marc Labbe
Software Designer
Mindready Solutions inc.
Tel: (514) 339-1394 x2170
Fax: (514) 339-1376


Dave Green <> dgreen@qnx.com> > wrote in message
news:bjl0rt$74m$> 1@nntp.qnx.com> …
Marc,

I’m attempting to install and test the same package that you have,
but I need to find one of the builders to obtain a licence number.
In the meantime, I’ve built an image from our internal CVS repository,
and tested the networking, using both the tiny and full tcpip stacks,
and it works OK for me. I did notice that io-net takes a while to
set up before ifconfig can be run, but I didn’t experience any hangs.

Could I e-mail you a binary boot image to try, just to eliminate
possible
hardware/firmware issues on your board?


Dave Green <> dgreen@qnx.com> > wrote:
Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the
version I
have ? I will try re-compiling the whole thing, maybe there is
mismatch
between the src and the bin package I installed.


Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the
startup
for this board, as part of a larger overall change. However, the
larger
change wound up not taking place yet, for firmware version reasons,
but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) |
SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue
is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA
with
QNX
6.2.1B (also tried with A, without the Power Management
supplement).
The
network chipset is a SMC91c110, as mentioned in your
documentation.
I
installed the IPL in flash, and QNX runs fine, until I try
setting
up
the
network. I don’t use the Amanda board yet, because and I want to
set
up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or
the
boot
script, it froze after a little while. Before freezing, it shows
the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the
OS
Running…” section of the systemH-ASB BSP documents to which I
added
the
verbose flag and modified the mac address.

io-net -dsmc9000

mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes
the
irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following
commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with
    other
    hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I
ping
it
from
other hosts on the same network. One thing I am not sure of is
how
to
set
the MAC address properly. MAC addresses aren’t supposed to be
written in
the
chipset ? I set up the Sandpoint PPC eval board the same way
before
this
one, so I assumed it would be as easy to do but it doesn’t seem
like
it…

Here is my build file, I barely modified the default version from
the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000
mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation
also.
In
the
Step 8, in the instructions to load an OS image using the qconn
target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in
14
the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

–

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

9

Marc Labbe <marc.labbe@mindready.com> wrote:

Dave,

the tag on the ROM seated at U7 has the number D001681_23_V02 on it, so your
probably on the right track.

Also, your suggestion to use the timer interrupt worked ! Could this affect
the system’s performance if I use the same interrupt in my applications
working with timers ?

I wouldn’t expect any overall drop in system performance, just in
network performance.

Keep me posted when you are able to provide us with a solution to the
problem. If possible, contact me directly @mindready to make sure I get the
update as soon as its ready. Do you need me to send a report using the
official support lines for this ?

I’ve passed the information along to a manager here, who is going to contact
Hitachi/Renesas to find out about the changes to the firmware, units shipped
with each version, etc., at which point we can decide how best to deal with
this. I imagine everyone who has affected BSPs will be notified/patched at
that point.



Thanks again !

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjl2kf$93b$> 1@nntp.qnx.com> …
Marc,

I think I’ve determined what’s happening - there is a ROM containing
firmware
for the FPGA interrupt controller on the board, which the SMC9000 uses.
Most of the boards that we have here contain firmware version 01. With
this firmware, networking works fine. However, we have a version 02
firmware ROM here, and when I put that into the previously working
board, it hangs soon after starting the network driver.

I’d expect that your board has a V02 ROM (seated in position U7
on the backplane board).

We (QNX) will need to contact Renesas to determine exactly what’s
changed between firmware versions, so we’ll know how to work around
this, and support either version of firmware.

In the meantime, I’d suggest starting the driver and attaching
to irq 0x2000 (the OS timer interrupt). The network performance
may be slower, but at least networking will work while we get
this issue resolved.

io-net -dsmc9000 ioport=0x13010300,irq=0x2000,mac=xxxxxxxxxxxx -ptcpip

waitfor /dev/io-net

ifconfig en0 x.x.x.x


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Could I e-mail you a binary boot image to try, just to eliminate
possible
hardware/firmware issues on your board?
of course, send it to the email adress in the header of this message.

BTW, the systemh-asb BSP packages I use were sent to my superior Pascal
Levesque a few weeks ago. If you need the license / registration numbers
for
the support, I could send them to you privately. I used the public lines
because I am used to it and, you proved it, it’s ususally fast and
reliable.

Here are the packages names:
systemh-asb_bin-6[1].2.1-bld6.qpr
systemh-asb_src-6[1].2.1-bld6.qpr

Marc Labbe
Software Designer
Mindready Solutions inc.
Tel: (514) 339-1394 x2170
Fax: (514) 339-1376


Dave Green <> dgreen@qnx.com> > wrote in message
news:bjl0rt$74m$> 1@nntp.qnx.com> …
Marc,

I’m attempting to install and test the same package that you have,
but I need to find one of the builders to obtain a licence number.
In the meantime, I’ve built an image from our internal CVS repository,
and tested the networking, using both the tiny and full tcpip stacks,
and it works OK for me. I did notice that io-net takes a while to
set up before ifconfig can be run, but I didn’t experience any hangs.

Could I e-mail you a binary boot image to try, just to eliminate
possible
hardware/firmware issues on your board?


Dave Green <> dgreen@qnx.com> > wrote:
Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi Dave,

I have version 6.2.1 build 6 and this line is not commented in the
version I
have ? I will try re-compiling the whole thing, maybe there is
mismatch
between the src and the bin package I installed.


Hmmm… I’ll investigate further here also.

Marc

Dave Green <> dgreen@qnx.com> > wrote in message
news:bjkr94$hv$> 1@nntp.qnx.com> …

Hi Marc,

There was a minor change made to the init_hwinfo.c file of the
startup
for this board, as part of a larger overall change. However, the
larger
change wound up not taking place yet, for firmware version reasons,
but
the minor change accidentally shipped.

In your init_hwinfo.c file in the startup directory, look for
the following line:

// out32(SYSTEMH_FPGA_REGS_IMASK, SIRQ(4) | SIRQ(3) | SIRQ(12) |
SIRQ(1)
| INTR0);

and remove the comment to re-instate the line of code.

After this, re-build your startup, and see if the networking issue
is
solved.


Marc Labbe <> marc.labbe@mindready.com> > wrote:
Hi,

I am trying to set up the network on a Renesas SystemH-AMANDA
with
QNX
6.2.1B (also tried with A, without the Power Management
supplement).
The
network chipset is a SMC91c110, as mentioned in your
documentation.
I
installed the IPL in flash, and QNX runs fine, until I try
setting
up
the
network. I don’t use the Amanda board yet, because and I want to
set
up
the
SystemH engine properly before.

First, when I tried to start io-net either from the console or
the
boot
script, it froze after a little while. Before freezing, it shows
the
following driver info.

SMC9000
Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x7
MAC address … 000002 821c55

To start io-net, I used the command as defined the “Getting the
OS
Running…” section of the systemH-ASB BSP documents to which I
added
the
verbose flag and modified the mac address.

io-net -dsmc9000

mac=000002821c55,ioport=0x13010300,irq=7,verbose=1 &

Then I tried the same command without setting the irq, it takes
the
irq
2
and it doesn’t freeze anymore.

SMC9000

Vendor … 0x0
Device … 0x9
Revision … 0x0
I/O port base … 0x13010300
Interrupt … 0x2
MAC address … 000002 821c55

Then, I (try to) set up the interface using the following
commands…

  1. mount -T io-net npm-tcpip.so
  2. ifconfig en0 10.1.0.226
  3. route add default 10.1.0.1 — to add our default gateway
  4. ping 10.1.0.1 — fails to find the gateway, I tried with
    other
    hosts
    and
    it didn’t work either…

Everyting is connected properly and the gateway is running, I
ping
it
from
other hosts on the same network. One thing I am not sure of is
how
to
set
the MAC address properly. MAC addresses aren’t supposed to be
written in
the
chipset ? I set up the Sandpoint PPC eval board the same way
before
this
one, so I assumed it would be as easy to do but it doesn’t seem
like
it…

Here is my build file, I barely modified the default version from
the
BSP.

[image=0x8c010000]
[virtual=shle/binary +compress] .bootstrap = {

uncomment for SH7751 support

#startup-systemh -Dscif -v

uncomment for SH7751R support

startup-systemh -Dscif…57600.47923200.16 -f234000000 -v

PATH=/proc/boot procnto -v
}

[+script] .script = {
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2

uncomment for SH7751 support

#devc-sersci -b57600 -c 41670000/16 -e scif &

uncomment for SH7751R support

devc-sersci -b57600 -c 47923200/16 -e scif &

reopen
display_msg Welcome to Neutrino on SystemH

slogger &

SYSNAME=nto
TERM=qansi
LD_LIBRARY_PATH=/proc/boot

#io-net -dsmc9000
mac=000002821c55,ioport=0x13010300,verbose=1 &

[+session] PATH=:/proc/boot sh &
}

[type=link] /dev/console=/dev/ser1
[type=link] /tmp=/dev/shmem
libc.so.2
libsocket.so
devn-smc9000.so
npm-ttcpip.so
npm-tcpip.so
npm-qnet.so

[data=c]
slogger
sloginfo
devc-sersci
sh=esh
pidin
ls
io-net
ping
slay
mount
ifconfig
route

I am a little confused about some parts of the documentation
also.
In
the
Step 8, in the instructions to load an OS image using the qconn
target
agent, point 11 tells us to add the npm-tcpip.so dll and then, in
14
the
io-net is started with ttcpip ?

Anyway, my main problem now is the network interface…


\

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

–

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

–

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