Menu
▾
▴
linux-gpib-general — linux-gpib package mailing list
You can subscribe to this list here.
| 2002 |
Jan
(2) |
Feb
(2) |
Mar
(22) |
Apr
(24) |
May
(7) |
Jun
(44) |
Jul
(16) |
Aug
(2) |
Sep
(13) |
Oct
(11) |
Nov
(19) |
Dec
(25) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(16) |
Feb
(27) |
Mar
(5) |
Apr
(20) |
May
(17) |
Jun
(34) |
Jul
(29) |
Aug
(22) |
Sep
(25) |
Oct
(11) |
Nov
(13) |
Dec
(18) |
| 2004 |
Jan
(25) |
Feb
(22) |
Mar
(33) |
Apr
(15) |
May
(37) |
Jun
(15) |
Jul
(12) |
Aug
(22) |
Sep
(18) |
Oct
(45) |
Nov
(19) |
Dec
(30) |
| 2005 |
Jan
(31) |
Feb
(35) |
Mar
(27) |
Apr
(22) |
May
(9) |
Jun
(13) |
Jul
(13) |
Aug
(9) |
Sep
(25) |
Oct
(25) |
Nov
(12) |
Dec
(20) |
| 2006 |
Jan
(14) |
Feb
(16) |
Mar
(17) |
Apr
(8) |
May
(7) |
Jun
(20) |
Jul
(21) |
Aug
(12) |
Sep
(19) |
Oct
(6) |
Nov
(23) |
Dec
(15) |
| 2007 |
Jan
(13) |
Feb
(14) |
Mar
(24) |
Apr
(21) |
May
(9) |
Jun
(5) |
Jul
(7) |
Aug
(9) |
Sep
(21) |
Oct
(5) |
Nov
(30) |
Dec
(9) |
| 2008 |
Jan
(15) |
Feb
(18) |
Mar
(4) |
Apr
(11) |
May
(3) |
Jun
(14) |
Jul
(12) |
Aug
(1) |
Sep
(31) |
Oct
(10) |
Nov
(9) |
Dec
(2) |
| 2009 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(2) |
May
(7) |
Jun
(22) |
Jul
(5) |
Aug
(1) |
Sep
(26) |
Oct
(13) |
Nov
(2) |
Dec
(10) |
| 2010 |
Jan
(29) |
Feb
(2) |
Mar
(23) |
Apr
(9) |
May
(7) |
Jun
(8) |
Jul
(4) |
Aug
(4) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(9) |
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(25) |
May
(2) |
Jun
(19) |
Jul
(6) |
Aug
(4) |
Sep
(9) |
Oct
(3) |
Nov
(8) |
Dec
(7) |
| 2012 |
Jan
(5) |
Feb
(10) |
Mar
(10) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
(18) |
Dec
(10) |
| 2013 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(4) |
Jun
|
Jul
(26) |
Aug
(13) |
Sep
(24) |
Oct
(2) |
Nov
(1) |
Dec
(4) |
| 2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
(2) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
(5) |
| 2015 |
Jan
(1) |
Feb
(8) |
Mar
(7) |
Apr
(30) |
May
(3) |
Jun
(4) |
Jul
|
Aug
(7) |
Sep
(6) |
Oct
(13) |
Nov
(9) |
Dec
(2) |
| 2016 |
Jan
|
Feb
(7) |
Mar
(11) |
Apr
(6) |
May
(2) |
Jun
(16) |
Jul
(2) |
Aug
(6) |
Sep
(2) |
Oct
(2) |
Nov
(2) |
Dec
(7) |
| 2017 |
Jan
(9) |
Feb
(25) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(14) |
Sep
(23) |
Oct
(3) |
Nov
|
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
(6) |
Apr
(4) |
May
(11) |
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
(3) |
Nov
(20) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(2) |
Mar
(9) |
Apr
(7) |
May
(2) |
Jun
(14) |
Jul
(17) |
Aug
(8) |
Sep
(9) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
| 2020 |
Jan
(5) |
Feb
(13) |
Mar
|
Apr
(6) |
May
|
Jun
(7) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(11) |
Dec
(4) |
| 2021 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
(4) |
May
(7) |
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
(8) |
Nov
|
Dec
(3) |
| 2022 |
Jan
(5) |
Feb
(13) |
Mar
|
Apr
(3) |
May
(4) |
Jun
(4) |
Jul
|
Aug
(10) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
(4) |
| 2023 |
Jan
(10) |
Feb
(5) |
Mar
|
Apr
|
May
(5) |
Jun
(4) |
Jul
(6) |
Aug
(4) |
Sep
(28) |
Oct
(8) |
Nov
(2) |
Dec
(1) |
| 2024 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
(3) |
Jun
(1) |
Jul
(10) |
Aug
(6) |
Sep
(3) |
Oct
|
Nov
(9) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: frank m. h. <fm...@st...> - 2002-06-20 23:48:04
|
On Thu, 20 Jun 2002, Mitchell Ferschweiler wrote: > Turning off DMA fixed the problem. Writing and reading > both work fine. > > When do modification to the interfaces in > /etc/gpib.conf file take effect? Do I need to reboot > my computer, reload the modules? > At the moment, it happens whenever the driver module goes from unused to used (as shown by lsmod). So stopping and restarting your program would probably be enough. Frank |
|
From: frank m. h. <fm...@st...> - 2002-06-20 23:36:08
|
On Wed, 19 Jun 2002, Mitchell Ferschweiler wrote: > I also have a PCII/PCIIA card. When I configure it to > use the same dma, irq, and io address as my PCIIA, and > try to do ibtest, it results in the command bytes > error: > > enter primary address for device (not interface board) > [0-30]: 26 > trying to open pad = 26 on /dev/gpib0 ... > clearing device.. > gpib clear error > ibsta = 0x130 > iberr= 0 EDVR > ibcnt = 0 > > Both of my tests were done with the CVS source. > > I also have a PCMCIA National Instruments card I am > interested in using with linux. Is there any support > or planned support for it? > > Thanks, > Mitchell > It looks like it's time for me to add a proper compile-time option for enabling verbose debugging output. I should be able to put that in over the weekend, and then we can debug the pc2a dma and pc2a command problems. NI pcmcia support is probably doable, if you are willing to do the testing. Frank |
|
From: Mitchell F. <mit...@ya...> - 2002-06-20 15:11:20
|
Turning off DMA fixed the problem. Writing and reading both work fine. When do modification to the interfaces in /etc/gpib.conf file take effect? Do I need to reboot my computer, reload the modules? Thanks, Mitchell --- frank mori hess <fm...@st...> wrote: > Yikes. You could try turning off dma (set it to > zero in your config > file). I usually have access to a pc2a card, > unfortunately I don't have > access to any gpib cards this summer. > > Frank > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: Mitchell F. <mit...@ya...> - 2002-06-20 00:56:27
|
I also have a PCII/PCIIA card. When I configure it to use the same dma, irq, and io address as my PCIIA, and try to do ibtest, it results in the command bytes error: enter primary address for device (not interface board) [0-30]: 26 trying to open pad = 26 on /dev/gpib0 ... clearing device.. gpib clear error ibsta = 0x130 iberr= 0 EDVR ibcnt = 0 Both of my tests were done with the CVS source. I also have a PCMCIA National Instruments card I am interested in using with linux. Is there any support or planned support for it? Thanks, Mitchell --- frank mori hess <fm...@st...> wrote: > > > On Wed, 19 Jun 2002, Mitchell Ferschweiler wrote: > > > Hello, > > > > I have a National Instruments PCIIa card. When I > try > > and write a string to a device (HP 3456A Digital > > Voltmeter), it freezes my computer. The > transaction is > > complete, the instrument does what the command > asked, > > but the computer completely stops responding > (can't > > switch consoles, no response from the mouse, > keyboard, > > etc..) > > Yikes. You could try turning off dma (set it to > zero in your config > file). I usually have access to a pc2a card, > unfortunately I don't have > access to any gpib cards this summer. > > Frank > > > ---------------------------------------------------------------------------- > Bringing you mounds of > caffeinated joy > >>> http://thinkgeek.com/sf > <<< > > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
|
From: frank m. h. <fm...@st...> - 2002-06-19 23:41:42
|
On Wed, 19 Jun 2002, Mitchell Ferschweiler wrote: > Hello, > > I have a National Instruments PCIIa card. When I try > and write a string to a device (HP 3456A Digital > Voltmeter), it freezes my computer. The transaction is > complete, the instrument does what the command asked, > but the computer completely stops responding (can't > switch consoles, no response from the mouse, keyboard, > etc..) Yikes. You could try turning off dma (set it to zero in your config file). I usually have access to a pc2a card, unfortunately I don't have access to any gpib cards this summer. Frank |
|
From: Mitchell F. <mit...@ya...> - 2002-06-19 22:56:31
|
Hello,
I have a National Instruments PCIIa card. When I try
and write a string to a device (HP 3456A Digital
Voltmeter), it freezes my computer. The transaction is
complete, the instrument does what the command asked,
but the computer completely stops responding (can't
switch consoles, no response from the mouse, keyboard,
etc..)
Reading from the same device works just fine.
/etc/gpib.conf:
interface {
minor = 0
board_type = pcIIa
pad = 0
sad = 0
timeout = 3s
eos = 0x0a
set-reos yes
set-bin no
base = 0x02E1
irq = 7
dma = 1
master yes
}
ibtest output:
"
You can (r)ead or (w)rite a string to your device or
(q)uit: w
enter a string to send to your device: F2
sending string: F2
"
Mitchell
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
|
|
From: <tim...@ex...> - 2002-06-19 16:13:30
|
Hello, I grabbed the source from CVS, installed, and got the same results: [root@speedy root]# /usr/local/src/linux-gpib-3.1.4/examples/ibtest enter primary address for device (not interface board) [0-30]: 26 trying to open pad = 26 on /dev/gpib0 ... clearing device.. gpib clear error ibsta = 0x130 iberr= 0 EDVR ibcnt = 0 Jun 19 08:57:36 speedy kernel: gpib command timed out Jun 19 08:57:36 speedy kernel: error writing gpib command bytes Anything else we can try? Thanks again, Tim Holmes ------------------------------------------------ Join Excite! - http://www.excite.com The most personalized portal on the Web! |
|
From: frank m. h. <fm...@st...> - 2002-06-17 15:59:34
|
On Mon, 17 Jun 2002, Steve Friend wrote: > I have an NI PCI-GPIB+ board that I would like to use with the linux gpib > software, but the software does not recognize the board. It is looking for > a 0xC801 device id (vs the PCI-GPIB+ device id of 0xc811). Is there any > easy way to configure the software to support the PCI-GPIB+ board? Thanks > for any help. > > You could change the id in driver/tnt4882/tnt4882.h and recompile to see if it works. Let me know how it goes. Frank |
|
From: Steve F. <fr...@dr...> - 2002-06-17 15:32:40
|
I have an NI PCI-GPIB+ board that I would like to use with the linux gpib software, but the software does not recognize the board. It is looking for a 0xC801 device id (vs the PCI-GPIB+ device id of 0xc811). Is there any easy way to configure the software to support the PCI-GPIB+ board? Thanks for any help. Steve Friend 617-258-2234 phone 617-258-3858 fax |
|
From: <tim...@ex...> - 2002-06-15 13:43:18
|
Never mind. I figured it out. (First time doing CVS).
I'll try it on Monday.
Tim
--- On Sat 06/15, wrote:
From: [mailto: tim...@ex...]
To: fm...@st...
Cc: lin...@li...
Date: Sat 06/15
Subject: Re: [Linux-gpib-general] linux-gpib 3.1.4
>
> OK, what module do I specify when I do the CVS?
>
> Tim
>
>
>
>
> --- On Sat 06/15, frank mori hess wrote:
> From: frank mori hess [mailto: fm...@st...]
> To: tim...@ex...,ho...@uf...
> Cc: lin...@li...
> Date: Sat 06/15
> Subject: Re: [Linux-gpib-general] linux-gpib 3.1.4
>
> >
> >
> > On Thu, 13 Jun 2002, wrote:
> >
> > >
> > > I have now installed RedHat 7.3 and linux-gpib-3.1.4. The board
> now
> > > talks to the device, but the device doesn't understand. I have
> > > included the pertinent info below. Any tips greatly
> appreciated.
> > >
> >
> > I think I have the problem with sending command bytes fixed in cvs
> now.
> > Would you try it and tell me if it helps?
> >
> > Frank
> >
> >
> >
> > > *********************************************************
> > > This is logged to the system log:
> > >
> > > Jun 13 14:56:37 speedy kernel: gpib: registered pcII interface
> > > Jun 13 14:56:37 speedy kernel: gpib: registered pcIIa interface
> > > Jun 13 14:56:48 speedy kernel: error writing gpib command bytes
> > >
> >
> >
> > _______________________________________________________________
> >
> > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > August 25-28 in Las Vegas -
> > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> >
> > _______________________________________________
> > Linux-gpib-general mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> >
>
> ------------------------------------------------
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -
> http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
------------------------------------------------
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
|
|
From: <tim...@ex...> - 2002-06-15 13:20:27
|
OK, what module do I specify when I do the CVS?
Tim
--- On Sat 06/15, frank mori hess wrote:
From: frank mori hess [mailto: fm...@st...]
To: tim...@ex...,ho...@uf...
Cc: lin...@li...
Date: Sat 06/15
Subject: Re: [Linux-gpib-general] linux-gpib 3.1.4
>
>
> On Thu, 13 Jun 2002, wrote:
>
> >
> > I have now installed RedHat 7.3 and linux-gpib-3.1.4. The board now
> > talks to the device, but the device doesn't understand. I have
> > included the pertinent info below. Any tips greatly appreciated.
> >
>
> I think I have the problem with sending command bytes fixed in cvs now.
> Would you try it and tell me if it helps?
>
> Frank
>
>
>
> > *********************************************************
> > This is logged to the system log:
> >
> > Jun 13 14:56:37 speedy kernel: gpib: registered pcII interface
> > Jun 13 14:56:37 speedy kernel: gpib: registered pcIIa interface
> > Jun 13 14:56:48 speedy kernel: error writing gpib command bytes
> >
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -
> http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>
------------------------------------------------
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
|
|
From: frank m. h. <fm...@st...> - 2002-06-15 04:23:25
|
On Thu, 13 Jun 2002, wrote: > > I have now installed RedHat 7.3 and linux-gpib-3.1.4. The board now > talks to the device, but the device doesn't understand. I have > included the pertinent info below. Any tips greatly appreciated. > I think I have the problem with sending command bytes fixed in cvs now. Would you try it and tell me if it helps? Frank > ********************************************************* > This is logged to the system log: > > Jun 13 14:56:37 speedy kernel: gpib: registered pcII interface > Jun 13 14:56:37 speedy kernel: gpib: registered pcIIa interface > Jun 13 14:56:48 speedy kernel: error writing gpib command bytes > |
|
From: <tim...@ex...> - 2002-06-13 22:17:02
|
I have now installed RedHat 7.3 and linux-gpib-3.1.4. The board now talks to the device, but the device doesn't understand. I have included the pertinent info below. Any tips greatly appreciated.
Thanks,
Tim Holmes
[root@speedy root]# /usr/local/src/linux-gpib-3.1.4/examples/ibtest
enter primary address for device (not interface board) [0-30]: 26
trying to open pad = 26 on /dev/gpib0 ...
clearing device..
gpib clear error
ibsta = 0x130
iberr= 0 EDVR
ibcnt = 0
*********************************************************
This is logged to the system log:
Jun 13 14:56:37 speedy kernel: gpib: registered pcII interface
Jun 13 14:56:37 speedy kernel: gpib: registered pcIIa interface
Jun 13 14:56:48 speedy kernel: error writing gpib command bytes
[root@speedy root]# lsmod
Module Size Used by Not tainted
pc2-gpib 4416 0 (unused)
nec7210 11264 0 [pc2-gpib]
gpib-common 15872 0 [pc2-gpib]
soundcore 6692 0 (autoclean)
binfmt_misc 7556 1
autofs 12164 0 (autoclean) (unused)
3c59x 28520 1
ipchains 43560 14
nls_iso8859-1 3488 1 (autoclean)
nls_cp437 5120 1 (autoclean)
vfat 12092 1 (autoclean)
fat 37400 0 (autoclean) [vfat]
ext3 67136 6
jbd 49400 6 [ext3]
aic7xxx 124768 8
sd_mod 12864 16
scsi_mod 108576 2 [aic7xxx sd_mod]
*************************************
/etc/gpib.conf:
interface {
minor = 0
board_type = pcII
pad = 0
sad = 0
timeout = 3s
eos = 0x0a
set-reos yes
set-bin no
base = 0x2b8
irq = 5
dma = 3
master yes
}
device {
name = bk
minor = 0
pad = 26
sad = 0
}
------------------------------------------------
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
|
|
From: Jean-Baptiste D. <jea...@un...> - 2002-06-12 13:29:57
|
Rolf Niepraschk a écrit : > > Is it possible to use the Linux-gpib driver with LabView for Linux? What > can I do? Thanks in advance, > > Rolf Niepraschk Hi, I am wondering the same question, but haven't seen any reply on the list. If somebody has sent a private reply to Rolf, would he please re-send a copy to the list? Thanks a lot. JB -- Jean-Baptiste Daban, CNRS UMR5831 Imagerie Géophysique BP 1155 - 64013 Pau cedex - France Tel:(33) 5 59 80 83 65 Fax:(33) 5 59 92 31 86 mailto:jea...@un... http://www.univ-pau.fr/~jbdaban |
|
From: Rolf N. <Rol...@pt...> - 2002-06-11 11:43:36
|
Has anyone used the Linux-gpib driver with LabView for Linux? What can I do? ...Rolf -- || Rolf Niepraschk c/o Physikalisch-Technische Bundesanstalt || || Abbestr. 2-12; D-10587 Berlin, Germany || || Tel/Fax: ++49-30-3481-316/490, email: nie...@pt... || |
|
From: Rolf N. <Rol...@pt...> - 2002-06-11 11:30:43
|
Is it possible to use the Linux-gpib driver with LabView for Linux? What
can I do? Thanks in advance,
Rolf Niepraschk
--
|| Rolf Niepraschk c/o Physikalisch-Technische Bundesanstalt ||
|| Abbestr. 2-12; D-10587 Berlin, Germany ||
|| Tel/Fax: ++49-30-3481-316/490, email: nie...@pt... ||
|
|
From: Ed S. <ed...@ne...> - 2002-06-03 16:08:40
|
On Sat, 1 Jun 2002, frank mori hess wrote:
>
>
> On Wed, 29 May 2002, Ed Sternin wrote:
>
> > Unfortunately, all my efforts with HP/Agilent to get the information about
> > the OTHER 24 i/o locations mapped out have failed so far (the PnP tools
> > report that the card wants 32 i/o locations, while 9914 only needs 8
> > registers). It is also not clear where/how/if DMA mode is to be enabled,
> > if supported.
>
> It's a 16 bit card, it's possible it uses 16 io addresses for the 8
> tms9914 registers, using 16 bits for each 9914 register (and wasting the
> upper 8 bits). Have you tried using outw/inw instead of outb/inb? There
> also should be additional registers for controlling the board's fifo.
I assumed as much. I tried to use the elementary write/reads to see if
things work. For example, set the gpib address, write out a byte, etc.
The simple test9914.c program (inspired by the NI documentation for
NAT9914) is on the web site, as well as the results of running it.
At first I thought that everything was working, at all 4 possible offsets
(+0, +0x08, +0x10, +0x18) but making more elaborate tests reveals that
all of the board's addresses report whatever the last write to it was.
So if I use write/read to verify the setting of an address, it confirms as
if it worked. It looks like there is something HP-ish there, in
front of the 9914. Anyways, see the code.
> I looked at the information you gathered on your web page. How did you
> determine the board uses a tms9914 chip? Without more register-level
Well, the labels on the chips on the board are pretty unequivocal. There
is a Xilinx glue chip, and a 9914.
> information, supporting this board does not look promising. Have you
> contracted HP about getting register level programming documentation for
> the board?
Yes, and they so far just bounced me around. See the quote from TAMS
engineer, also on the Web page. HP was more eager to close the service
call I opened than to answer my question. I will pursue it further, but I
am not holding my breath; my experience with the HP since they became
Agilent has been terrible, and not just on this issue.
Greg Goebel had been helpful in the past, according to Clausi's note on
LLP site, but he's been gone from HP for two years now.
Does anybody else know anything?
------------------------------------------------------------------
Ed Sternin, Physics Dept, Brock U, St.Catharines, Ontario, L2S 3A1
http://www.physics.BrockU.CA/faculty/sternin.html
voice:(905)688-5550x3414 FAX:(905)682-9020 email: ed...@br...
|
|
From: frank m. h. <fm...@st...> - 2002-06-03 00:57:36
|
There is a new linux-gpib tarball available from sourceforge. No major changes, mostly bug fixes that have accumulated since 3.1.3. Frank |
|
From: frank m. h. <fm...@st...> - 2002-06-01 22:05:28
|
On Wed, 29 May 2002, Ed Sternin wrote: > Unfortunately, all my efforts with HP/Agilent to get the information about > the OTHER 24 i/o locations mapped out have failed so far (the PnP tools > report that the card wants 32 i/o locations, while 9914 only needs 8 > registers). It is also not clear where/how/if DMA mode is to be enabled, > if supported. It's a 16 bit card, it's possible it uses 16 io addresses for the 8 tms9914 registers, using 16 bits for each 9914 register (and wasting the upper 8 bits). Have you tried using outw/inw instead of outb/inb? There also should be additional registers for controlling the board's fifo. I looked at the information you gathered on your web page. How did you determine the board uses a tms9914 chip? Without more register-level information, supporting this board does not look promising. Have you contracted HP about getting register level programming documentation for the board? Frank |
|
From: Ed S. <ed...@ne...> - 2002-05-29 16:59:00
|
That's excellent, Frank, thanks a lot. If it's any help, I pulled together all the 9914 and related info onto a single web page, http://www.physics.BrockU.CA/~edik/gpib In particular, there are hard-to-come-by datasheets for TMS9914 and SMJ9914A. I took the old listing of gpib_registers.h (presumably, written as per NI NAT9914 data sheets) and edited it to reflect the true TI 9914, it is posted on the above web page as registers.h. There were only a couple of small changes. Unfortunately, all my efforts with HP/Agilent to get the information about the OTHER 24 i/o locations mapped out have failed so far (the PnP tools report that the card wants 32 i/o locations, while 9914 only needs 8 registers). It is also not clear where/how/if DMA mode is to be enabled, if supported. The HP82335 cards, for which the support supposedly was there in the linux-gpib-2.x.x, were MEMORY-mapped (not io-mapped); there the eight UPPERMOST memory addresses were mapped onto 9914 registers. I tried to scan the entire isapnp-assigned 32-location space for 9914 "signature" or other info, using raw portio, but the results are puzzling: multiple reads in a row never yield the same values, pretty much anywhere in that space, except base+0x09 and base +0x19 which are consistently zero: # isapnp isapnp.conf Board 1 has Identity a9 40 00 18 e8 11 14 f0 22: HWP1411 Serial No 1073748200 [checksum a9] HWP1411/1073748200[0]{Hewlett-Packard HP-IB Interface Card}: Port 0x240; IRQ11 --- Enabled OK # modprobe portio ports='0x240-0x25f' # grep 240 /proc/ioports 0240-025f : portio # ./scan-registers.sh 0x240 = 0x50 0x90 0x8e 0x8f 0x8f 0x8e 0x8f 0x90 0x8e 0x8f 0x242 = 0x8e 0x8d 0x8f 0x8f 0x8e 0x8c 0x8f 0x8d 0x8f 0x8f 0x243 = 0x8f 0x8e 0x8e 0x8f 0x8f 0x8f 0x8f 0x8e 0x8f 0x8f 0x244 = 0x91 0x8f 0x8f 0x8e 0x8e 0x8f 0x8f 0x8f 0x8f 0x8f 0x245 = 0x90 0x8e 0x8f 0x8d 0x8e 0x8e 0x8f 0x8e 0x8f 0x8d 0x246 = 0x8f 0x8c 0x8c 0x8e 0x8e 0x8f 0x8e 0x8f 0x8e 0x8e 0x247 = 0x8e 0x8e 0x8d 0x8e 0x8e 0x8f 0x90 0x8e 0x90 0x8f 0x248 = 0x8f 0x91 0x8f 0x8d 0x8d 0x8e 0x90 0x8e 0x8f 0x8e 0x249 = 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x24A = 0x8e 0x90 0x8e 0x8b 0x8f 0x8e 0x8f 0x8e 0x8f 0x91 0x24B = 0x90 0x8e 0x8f 0x8c 0x90 0x8e 0x8c 0x90 0x8a 0x8f 0x24C = 0x90 0x89 0x90 0x8d 0x8f 0x8e 0x8f 0x8f 0x8e 0x8c 0x24D = 0x8d 0x91 0x8f 0x8f 0x8e 0x90 0x8d 0x8e 0x8d 0x8e 0x24E = 0x90 0x8e 0x90 0x90 0x8e 0x8f 0x8e 0x8e 0x90 0x8f 0x24F = 0x8e 0x90 0x8f 0x90 0x8e 0x8e 0x8e 0x8d 0x8f 0x90 0x250 = 0x92 0x90 0x8e 0x8f 0x8e 0x8e 0x8f 0x8e 0x92 0x8e 0x252 = 0x8f 0x8e 0x8e 0x91 0x8f 0x8e 0x90 0x8f 0x8e 0x8f 0x253 = 0x8d 0x90 0x8e 0x8f 0x8f 0x8d 0x92 0x8f 0x8e 0x90 0x254 = 0x8c 0x91 0x8f 0x8b 0x91 0x8b 0x8e 0x8d 0x8f 0x8f 0x255 = 0x8c 0x92 0x8e 0x8f 0x8e 0x8f 0x8e 0x90 0x8f 0x8f 0x256 = 0x90 0x8f 0x90 0x8f 0x8a 0x90 0x8e 0x8f 0x8f 0x8e 0x257 = 0x90 0x8f 0x90 0x8f 0x8f 0x8c 0x8f 0x8f 0x90 0x8e 0x258 = 0x8f 0x90 0x8e 0x90 0x8c 0x8f 0x8f 0x8f 0x90 0x8f 0x259 = 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x25A = 0x8d 0x8e 0x8e 0x8f 0x8f 0x8d 0x92 0x8e 0x8e 0x90 0x25B = 0x8e 0x94 0x8e 0x8c 0x90 0x90 0x8f 0x8f 0x8f 0x8e 0x25C = 0x8d 0x8e 0x8e 0x8d 0x8f 0x8e 0x8f 0x90 0x8f 0x90 0x25D = 0x91 0x8f 0x8e 0x8f 0x8e 0x8f 0x8d 0x8f 0x8f 0x8e 0x25E = 0x8e 0x8e 0x8f 0x90 0x8e 0x8f 0x8e 0x8e 0x8e 0x8e 0x25F = 0x90 0x8f 0x8f 0x8e 0x8f 0x8f 0x8f 0x8d 0x90 0x8f Perhaps, some magic write needs to happen before reads return meaningful values? So that's where I am stuck. ------------------------------------------------------------------ Ed Sternin, Physics Dept, Brock U, St.Catharines, Ontario, L2S 3A1 http://www.physics.BrockU.CA/faculty/sternin.html voice:(905)688-5550x3414 FAX:(905)682-9020 email: ed...@br... |
|
From: frank m. h. <fm...@st...> - 2002-05-29 03:00:33
|
On Fri, 24 May 2002, Ed Sternin wrote: > Unfortunately, the GPIB card(s) in our lab are the HP82341D, which are the > i/o mapped, PnP ISA cards from HP (Agilent). They use the 9914 chipset, and > work under Win95. > > I had tried to connect to them under "Ziatech" driver under kernel 2.0.16 earlier, > (using linux-gpib-2.04) but failed. I was hoping the new release would include > a driver for this card, but I see you re-configured the driver scheme completely. > In fact, I cannot see which driver in 3.1.3 uses tms9914 at all!? The only driver that uses the tms9914 module is the tnt4882-tms driver. I only made that to test tms9914 support (since the NI chips can be configured to operate in tms9914 compatibility mode). I intended to get the tms9914 boards running, but lost interest due to the chip being quite old and noone had made any requests for it (until now). > Could you help? We are willing to do some coding, but we are not terribly clever > with kernel-level stuff. Perhaps you could give us some pointers? Actually, if you could > add to the driver tree an hp8234x subdirectory, and put a skeleton driver in, and add it > to the list of valid drivers, somewhere in the code, we could then try to figure out > what to do within the driver (hopefully, very little compared to any other ISA/9914-type > driver). I looked at the code structure, and although it is a > major improvement from old versions, I am still quite confused by the relationships > of various pieces, and that's where your help would be most welcome. > I'll try and get a skeleton driver into cvs this weekend. It shouldn't be too bad, as I remember I was able to get basic read/writes working on the NI board using the tms9914 support that is already present. Frank |
|
From: Ed S. <ed...@ne...> - 2002-05-24 18:03:26
|
Dear Frank,
I was most happy to discover that someone has picked up gpib, a great job=
!
After a few snags linux-gpib-3.1.3 compiles and installs fine under my
2.4.5 (Slackware 8.0).
Unfortunately, the GPIB card(s) in our lab are the HP82341D, which are th=
e=20
i/o mapped, PnP ISA cards from HP (Agilent). They use the 9914 chipset, =
and
work under Win95.
I had tried to connect to them under "Ziatech" driver under kernel 2.0.16=
earlier,
(using linux-gpib-2.04) but failed. I was hoping the new release would i=
nclude
a driver for this card, but I see you re-configured the driver scheme com=
pletely.
In fact, I cannot see which driver in 3.1.3 uses tms9914 at all!?
I went through=20
modprobe <drivername>=20
for every one of them in drivers.txt, and in no case did tms9914 get load=
ed.
I looked at the code, and the only mention of 9914 was in the tnt4882 dir=
ectory,
so I tried forcing tms9914 install with tnt4882, to no avail.
In every case, upon installation of the driver module, the BASE/IRQ value=
s assigned
to the card by the isapnp remain unused (in /proc/ioports and /proc/inter=
rupts), and
ibtest does not find anything of value.
Could you help? We are willing to do some coding, but we are not terribl=
y clever
with kernel-level stuff. Perhaps you could give us some pointers? Actua=
lly, if you could
add to the driver tree an hp8234x subdirectory, and put a skeleton driver=
in, and add it
to the list of valid drivers, somewhere in the code, we could then try to=
figure out=20
what to do within the driver (hopefully, very little compared to any othe=
r ISA/9914-type
driver). I looked at the code structure, and although it is a
major improvement from old versions, I am still quite confused by the rel=
ationships=20
of various pieces, and that's where your help would be most welcome.
Thanks in advance!
Here are some relevant snippets.
# cat /etc/isapnp.conf
(READPORT 0x0273)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL))
(CONFIGURE HWP1411/1073748200 (LD 0
(IO 0 (SIZE 32) (BASE 0x0240) (CHECK)) # also tried BASE 0x260
(INT 0 (IRQ 13 (MODE +E))) # also tried IRQ 12
(NAME "HWP1411/1073748200[0]{Hewlett-Packard HP-IB Interface Card}")
(ACT Y)
))
(WAITFORKEY)
# isapnp /etc/isapnp.conf
Board 1 has Identity a9 40 00 18 e8 11 14 f0 22: HWP1411 Serial No 10737=
48200 [checksum a9]
HWP1411/1073748200[0]{Hewlett-Packard HP-IB Interface Card}: Port 0x240; =
IRQ13 --- Enabled OK
# modprobe tms9914
# modprobe tnt4882
# lsmod
tnt4882 5056 0 (unused)
nec7210 8800 0 [tnt4882]
gpib-common 14400 0 [tnt4882]
tms9914 5872 0 (unused)
eepro100 15632 1
es1371 27712 0 (unused)
gameport 1568 0 [es1371]
ac97_codec 8864 0 [es1371]
soundcore 3664 4 [es1371]
# lspci -v | grep IRQ
Flags: bus master, medium devsel, latency 64, IRQ 10
Flags: medium devsel, IRQ 9
Flags: bus master, medium devsel, latency 64, IRQ 5
Flags: bus master, slow devsel, latency 64, IRQ 3
Flags: bus master, stepping, medium devsel, latency 64, IRQ 11
# cat /proc/interrupts
CPU0 =20
0: 85271 XT-PIC timer
1: 3261 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC es1371
4: 6 XT-PIC =20
5: 646 XT-PIC eth0
8: 1 XT-PIC rtc
14: 3086 XT-PIC ide0
15: 26 XT-PIC ide1
NMI: 0=20
ERR: 0
# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0213-0213 : isapnp read
0376-0376 : ide1
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0a79-0a79 : isapnp write
0cf8-0cff : PCI conf1
4000-403f : Intel Corporation 82371AB PIIX4 ACPI
5000-501f : Intel Corporation 82371AB PIIX4 ACPI
d000-dfff : PCI Bus #01
d000-d0ff : ATI Technologies Inc 3D Rage LT Pro AGP-133
e000-e01f : Intel Corporation 82371AB PIIX4 USB
e400-e41f : Intel Corporation 82557 [Ethernet Pro 100]
e400-e41f : eepro100
e800-e83f : Ensoniq ES1371 [AudioPCI-97]
e800-e83f : es1371
f000-f00f : Intel Corporation 82371AB PIIX4 IDE
f000-f007 : ide0
f008-f00f : ide1
# ibtest
enter primary address for device [0-30]: 0
trying to open pad =3D 0 on /dev/gpib0 ...
ibBoardOpen :[Fri May 24 17:04:23 2002](-)< ERR> EDVR <OS Error>
-- errno=3D19 (No such device)
ibBdChrConfig :[Fri May 24 17:04:23 2002](=90=A5)< ERR> EDVR <OS Erro=
r>
-- errno=3D19 (No such device)
failed to get descriptor
# cat /etc/gpib.conf
/***********************************************************************
GPIB.CONF IEEE488 library config file
-------------------
copyright : (C) 2002 by Frank Mori Hess
(C) 1994 by C.Schroeter
email : fm...@us...
************************************************************************=
***/
/************************************************************************=
***
* =20
* Syntax:
*
* interface { ... } starts new interface board section
* device {...} device configuration
*
************************************************************************=
***/
/* This section configures the configurable driver characteristics
* for an interface board, such as board address, and interrupt level.
* minor =3D 0 configures /dev/gpib0, minor =3D 1 configures /dev/gpib1, =
etc.
*/
interface {
minor =3D 0 /* minor =3D 0 uses /dev/gpib0, minor =3D 1 uses /dev/gpib1=
, etc. */
board_type =3D tnt4882 /* type of interface board being used */
pad =3D 0 /* primary adress of interface */
sad =3D 0 /* secondary adress of interface */
timeout =3D 3s /* timeout for commands */
eos =3D 0x0a /* EOS Byte */
set-reos yes /* Terminate read if EOS */
set-bin no /* Compare EOS 8-bit */
/* settings for boards that lack plug-n-play capability */
base =3D 0x240 /* Base io ADDRESS */
irq =3D 12 /* Interrupt request level */
dma =3D 0 /* DMA channel (zero disables) */
master yes /* interface board is system controller */
}
/* now the device section defines the device characteristics for each dev=
ice.
*/
device { /* HP34401A at address 22 */
name =3D voltmeter /* device mnemonic =
*/
minor =3D 0 /* minor number for interface board this device is connecte=
d to */
pad =3D 22 /* The Primary Address =
*/
sad =3D 0 /* Secondary Address =
*/
/* init-string =3D D2HELLO */ /* send some init chars =
*/
init-flags =3D LLO,DCL /* set flags =
*/
eos=3D0xa /* EOS Byte =
*/
set-reos no /* Terminate read if EOS =
*/
set-bin no /* Compare EOS 8-bit =
*/
}
------------------------------------------------------------------
Ed Sternin, Physics Dept, Brock U, St.Catharines, Ontario, L2S 3A1
http://www.physics.BrockU.CA/faculty/sternin.html
voice:(905)688-5550x3414 FAX:(905)682-9020 email: ed...@br...
|
|
From: <tim...@ex...> - 2002-05-01 22:16:39
|
I don't think it's a pnp device. Windows didn't find it as a pnp device. And linux isapnp doesn't find it either. I'll look at CVS, but I admit I'm a rookie with CVS. Thanks, Tim --- On Wed 05/01, frank mori hess wrote: > > I fixed some writeb() that should have been outb() in CVS, could you try > that? I've got a pci NI board that works with the same driver, so your > board shouldn't be too far from working. By the way, when ibtest asks > for > the gpib address of your device, it wants the address of the device you > are going to talk to, not the address of your interface board (I should > make that more clear in the program). Giving it the primary address of > zero wasn't the cause of the crash though. Also, are you using > isapnptools to configure your board under linux? > > Frank > > On Wed, 1 May 2002, wrote: > > > > > Hello again, > > > > I tried running this at run level 1 (and also in run level 3) and > here is what happens: > > > > the following message repeated about 20 times, then freeze: > > > > unable to handle kernel paging request > > at virtual address 307446b2 > > printing eip: > > c0124a16 > > *pde=00000000 > > ooops:00000 > > > > For what it's worth. > > > > Tim > > > > > > > > > > ------------------------------------------------ > > > > > > _______________________________________________________________ > > > > Have big pipes? SourceForge.net is looking for download mirrors. We > supply > > the hardware. You get the recognition. Email Us: > ban...@so... > > _______________________________________________ > > Linux-gpib-general mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > > > > ------------------------------------------------ Join Excite! - http://www.excite.com The most personalized portal on the Web! |
|
From: frank m. h. <fm...@st...> - 2002-05-01 22:06:20
|
I fixed some writeb() that should have been outb() in CVS, could you try that? I've got a pci NI board that works with the same driver, so your board shouldn't be too far from working. By the way, when ibtest asks for the gpib address of your device, it wants the address of the device you are going to talk to, not the address of your interface board (I should make that more clear in the program). Giving it the primary address of zero wasn't the cause of the crash though. Also, are you using isapnptools to configure your board under linux? Frank On Wed, 1 May 2002, wrote: > > Hello again, > > I tried running this at run level 1 (and also in run level 3) and here is what happens: > > the following message repeated about 20 times, then freeze: > > unable to handle kernel paging request > at virtual address 307446b2 > printing eip: > c0124a16 > *pde=00000000 > ooops:00000 > > For what it's worth. > > Tim > > > > > ------------------------------------------------ > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Linux-gpib-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general > |
|
From: <tim...@ex...> - 2002-05-01 21:44:14
|
Hello again, I tried running this at run level 1 (and also in run level 3) and here is what happens: the following message repeated about 20 times, then freeze: unable to handle kernel paging request at virtual address 307446b2 printing eip: c0124a16 *pde=00000000 ooops:00000 For what it's worth. Tim ------------------------------------------------ |
5 messages has been excluded from this view by a project administrator.
