|
Michael Schanz
04/11/2008 7:50 AM
post6663
|
I'm trying to compile network driver source code (a Davicom DM9102 network driver) for Intel X86. The source code was
provided by the chip vendor. Unfortunately, the build process fails, because it seems that some required components are
missing. In particular, the file netdriver.mk, which is referenced by the makefile, doesn't exist in my environment. My
system environment is based on the QNX 4.25 Product Suite July 2003. Are there additional components, for instance a
dedicated Network DDK, which are required to successfully compile a network driver for QNX 4.25? If no, are there any
other ideas what's wrong in my setup? Thanks a lot.
|
|
|
|
|
|
Mario Charest
04/11/2008 2:39 PM
post6686
|
> I'm trying to compile network driver source code (a Davicom DM9102 network
> driver) for Intel X86. The source code was provided by the chip vendor.
> Unfortunately, the build process fails, because it seems that some required
> components are missing. In particular, the file netdriver.mk, which is
> referenced by the makefile, doesn't exist in my environment. My system
> environment is based on the QNX 4.25 Product Suite July 2003. Are there
> additional components, for instance a dedicated Network DDK, which are
> required to successfully compile a network driver for QNX 4.25? If no, are
> there any other ideas what's wrong in my setup? Thanks a lot.
Are you sure this is not for QNX6?
If it's for QNX4 then in orther to provide you with this they should have "in theory" get you to sign an NDA.
QSS never released a network DDK for QNX4. In fact it's been a very well kept secret, and only a selected few got the
information required to write a network driver for QNX4.
|
|
|
|
|
|
Michael Schanz
04/14/2008 3:51 AM
post6713
|
Well, I see. The driver is really for QNX4. My intention is not to write a network driver from scratch, but rather to
fix a chip revision problem. But it seems to be impossible without the DDK (I'm not going to dig into the binary ;-).
Unfortunately, it's neither an option to switch to QNX6 nor to go back to an elder chip revision. Anyway, thank you very
much for the answer.
|
|
|
|
|
|
Hugh Brown
04/14/2008 7:54 AM
post6719
|
Well if you let us know what you are wanting to do, we can add the device to
the driver and post an experimental version of the driver for you to test.
-----Original Message-----
From: Michael Schanz [mailto:michael.schanz@congatec.com]
Sent: Monday, April 14, 2008 3:51 AM
To: qnx4-community
Subject: Re: QNX4 Network DDK?
Well, I see. The driver is really for QNX4. My intention is not to write a
network driver from scratch, but rather to fix a chip revision problem. But
it seems to be impossible without the DDK (I'm not going to dig into the
binary ;-). Unfortunately, it's neither an option to switch to QNX6 nor to
go back to an elder chip revision. Anyway, thank you very much for the
answer.
_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post6713
|
|
|
|
|
|
Michael Schanz
|
Re: RE: QNX4 Network DDK?
|
|
Michael Schanz
04/15/2008 9:19 AM
post6787
|
Re: RE: QNX4 Network DDK?
Hi Hugh,
I'm trying to get a Davicom DM9102DE chip working under QNX4. The QNX4 driver (Net.davicom), which was originally
provided by the chip vendor, fails with a "cannot decode SROM" failure. This driver is claimed to work properly with a
DM9102A chip (I can't verify this, because I don't have a NIC based on this revision). In the meantime, the local QNX
support in Germany also provided an experimental version of the Net.dm9102 driver (cksum: 608562689), thanks a lot!
Unfortunately, this driver also doesn't seem to work: after executing Net.dm9102, the Link-LED flickers and after about
10s, the driver terminates (without any output messages, also the -v option doesn't show any output). As far as we know,
the layout of the Ethernet eeprom has changed from rev. A to rev. D, which certainly could be the reason for the
misbehaviour.
|
|
|
|
|
|
Hugh Brown
|
RE: RE: QNX4 Network DDK?
|
|
Hugh Brown
04/15/2008 9:27 AM
post6789
|
RE: RE: QNX4 Network DDK?
If you start the driver with '-v' it should at least display something. Does
it not display "I/O port base ...."? If you can let me know what it displays
on the screen, that might be a help. Also the output from 'show_pci -v'
would help.
-----Original Message-----
From: Michael Schanz [mailto:michael.schanz@congatec.com]
Sent: Tuesday, April 15, 2008 9:19 AM
To: qnx4-community
Subject: Re: RE: QNX4 Network DDK?
Hi Hugh,
I'm trying to get a Davicom DM9102DE chip working under QNX4. The QNX4
driver (Net.davicom), which was originally provided by the chip vendor,
fails with a "cannot decode SROM" failure. This driver is claimed to work
properly with a DM9102A chip (I can't verify this, because I don't have a
NIC based on this revision). In the meantime, the local QNX support in
Germany also provided an experimental version of the Net.dm9102 driver
(cksum: 608562689), thanks a lot! Unfortunately, this driver also doesn't
seem to work: after executing Net.dm9102, the Link-LED flickers and after
about 10s, the driver terminates (without any output messages, also the -v
option doesn't show any output). As far as we know, the layout of the
Ethernet eeprom has changed from rev. A to rev. D, which certainly could be
the reason for the misbehaviour.
_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post6787
|
|
|
|
|
|
Michael Schanz
|
Re: RE: RE: QNX4 Network DDK?
|
|
Michael Schanz
04/16/2008 3:43 AM
post6867
|
Re: RE: RE: QNX4 Network DDK?
Hi,
find a dump of show_pci as attachement. Starting the experimental driver with "Net.dm9102 -v" really doesn't show any
output on screen. It appears strange to me, I would at least expect something like "DriverInit: Unable to locate adapter
" or an error message. However, the Link-LED flickers for a very short time when starting the driver. From my experience
, that means, that at least the chip has been detected and the diver initialization has been started.
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: QNX4 Network DDK?
|
|
Hugh Brown
04/16/2008 7:51 AM
post6871
|
RE: RE: RE: QNX4 Network DDK?
Are you staring the driver from within Photon? You will only see screen
display if you start the driver in text mode. The show_pci output doesn't
show anything strange, so if you could please start the driver in verbose
mode in text mode and let me know what it displays on the screen, it would
be helpful. Please start the driver as 'Net.dm9102 -vvv'.
-----Original Message-----
From: Michael Schanz [mailto:michael.schanz@congatec.com]
Sent: Wednesday, April 16, 2008 3:44 AM
To: qnx4-community
Subject: Re: RE: RE: QNX4 Network DDK?
Hi,
find a dump of show_pci as attachement. Starting the experimental driver
with "Net.dm9102 -v" really doesn't show any output on screen. It appears
strange to me, I would at least expect something like "DriverInit: Unable to
locate adapter" or an error message. However, the Link-LED flickers for a
very short time when starting the driver. From my experience, that means,
that at least the chip has been detected and the diver initialization has
been started.
_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post6867
|
|
|
|
|
|
Michael Schanz
|
Re: RE: RE: RE: QNX4 Network DDK?
|
|
Michael Schanz
04/16/2008 9:12 AM
post6893
|
Re: RE: RE: RE: QNX4 Network DDK?
Oops, I'm really sorry. I wasn't aware that there's a difference. Starting from the text console, the driver reports: "
Net.dm9102: INITIALIZATION ERROR 1"
|
|
|
|
|
|
Michael Schanz
|
Re: RE: RE: RE: QNX4 Network DDK?
|
|
Michael Schanz
04/16/2008 9:15 AM
post6894
|
Re: RE: RE: RE: QNX4 Network DDK?
...
Net.dm9102: proc_fun = e0:0a69
Net.dm9102: vidbuf_inuse = e8:4bc4
devn-dm9102: mii PHY address=1
I/O port base ....... 0xde00
Interrupt ...... 7
Net.dm9102: INITIALIZATION ERROR 1
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: QNX4 Network DDK?
|
|
Hugh Brown
04/16/2008 9:21 AM
post6895
|
RE: RE: RE: RE: QNX4 Network DDK?
Well INITIALIZATION ERROR 1 means that the driver cannot find Net. Are you
running 'Net &'?
-----Original Message-----
From: Michael Schanz [mailto:michael.schanz@congatec.com]
Sent: Wednesday, April 16, 2008 9:16 AM
To: qnx4-community
Subject: Re: RE: RE: RE: QNX4 Network DDK?
...
Net.dm9102: proc_fun = e0:0a69
Net.dm9102: vidbuf_inuse = e8:4bc4
devn-dm9102: mii PHY address=1
I/O port base ....... 0xde00
Interrupt ...... 7
Net.dm9102: INITIALIZATION ERROR 1
_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post6894
|
|
|
|
|
|
Michael Schanz
|
Re: RE: RE: RE: RE: QNX4 Network DDK?
|
|
Michael Schanz
04/16/2008 10:39 AM
post6916
|
Re: RE: RE: RE: RE: QNX4 Network DDK?
My god, I made myself a complete fool! What a shame! After loading "Net &", also the driver loaded correctly. Many
thanks to you, Hugh, the community and Mr. Mathew from the QNX support team in Germany for your excellent support! I
really appreciated your help. Just one final question: since the driver is experimental, is there any chance to get a
released version?
|
|
|
|
|
|
Hugh Brown
|
RE: RE: RE: RE: RE: QNX4 Network DDK?
|
|
Hugh Brown
04/16/2008 10:55 AM
post6918
|
RE: RE: RE: RE: RE: QNX4 Network DDK?
Good news!
There should be an official version in the QNX4 network driver patch on our
web site.
-----Original Message-----
From: Michael Schanz [mailto:michael.schanz@congatec.com]
Sent: Wednesday, April 16, 2008 10:40 AM
To: qnx4-community
Subject: Re: RE: RE: RE: RE: QNX4 Network DDK?
My god, I made myself a complete fool! What a shame! After loading "Net &",
also the driver loaded correctly. Many thanks to you, Hugh, the community
and Mr. Mathew from the QNX support team in Germany for your excellent
support! I really appreciated your help. Just one final question: since the
driver is experimental, is there any chance to get a released version?
_______________________________________________
QNX4 Community Support
http://community.qnx.com/sf/go/post6916
|
|
|
|
|
|
