Menu
▾
▴
x2susbsfwkit-devel — discussions between developers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Jouni <Jou...@fm...> - 2005-09-09 05:33:44
|
is in the CVS. The isotransfer it not tested yet, and it behaves a bit
differently. The device-files are named differently ...
regards
Jouni
--=20
Jouni Ryn=F6 mailto://Jou...@fm.../
http://www.geo.fmi.fi/~ryno/
Finnish Meteorological Institute http://www.fmi.fi/
Space Research http://www.geo.fmi.fi/
P.O.BOX 503 Tel (+358)-9-19294656
FIN-00101 Helsinki FAX (+358)-9-19294603
Finland priv-GSM (+358)-50-5302903
=20
"It's just zeros and ones, it cannot be hard"
|
|
From: Jouni <Jou...@fm...> - 2002-11-27 11:00:47
|
Did any of you receive this email. I got it, but the sourceforge webpage
does not show it in the archive.
Anyway, I fixed the broken seek routine today.
Needs a bit of thinking, if one should also implement a polling routine
for iso writing.
regards
Jouni
On Tue, 2002-11-19 at 14:59, Jouni Ryn=F6 wrote:
> Well, I might have a bit hasty, but I just created a CVS directory
> x2s_driver. Erzin Ozalp promised to do it asap in spring :-), but as my
> driver works now with exo demodesing CESYS has made, I though I could
> speed things a little.
>=20
> There's a README file, which explains some of the functionality. Really
> I must do a better documentation, but I kind of like to get some
> feedback first ...CESYS people might like to check and comment the
> naming of files/ioctl routines ...=20
>=20
> regards
> Jouni
--=20
Jouni Ryn=F6 mailto://Jou...@fm.../
http://www.geo.fmi.fi/~ryno/
Finnish Meteorological Institute http://www.fmi.fi/
Geophysical Research http://www.geo.fmi.fi/
P.O.BOX 503 Tel (+358)-9-19294656
FIN-00101 Helsinki FAX (+358)-9-19294603
Finland priv-GSM (+358)-50-5302903
=20
"It's just zeros and ones, it cannot be hard"
|
|
From: Jouni <Jou...@fm...> - 2002-11-19 12:59:54
|
Well, I might have a bit hasty, but I just created a CVS directory
x2s_driver. Erzin Ozalp promised to do it asap in spring :-), but as my
driver works now with exo demodesing CESYS has made, I though I could
speed things a little.
There's a README file, which explains some of the functionality. Really
I must do a better documentation, but I kind of like to get some
feedback first ...CESYS people might like to check and comment the
naming of files/ioctl routines ...=20
regards
Jouni
--=20
Jouni Ryn=F6 mailto://Jou...@fm.../
http://www.geo.fmi.fi/~ryno/
Finnish Meteorological Institute http://www.fmi.fi/
Geophysical Research http://www.geo.fmi.fi/
P.O.BOX 503 Tel (+358)-9-19294656
FIN-00101 Helsinki FAX (+358)-9-19294603
Finland priv-GSM (+358)-50-5302903
=20
"It's just zeros and ones, it cannot be hard"
|
|
From: Jouni R. <Jou...@fm...> - 2002-11-02 15:42:47
|
On Sat, 2002-11-02 at 17:25, Johann Glaser wrote: > Hi! >=20 > > I have them. Sorry I really should have phrased myself better. I was > > asking for the possibility to get the CESYS firmware source. > >=20 > > As I have no experience from that CPU and assembler, would it be > > possible to make it work as the CESYS code, i.e. rebooting with other > > product ID. That would make it possible for the USB system to detect it > > and use my driver module. >=20 > CESYS doesn't give away their firmware's sources. But Mr. =D6zalp sent me > the specification of the USB protocol with their firmware. Please ask > him to get it too. >=20 I got it also. I just would prefer to have all the source files, I use. Well, I'm anyway dependent on the hardware they make, so it's not so big issue. Most likely we will be happy with the evaluation boards, as there will never be need for more than 30 boards or so. Some space instrument interface systems ... > Currently I don't have enough time to develop for the X2S_USB board. In > the christmas holidays I'm going to program a bit. >=20 Hopefully I have the driver done by that :-) Thanks anyway. Jouni |
|
From: Johann G. <Joh...@gm...> - 2002-11-02 15:25:30
|
Hi!
> I have them. Sorry I really should have phrased myself better. I was
> asking for the possibility to get the CESYS firmware source.
>=20
> As I have no experience from that CPU and assembler, would it be
> possible to make it work as the CESYS code, i.e. rebooting with other
> product ID. That would make it possible for the USB system to detect it
> and use my driver module.
CESYS doesn't give away their firmware's sources. But Mr. =D6zalp sent me
the specification of the USB protocol with their firmware. Please ask
him to get it too.
Currently I don't have enough time to develop for the X2S_USB board. In
the christmas holidays I'm going to program a bit.
Bye
Hansi
--=20
Johann Glaser <Joh...@gm...>
Vienna University of Technology
Electrical Engineering=20
____ http://www.johann-glaser.at/ ____
|
|
From: Jouni R. <Jou...@fm...> - 2002-11-02 15:14:51
|
On Sat, 2002-11-02 at 15:32, Johann Glaser wrote: > Hi! > > > Finally got active in developing a module for CESYS X2S_USB card. > > > > What I did, was to use hotplug and fxload to load the CESYS loader and > > firmware files to it. Johann Glaser has made his own loader, but does > > not restart and change the device ID. As there is a tool to compile the > > code (asx8051) in Linux, it would be nice to get the source ... open > > source :-) > > The sources are available at my web site > http://www.johann-glaser.at/projects/X2S_USB/ > for downloading. > I have them. Sorry I really should have phrased myself better. I was asking for the possibility to get the CESYS firmware source. As I have no experience from that CPU and assembler, would it be possible to make it work as the CESYS code, i.e. rebooting with other product ID. That would make it possible for the USB system to detect it and use my driver module. regards Jouni |
|
From: Johann G. <Joh...@gm...> - 2002-11-02 13:32:33
|
Hi! > Finally got active in developing a module for CESYS X2S_USB card. > > What I did, was to use hotplug and fxload to load the CESYS loader and > firmware files to it. Johann Glaser has made his own loader, but does > not restart and change the device ID. As there is a tool to compile the > code (asx8051) in Linux, it would be nice to get the source ... open > source :-) The sources are available at my web site http://www.johann-glaser.at/projects/X2S_USB/ for downloading. Bye Hansi -- Johann Glaser <Joh...@gm...> Vienna University of Technology Electrical Engineering ____ http://www.johann-glaser.at/ ____ |
|
From: Jouni <Jou...@fm...> - 2002-11-01 15:42:11
|
Hi Ersin (and others ...)
Finally got active in developing a module for CESYS X2S_USB card.
What I did, was to use hotplug and fxload to load the CESYS loader and
firmware files to it. Johann Glaser has made his own loader, but does
not restart and change the device ID. As there is a tool to compile the
code (asx8051) in Linux, it would be nice to get the source ... open
source :-)
Anyway, I got to the point, that upon starting the driver for 0xCE85, I
create a file at /dev/usb/cesys0/download and use 'cat' to pipe the
exo-files to FPGA.
Now the programmers guide at 2.5 talks about using bulk pipes to use
addressable data. On the other hand, I only see two iso streams for the
device. Also the document I received last sprint, X2S_USB firmware
interface, 2.10 descripes CESYS_ADDRESSABLE_DATA with code 0xE9, which
makes me think, that it's implemented as control message ? How is it
really done ?=20
And if it's control message, is the index simply the copy of transfer
size. Values is in the form 0x8000 + address ?
A bit hasty email, have to go home ...
regards
Jouni
=20
--=20
Jouni Ryn=F6 mailto://Jou...@fm.../
http://www.geo.fmi.fi/~ryno/
Finnish Meteorological Institute http://www.fmi.fi/
Geophysical Research http://www.geo.fmi.fi/
P.O.BOX 503 Tel (+358)-9-19294656
FIN-00101 Helsinki FAX (+358)-9-19294603
Finland priv-GSM (+358)-50-5302903
=20
"It's just zeros and ones, it cannot be hard"
|
|
From: Johann G. <Joh...@gm...> - 2002-07-07 17:29:22
|
Dear Mr. Kraus, Dear Mr. Ozalp, Dear mailing list members! In March I developed a little program to download configuration files into the FPGA on the X2S_USB Eval Board for Linux. Today I added a nice README file containing information how to setup hotplugging to use cesys_downloader as a normal user without root rights. Since in March Mr. Ozalp didn't respond to my announcement and due to lack of my own time (had to do a lot at university) I want to use this mail today, to announce the (little) enhanced version of the downloader. We now should manage to setup a homepage for the SourceForge Project to provide a downloadable version. Currently I am hosting the downloadable file at my own homepage at http://www.johann-glaser.at/projects/X2S_USB/ I'd like to hear some feedback from you and any tips, suggestions, plans, ... Bye Hansi -- Johann Glaser <Joh...@gm...> Vienna University of Technology Electrical Engineering ____ http://www.johann-glaser.at/ ____ |
|
From: James O. <ja...@ze...> - 2002-03-31 14:21:11
|
There seems to have been a little confusion in previous e-mails regarding (my) driver development. To put things straight, I have developed a rudimentary PCI driver (nothing to do with the USB driver) for the XC2S PCI based development board. The source for this driver can be found under the FPRT (FPGA centric Radio Transceiver) project page on www.sourceforge.net. Presently, the driver supports one CESYS XC2S card and allows FPGA configuration and access to the FPGA (NCS2) I/O region for debugging designs. The prime aim of the driver was to familiarise myself with the linux kernel and the PCI bus and also to allow me to test my FPGA designs under linux for the FPRT project. Hope that makes everything clear. If you have any questions, don't hesitate to e-mail. yours, James Ogden (Zemned) |
|
From: James O. <ja...@ze...> - 2002-03-31 12:27:34
|
There seems to have been a little confusion in previous e-mails regarding (my) driver development. To put things straight, I have developed a rudimentary PCI driver (nothing to do with the USB driver) for the XC2S PCI based development board. The source for this driver can be found under the FPRT (FPGA centric Radio Transceiver) project page on www.sourceforge.net. Presently, the driver supports one CESYS XC2S card and allows FPGA configuration and access to the FPGA (NCS2) I/O region for debugging designs. The prime aim of the driver was to familiarise myself with the Linux kernel and the PCI bus and also to allow me to test my FPGA designs under Linux for the FPRT project. Hope that makes everything clear. If you have any questions, don't hesitate to e-mail. yours, James Ogden (Zemned) |
|
From: Johann G. <Joh...@gm...> - 2002-03-24 22:40:44
|
Hi! Yesterday I developed a very small FPGA configuration downloading program for Linux. It simply took a .rbt file and pushed it into the FPGA. Therefore I wrote my own 8051 firmware for the EZ-USB chip because the CESYS interface is undocumented. After playing a while I found the last errors and bugs and HURRA it worked. A simple 12kByte linux executable. Today I cleaned up, added some more features, made several .c files splited by function (read rbt, read exo, read intel hex, download firmware, download fpga config, ...) and now the executable has 15kByte. Neat. :-) The program uses libusb (see http://libusb.sf.net/) so no kernel module is necessary. But it depends on usbdevfs (mounted at /proc/bus/usb). If a non-root user wants to execute the program this usbdevfs must have accurate access rights (set by module parameters, invoke chmod by hand, ...). Is anybody interested in this program? Hmm, we should manage to upload it to our SourceForge account. Any ideas? Shall we use CVS? Downloading the FPGA is done in astonishing 6 seconds, which is just a fraction of the windows duration. Perhaps the windows program can be optimized too. Another speedup could be achieved using isochronous pipes instead of simple bulk pipes. But libusb doesn't support them, so a kernel module is necessary. Since the Windows driver supports isochronous transport I think it is expected that the linux drivers should too. I talked to the libusb developers and they said, that isochronous pipes will not be supported in the near future due to problems specifying a good API. Bye Hansi -- Johann Glaser <Joh...@gm...> Vienna University of Technology Electrical Engineering http://stud3.tuwien.ac.at/~e9825761/index.html |
|
From: Johann G. <Joh...@gm...> - 2002-03-23 12:43:04
|
This is a test.
--
Johann Glaser <Joh...@gm...>
Vienna University of Technology
Electrical Engineering
http://stud3.tuwien.ac.at/~e9825761/index.html
|
