[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] A/D converter and D/A converter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Yashi,
Thank you for your reply! Some very good news!
> should be easy. I assume form following comment, your a/d d/a use
> I2C, no?
Yes, I can order an I2C a/d and d/a.
> they are in ppc tree. I haven't look at those driver, but ppc
> currently have better xparameter.h support. if those driver use
> some defines which standalone/microblaze version doesn't have, it
> might be a little bit work, but definitely feasible.
Not sure what this means... does it mean re-synthesize the hardware
.bin file to use the PPC processor instead of the Microblaze
processor?
Or, can the existing mbvanilla-net .bin file be used with some mods?
I am a novice, but am completely open to suggestions.
> if you use linux i2c framework, it just read/write on a device
> node, which is not defferent from reading/writing files.
Can you suggest/think of any examples or references that may be
helpful?
Thank you!
- -Shamus McCarthy
- -----Original Message-----
From: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of Yasushi
SHOJI
Sent: Wednesday, September 08, 2004 7:45 PM
To: microblaze-uclinux@itee.uq.edu.au
Subject: Re: [microblaze-uclinux] A/D converter and D/A converter
Hi Shamus,
I'm not using memec virtex2 but ...
At Wed, 8 Sep 2004 15:59:35 -0600,
Shamus McCarthy wrote:
>
>
> I am working on a senior design project using the Insight/Memec
> Virtex2 system board and the P160 Communications module. I have
> uClinux up and running fine and would now like to add an A/D
> converter and a D/A converter to the setup.
>
> 1) Is it feasible to add these two components?
should be easy. I assume form following comment, your a/d d/a use
I2C, no?
> 2) There is an I2C port and a SPI port avaiable...would it be a
> good option to try to use these ports for adding the ADC and DAC?
they are in ppc tree. I haven't look at those driver, but ppc
currently have better xparameter.h support. if those driver use some
defines which standalone/microblaze version doesn't have, it might be
a little bit work, but definitely feasible.
> 3) How complicated would it be to use uClinux to read/control these
> two components?
if you use linux i2c framework, it just read/write on a device node,
which is not defferent from reading/writing files.
hope this helps,
- --
yashi
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQUEx/GkFsGRam+VXEQKDaACeII3TwK8ZySt5STZd9fDsauFqbycAoL8H
qmrZtSHUcTbPb95bkrvkQJ5x
=t4xL
-----END PGP SIGNATURE-----
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/