SYSTEM INTEGRATION - Revision history

OZ1HFT: +cat

2010-01-25T18:57:18Z

+cat

Charlieh0tel: /* To do list */

2008-01-23T00:08:15Z

‎To do list

Charlieh0tel: /* Loading Ozy firmware */

2008-01-23T00:06:06Z

‎Loading Ozy firmware

Charlieh0tel at 00:05, 23 January 2008

2008-01-23T00:05:26Z

Charlieh0tel: clean up

2008-01-22T23:51:12Z

clean up

Charlieh0tel: /* Ozy and Janus with Linux */

2008-01-22T23:45:17Z

‎Ozy and Janus with Linux

WikiSysop: Initial edit of SYSTEM INTEGRATION page

2008-01-22T05:52:48Z

Initial edit of SYSTEM INTEGRATION page

New page

This section contains information useful in putting various pieces (modules) together to make working systems.

== Ozy and Janus with Linux ==

(to be added by CH here)

← Older revision		Revision as of 18:57, 25 January 2010
Line 73:		Line 73:
	* alternatively, continue on with KD5TFD's approach to the problem, which is to rewrite the code in C/C++ with native code lib		* alternatively, continue on with KD5TFD's approach to the problem, which is to rewrite the code in C/C++ with native code lib
	* see if we can built the FX2 firmware using FOSS (probably sdcc [[http://sdcc.sourceforge.net/]]).		* see if we can built the FX2 firmware using FOSS (probably sdcc [[http://sdcc.sourceforge.net/]]).
		+
		+	[[Category:Hardware]]

← Older revision		Revision as of 00:08, 23 January 2008
Line 72:		Line 72:
	* experiment to see if we can get a CIL version of libusb running with Mono [[http://www.mono-project.com/Main_Page]] so that we can leverage N8VB's C# sources.		* experiment to see if we can get a CIL version of libusb running with Mono [[http://www.mono-project.com/Main_Page]] so that we can leverage N8VB's C# sources.
	* alternatively, continue on with KD5TFD's approach to the problem, which is to rewrite the code in C/C++ with native code lib		* alternatively, continue on with KD5TFD's approach to the problem, which is to rewrite the code in C/C++ with native code lib
		+	* see if we can built the FX2 firmware using FOSS (probably sdcc [[http://sdcc.sourceforge.net/]]).

@@ Line 13: / Line 13: @@
   lsusb -d 0xfffe:0x0007
-The bus and device number display by lsusb can be used to construct the path (/proc/bus/usb/...) to the device that libusb-programs such as fxload expect.  On my setup after a reboot, Ozy shows up on bus 4 and as device 10.  (The device number will change as devices come and go.)
+The bus and device number displayed by lsusb can be used to construct the path (/proc/bus/usb/...) to the device that libusb-programs such as fxload expect.  On my setup after a reboot, Ozy shows up on bus 4 and as device 10.  (The device number will change as devices come and go.)
 Next, given an Ozy, say, at usb bus 4, device 10, invoke fxload as follows to load the firmware on to the Ozy FX2:

@@ Line 5: / Line 5: @@
 === Loading Ozy firmware ===
-fxload is the standard Cypress firmware loader for modern Linux distros.
+fxload [[http://linux-hotplug.sourceforge.net/?selected=usb]] is the standard Cypress firmware loader for modern Linux distros.
 Until we getting hotplug/udev support working (see the [[#To_do_list|to do list]]), loading firmware with fxload requires a few manual steps.
-The frist step is to find your Ozy.  Do this by using the lsusb utility from usbutils:
+The first step is to find your Ozy.  Do this by using the lsusb utility from usbutils [[http://sourceforge.net/project/showfiles.php?group_id=3581&package_id=142529]]:
   lsusb -d 0xfffe:0x0007
@@ Line 15: / Line 15: @@
 The bus and device number display by lsusb can be used to construct the path (/proc/bus/usb/...) to the device that libusb-programs such as fxload expect.  On my setup after a reboot, Ozy shows up on bus 4 and as device 10.  (The device number will change as devices come and go.)
-Given an Ozy at usb bus 4, device 10, the following will load the firmware on to the Ozy FX2:
+Next, given an Ozy, say, at usb bus 4, device 10, invoke fxload as follows to load the firmware on to the Ozy FX2:
   fxload -t fx2 -D /proc/bus/usb/004/010 -I ./PowerSDR-163-OzyJanus-2007May11/Release/ozyfw-sdr1k.hex
 Unless you adjust the permissions on the file, you will need to run this as root (e.g. via sudo).
-Note: after the firmware loads, the device will be renumbered.  You can find it as above -- the vendor id (0xfffe) and product id (0x0007) remain the same once the firmware is running -- although this is probably a mistake in the firmware design.
+Note: after the firmware loads, the device will be renumbered.  You can find it at its new address by repearting the process above -- the vendor id (0xfffe) and product id (0x0007) remain the same once the firmware is running -- although this is probably a mistake in the firmware design.
 === Loading the FPGA ===
-Tbd.
+Using KD5TFD's tools -- these are in the svn repo -- you can load everything (firmware, fpga) and configure it with the following script, based on N8VB's DOS batch file.
 === To do list ===
@@ Line 31: / Line 67: @@
 This list needs to be fleshed out and triaged.
-* figure out hotplug/udev magic to make Ozy firmware load automatically
+* figure out the hotplug/udev magic to make Ozy firmware load automagically
 * packaging -- i can create and test a .deb for Debian and Ubuntu.  i can also rough out the rpm for RHEL4/RHEL5/Fedora, but someone else will have to test and tweak it.
 * build the Ozy firmware using only FOSS
-* experiment to see if we can get a CIL version of libusb running with Mono so that we can leverage N8VB's C# sources.
+* experiment to see if we can get a CIL version of libusb running with Mono [[http://www.mono-project.com/Main_Page]] so that we can leverage N8VB's C# sources.
-* alternatively, continue on with KD5TFD's approach, which is to rewrite the code in C/C++ with native code libusb.
+* alternatively, continue on with KD5TFD's approach to the problem, which is to rewrite the code in C/C++ with native code lib

@@ Line 7: / Line 7: @@
 fxload is the standard Cypress firmware loader for modern Linux distros.
-Until we getting hotplug/udev support working (see the to do list below), loading firmware with fxload requires a few manual steps.
+Until we getting hotplug/udev support working (see the [[#To_do_list|to do list]]), loading firmware with fxload requires a few manual steps.
-The frist step is to find your Ozy.  Do this by using the lsusb utiltiy from usbutils:
+The frist step is to find your Ozy.  Do this by using the lsusb utility from usbutils:
-lsusb -d 0xfffe:0x0007
+ lsusb -d 0xfffe:0x0007
 The bus and device number display by lsusb can be used to construct the path (/proc/bus/usb/...) to the device that libusb-programs such as fxload expect.  On my setup after a reboot, Ozy shows up on bus 4 and as device 10.  (The device number will change as devices come and go.)
@@ Line 17: / Line 17: @@
 Given an Ozy at usb bus 4, device 10, the following will load the firmware on to the Ozy FX2:
-fxload -t fx2 -D /proc/bus/usb/004/010 -I ./PowerSDR-163-OzyJanus-2007May11/Release/ozyfw-sdr1k.hex
+ fxload -t fx2 -D /proc/bus/usb/004/010 -I ./PowerSDR-163-OzyJanus-2007May11/Release/ozyfw-sdr1k.hex
 Unless you adjust the permissions on the file, you will need to run this as root (e.g. via sudo).

← Older revision		Revision as of 23:45, 22 January 2008
Line 3:		Line 3:
	== Ozy and Janus with Linux ==		== Ozy and Janus with Linux ==

−	(to ~~be added~~ by ~~CH here~~)	+	=== Loading Ozy firmware ===
		+
		+	fxload is the standard Cypress firmware loader for modern Linux distros.
		+
		+	Until we getting hotplug/udev support working (see the to do list below), loading firmware with fxload requires a few manual steps.
		+
		+	The frist step is to find your Ozy. Do this by using the lsusb utiltiy from usbutils:
		+
		+	lsusb -d 0xfffe:0x0007
		+
		+	The bus and device number display by lsusb can be used to construct the path (/proc/bus/usb/...) to the device that libusb-programs such as fxload expect. On my setup after a reboot, Ozy shows up on bus 4 and as device 10. (The device number will change as devices come and go.)
		+
		+	Given an Ozy at usb bus 4, device 10, the following will load the firmware on to the Ozy FX2:
		+
		+	fxload -t fx2 -D /proc/bus/usb/004/010 -I ./PowerSDR-163-OzyJanus-2007May11/Release/ozyfw-sdr1k.hex
		+
		+	Unless you adjust the permissions on the file, you will need to run this as root (e.g. via sudo).
		+
		+	Note: after the firmware loads, the device will be renumbered. You can find it as above -- the vendor id (0xfffe) and product id (0x0007) remain the same once the firmware is running -- although this is probably a mistake in the firmware design.
		+
		+	=== Loading the FPGA ===
		+
		+	Tbd.
		+
		+	=== To do list ===
		+
		+	This list needs to be fleshed out and triaged.
		+
		+	* figure out hotplug/udev magic to make Ozy firmware load automatically
		+	* packaging -- i can create and test a .deb for Debian and Ubuntu. i can also rough out the rpm for RHEL4/RHEL5/Fedora, but someone else will have to test and tweak it.
		+	* build the Ozy firmware using only FOSS
		+	* experiment to see if we can get a CIL version of libusb running with Mono so that we can leverage N8VB's C# sources.
		+	* alternatively, continue on with KD5TFD's approach, which is to rewrite the code in C/C++ with native code libusb.