Installing a new PCI ParaPort in linux?

MAG45 wrote:

Does the <access denied> mean anything?

It probably just means you ran lspci without prefixing with sudo

All the port testing is confusing you and getting no closer to having your machine running.

You need to edit your .hal file in gedit

Find the line
loadrt hal_parport cfg="0x378.........."

That line specifies to use the built in port as parport 0

Since that port is broken, you need your first card port address here followed by the second
eg

loadrt hal_parport cfg="0xd400 out dc00 in"

This results in parport 0 being d400 and parport dc00 being parport 1 in your setup
(the numbers may be the second ones listed, you will have to test, but mostly the port is 0x400 lower than the register)

regards

I looked at the HAL file last night and it has dc00 as the Paraport, probably from me using stepconfig wizard. Its going to be too cold today for me to be out in the shop long. I'll be back at it tomorrow afternoon though.

Good morning!

Now that you have ptest working let's try this.
paste the following, between the dashes, into your ptest.hal, replace what is there.

---

loadrt hal_parport cfg="0x378 0xd400"
loadusr -Wn PortTest pyvcp -c PortTest ptest.xml
loadrt threads name1=porttest period1=1000000

addf parport.0.read porttest
addf parport.0.write porttest
addf parport.1.read porttest
addf parport.1.write porttest

net pin02 PortTest.btn02 parport.1.pin-02-out PortTest.led-02
net pin03 PortTest.btn03 parport.1.pin-03-out PortTest.led-03

start

# loadusr halmeter

---

Then run ptest and see if you can get pin2 and 3 to toggle. If not, shut down the tester and change the line:
loadrt hal_parport cfg="0x378 0xd400"
to
loadrt hal_parport cfg="0x378 0xdc00"

save and start the tester again.
I'll be gone for the day but will follow up later.
Best, Dan.

lakeweb wrote:

shut down the tester and change the line:
loadrt hal_parport cfg="0x378 0xd400"
to
loadrt hal_parport cfg="0x378 0xdc00"
.

I think the whole point of this, is that he has blown up his onboard port.

So he needs to remove the reference to 0x378, so that the PCI port is parport 0, otherwise nothing will work

regards

Yes, its possible my on board ParaPort was partially shot, although it was still working i was getting strange errors. I wanted to replace it for the peace of mind before I installed the new BOB. I dont have any use for the 2nd port right now, but it was only like $2 more.

I really wish I understood Linux better, I can somewhat follow what im being told to try, but I have no idea what im doing!

Hi ArcEye, MAG45,

When I set mine up I thought I could not get it to work without the 0x378 so I left it in. My box has no port on 0x378. So I went back and took it out and moved my pins to 0 to see if I was confused by something else. Sure enough this works:

---

loadrt hal_parport cfg="0xdcb0"
loadusr -Wn PortTest pyvcp -c PortTest ptest.xml
loadrt threads name1=porttest period1=1000000

addf parport.0.read porttest
addf parport.0.write porttest

net pin02 PortTest.btn02 parport.0.pin-02-out PortTest.led-02
net pin03 PortTest.btn03 parport.0.pin-03-out PortTest.led-03

start

# loadusr halmeter

---

I'm using the same chip, NetMos Technology PCI 9865. So it seems there should be no good reason why the above should not work for you.

Best, Dan.

Addendum: Your addresses are d400 and dc00 for your two ports.

I will try that tomorrow, hopefully i can figure out where to copy that to

HI,
That goes into your ptest.hal file. Your fully qualified addresses, one at a time, go in the first line quotes.
0xd400
0xdc00

You should be able to try just one address and one of the ports should work, move the plug. You have two addresses because you have two ports. When you find one of the ports working the second address would be for the other port.

Best, Dan.

Using a multimeter what should i be reading? Using d400 address i get it to toggle on pin 2 about 3mv.

Well thats as far as I got, ended up having to plug in the new BOB to get a reading on the pin. Just not sure the 3-4Mv i was seeing is right, i expected more, so i didnt know where to go next.