Install Dev.ser for DIGI ClassicBoard

I am having problems getting a DIGI ClassicBoard (PCI) running. DIGI support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that QNX support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128 bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only) causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and “stty -a
</dev/digi1” shows “normal” conditions for a serial port. When I qtalk to the
port and check it with a loop back tester, I get no response suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to installing any
DIGI ClassicBoards. We have been successfully launching Connectech boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are moving to the
DIGI card because we need world wide access and PCI interface. Please let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: support@pcauto.com
Ontario, Canada, N2J 3Z4

I am of the firm opinion that these won’t work. I had talked
to Scott at Digi (their QNX support guy) and he was of that
opinion. It will need a driver to sort out the real ports, as
I recall.

Richard

Douglas Barker wrote:

I am having problems getting a DIGI ClassicBoard (PCI) running. DIGI support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that QNX support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128 bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only) causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and “stty -a
/dev/digi1” shows “normal” conditions for a serial port. When I qtalk to the
port and check it with a loop back tester, I get no response suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to installing any
DIGI ClassicBoards. We have been successfully launching Connectech boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are moving to the
DIGI card because we need world wide access and PCI interface. Please let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: > support@pcauto.com
Ontario, Canada, N2J 3Z4

I checked back with Digi and their support staff indicate that there is no Scott in
support (must have moved on to greener pastures). Their answer is “it MAY work under
QNX” BUT they “don’t supply the drivers and don’t know if it does work”. The support
staff indicate that ONLY QNX can give the definitive answer on this.

Thanks for the input Richard. We appreciate your interest and information. Times
being as they are, I guess we may have missed Scott.

Douglas

“Richard R. Kramer” wrote:

I am of the firm opinion that these won’t work. I had talked
to Scott at Digi (their QNX support guy) and he was of that
opinion. It will need a driver to sort out the real ports, as
I recall.

Richard

Douglas Barker wrote:

I am having problems getting a DIGI ClassicBoard (PCI) running. DIGI support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that QNX support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128 bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only) causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and “stty -a
/dev/digi1” shows “normal” conditions for a serial port. When I qtalk to the
port and check it with a loop back tester, I get no response suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to installing any
DIGI ClassicBoards. We have been successfully launching Connectech boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are moving to the
DIGI card because we need world wide access and PCI interface. Please let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: > support@pcauto.com
Ontario, Canada, N2J 3Z4

Digi does have another PCI card that has a processor on board
for which there is a driver (their generic QNX/Digi driver). I
think it’s the Xe.


Douglas Barker wrote:

I checked back with Digi and their support staff indicate that there is no Scott in
support (must have moved on to greener pastures). Their answer is “it MAY work under
QNX” BUT they “don’t supply the drivers and don’t know if it does work”. The support
staff indicate that ONLY QNX can give the definitive answer on this.

Thanks for the input Richard. We appreciate your interest and information. Times
being as they are, I guess we may have missed Scott.

Douglas

“Richard R. Kramer” wrote:

I am of the firm opinion that these won’t work. I had talked
to Scott at Digi (their QNX support guy) and he was of that
opinion. It will need a driver to sort out the real ports, as
I recall.

Richard

Douglas Barker wrote:

I am having problems getting a DIGI ClassicBoard (PCI) running. DIGI support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that QNX support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128 bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only) causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and “stty -a
/dev/digi1” shows “normal” conditions for a serial port. When I qtalk to the
port and check it with a loop back tester, I get no response suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to installing any
DIGI ClassicBoards. We have been successfully launching Connectech boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are moving to the
DIGI card because we need world wide access and PCI interface. Please let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: > support@pcauto.com
Ontario, Canada, N2J 3Z4

Do you know the Digi part# of the board?

-Glenn Sherman

“Douglas Barker” <dougb@pcauto.com> wrote in message
news:3ACB339C.3C611796@pcauto.com

I checked back with Digi and their support staff indicate that there is no
Scott in
support (must have moved on to greener pastures). Their answer is “it MAY
work under
QNX” BUT they “don’t supply the drivers and don’t know if it does work”.
The support
staff indicate that ONLY QNX can give the definitive answer on this.

Thanks for the input Richard. We appreciate your interest and
information. Times
being as they are, I guess we may have missed Scott.

Douglas

“Richard R. Kramer” wrote:

I am of the firm opinion that these won’t work. I had talked
to Scott at Digi (their QNX support guy) and he was of that
opinion. It will need a driver to sort out the real ports, as
I recall.

Richard

Douglas Barker wrote:

I am having problems getting a DIGI ClassicBoard (PCI) running. DIGI
support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that QNX
support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows
this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128
bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only)
causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and
“stty -a
/dev/digi1” shows “normal” conditions for a serial port. When I
qtalk to the
port and check it with a loop back tester, I get no response
suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to
installing any
DIGI ClassicBoards. We have been successfully launching Connectech
boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are
moving to the
DIGI card because we need world wide access and PCI interface. Please
let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: > support@pcauto.com
Ontario, Canada, N2J 3Z4
\

Dear QNX Serial I/O Customers;

Please note that Connect Tech does have PCI serial I/O cards that support
QNX4.xx and Neutrino and our products are distributed world wide. Please
check out our web page ( www.connecttech.com ) for more detailed
information.

Yours truly;

\

Adrian Stickland
Connect Tech Inc.
Tel: 1-800-426-8979; 519-836-1291 ext. 228
Fax: 519-836-4878
Email: adrian@connecttech.com
Web: www.connecttech.com

Providing Industrial Strength Communications Since 1985
“Glenn Sherman” <gsherman@nospam.m20.net> wrote in message
news:9ai3pm$i3f$1@inn.qnx.com

Do you know the Digi part# of the board?

-Glenn Sherman

“Douglas Barker” <> dougb@pcauto.com> > wrote in message
news:> 3ACB339C.3C611796@pcauto.com> …
I checked back with Digi and their support staff indicate that there is
no
Scott in
support (must have moved on to greener pastures). Their answer is “it
MAY
work under
QNX” BUT they “don’t supply the drivers and don’t know if it does work”.
The support
staff indicate that ONLY QNX can give the definitive answer on this.

Thanks for the input Richard. We appreciate your interest and
information. Times
being as they are, I guess we may have missed Scott.

Douglas

“Richard R. Kramer” wrote:

I am of the firm opinion that these won’t work. I had talked
to Scott at Digi (their QNX support guy) and he was of that
opinion. It will need a driver to sort out the real ports, as
I recall.

Richard

Douglas Barker wrote:

I am having problems getting a DIGI ClassicBoard (PCI) running.
DIGI
support
reports that it SHOULD(?!?) run with Dev32.ser but indicated that
QNX
support
was the place to get an answer.

OK, here is the configuration, show_pci shows no conflicts and shows
this for
the board:
Vendor ID = 114fh
Device ID = 29h
PCI index = 0h
Class Code = 8078000h Communication (Other 128) ProgIF=0
Revision ID = 2h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 280h
Command Reg = 3h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 8h un-cacheable
Base Address = MEM@e4800000h,32bit length 128 IO@b400h length 128
bytes
IO@b000h length 256 bytes MEM@e4000000h,32bit length 256
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Launching the device with:
Dev.ser -Ndigi -b38400 b400,10 & (to get first port working only)
causes a
kernel fault
Dev.ser -Ndigi -b38400 b000,10 & gives a listing /dev/digi1 and
“stty -a
/dev/digi1” shows “normal” conditions for a serial port. When I
qtalk to the
port and check it with a loop back tester, I get no response
suggesting that I
am not communicating with the device

I have reviewed the support pages and can find no reference to
installing any
DIGI ClassicBoards. We have been successfully launching Connectech
boards
including the DFlex4/8 cards using Dev.ser for 10 years+. We are
moving to the
DIGI card because we need world wide access and PCI interface.
Please
let me
know what I have missed.

Thanks

Douglas M. Barker (800) 387-4876 (toll free)
Software Support Engineer (519) 888-9304 (voice)
PC Automation Inc. (519) 888-9085 (fax)
925 Erb St. W., Waterloo email: > support@pcauto.com
Ontario, Canada, N2J 3Z4


\

Previously, Glenn Sherman wrote in qdn.public.qnx4:

Do you know the Digi part# of the board?

-Glenn Sherman

“Douglas Barker” <> dougb@pcauto.com> > wrote in message
news:> 3ACB339C.3C611796@pcauto.com> …
I checked back with Digi and their support staff indicate that
there is no Scott in support (must have moved on to greener
pastures). Their answer is “it MAY work under QNX” BUT they
“don’t supply the drivers and don’t know if it does work”.
The support staff indicate that ONLY QNX can give the definitive
answer on this.

When I talked to Digi some time ago, they admitted that their QNX4
driver was written by a summer student, and he was not necessarily
available back then, and they didn’t know how much longer they would
have access to him. At one point I think Jeff Page wrote a driver as
well, but he is no longer involved with QNX (the operating system) as
far as I know, so there’s no help there.

If you have a choice of boards, look at ConnectTech. I’ve never heard
a single complaint about their QNX support, and they actually do
have qualified people on staff to deal with QNX issues.

Cheers,
Andrew

Ahem. Not to start any wars, here, but to set things straight, as
I know them, at least:

  1. We use Connecttech and Digiboard products. They both work fine.
  2. The original Digi driver for 4.0-4.22 was written by a “real
    programmer”. The driver for 4.23 was started by a young fellow who
    got it mostly right.
  3. The recent driver was written by another “real programmer” who
    is an associate of the first fellow above, and their web site is still
    up and running. The driver works well.
  4. As far as I can tell, Connectech does their software development
    inhouse.

Richard

Andrew Thomas wrote:

Previously, Glenn Sherman wrote in qdn.public.qnx4:
Do you know the Digi part# of the board?

-Glenn Sherman

“Douglas Barker” <> dougb@pcauto.com> > wrote in message
news:> 3ACB339C.3C611796@pcauto.com> …
I checked back with Digi and their support staff indicate that
there is no Scott in support (must have moved on to greener
pastures). Their answer is “it MAY work under QNX” BUT they
“don’t supply the drivers and don’t know if it does work”.
The support staff indicate that ONLY QNX can give the definitive
answer on this.

When I talked to Digi some time ago, they admitted that their QNX4
driver was written by a summer student, and he was not necessarily
available back then, and they didn’t know how much longer they would
have access to him. At one point I think Jeff Page wrote a driver as
well, but he is no longer involved with QNX (the operating system) as
far as I know, so there’s no help there.

If you have a choice of boards, look at ConnectTech. I’ve never heard
a single complaint about their QNX support, and they actually do
have qualified people on staff to deal with QNX issues.

Cheers,
Andrew

Previously, Richard R. Kramer wrote in qdn.public.qnx4:

Ahem. Not to start any wars, here, but to set things straight, as
I know them, at least:

Fair enough. Thanks for the clarification. I guess my information
was just out of date.

Andrew