EmCOREFS - Revision history

User890104: finally remove the requirement for gcc version

2014-05-08T13:07:41Z

finally remove the requirement for gcc version

← Older revision		Revision as of 13:07, 8 May 2014
Line 6:		Line 6:
	You need:		You need:

	1. GCC ~~4.4~~ and GNU Make (Xcode on OS X)		1. GCC and GNU Make (Xcode on OS X)

	2. pkg-config		2. pkg-config
Line 17:		Line 17:

	===Installing needed packages on Ubuntu===		===Installing needed packages on Ubuntu===
	sudo apt-get install gcc~~-4.4~~ make pkg-config libusb-1.0-0-dev libfuse-dev		sudo apt-get install gcc make pkg-config libusb-1.0-0-dev libfuse-dev

	===Compiling===		===Compiling===

User890104: add os x umount command

2014-01-29T21:28:20Z

add os x umount command

← Older revision		Revision as of 21:28, 29 January 2014
Line 47:		Line 47:

	* Stopping:		* Stopping:
	fusermount -u <mountpoint as seen in /etc/mtab>		fusermount -u <mountpoint as seen in /etc/mtab> (on Linux)

			diskutil unmount <mountpoint as seen in /etc/mtab> (on OS X)

	==Known bugs/issues==		==Known bugs/issues==

User890104 at 23:21, 2 January 2014

2014-01-02T23:21:46Z

← Older revision		Revision as of 23:21, 2 January 2014
Line 50:		Line 50:

	==Known bugs/issues==		==Known bugs/issues==
	* Write support not tested very well.
	* Running FUSE with multithreading breaks file reading because of the way these are implemented on emCORE's side. Workaround: use the "-s" option.		* Running FUSE with multithreading breaks file reading because of the way these are implemented on emCORE's side. Workaround: use the "-s" option.
	* ~~Most~~ errors are not handled properly, EIO (Input/output error) is given in ~~many~~ cases where there's a more descriptive error message available. Will be fixed in the future.		* Some errors are not handled properly, EIO (Input/output error) is given in cases where there's a more descriptive error message available. Will be fixed in the future.
	* Rename/move in the filesystem itself is currently disabled, since the underlying filesystem call crashes the emCORE kernel. Workaround: move the file/dir on another filesystem, then rename it if needed, then move it back.		* '''Rename/move in the filesystem itself is currently disabled, since the underlying filesystem call crashes the emCORE kernel.''' Workaround: move the file/dir on another filesystem, then rename it if needed, then move it back.

	==Future plans==		==Future plans==
	* Merge some functions that are doing similar tasks to reduce code duplication. Return proper error codes in FS operations.		* Merge some functions that are doing similar tasks to reduce code duplication.
			* Return proper error codes in FS operations.

	==Bug reporting==		==Bug reporting==

User890104 at 22:32, 15 October 2013

2013-10-15T22:32:44Z

← Older revision		Revision as of 22:32, 15 October 2013
Line 21:		Line 21:
	===Compiling===		===Compiling===
	* standard build, no debug messages, only fatal errors on startup are shown.		* standard build, no debug messages, only fatal errors on startup are shown.
	make		make build/emcorefs


Line 33:		Line 33:

	===Testing===		===Testing===
	* ~~run~~ the ~~build without FUSE debugging messages, going into the background if it connects~~ to ~~the device successfully~~.		* test the connection and some basic emCORE functions. useful only to developers.
	make test		make build/emcore-test
			./build/emcore-test

	* run the build ~~in the foreground, showing FUSE debug messages in the terminal.~~
	~~make testdebug~~

	==Running==		==Running==
Line 46:		Line 43:

	* Starting:		* Starting:
	./emcorefs <mountpoint>		./build/emcorefs <mountpoint>

User890104 at 22:28, 15 October 2013

2013-10-15T22:28:13Z

← Older revision		Revision as of 22:28, 15 October 2013
Line 1:		Line 1:
	~~{{Template:Outdated\|reason=emCOREFS is not compatible with emCORE r891+, due to breaking changes (new debugging method)}}~~		emCOREFS is a FUSE-based filesystem that uses emCORE's Monitor API to provide communication with device's FS. It is mostly complete, and works well. It runs on both Linux and Mac OS X.
	emCOREFS is a FUSE-based filesystem that uses emCORE's Monitor API to provide communication with device's FS. It is ~~not yet~~ complete, ~~but most features are done~~. It runs on both Linux and Mac OS X.

	For communication with the device, this application uses libusb 1.0.		For communication with the device, this application uses libusb 1.0.
Line 7:		Line 6:
	You need:		You need:

	1. GCC/Make (Xcode on OS X)		1. GCC 4.4 and GNU Make (Xcode on OS X)

	2. pkg-config		2. pkg-config
Line 16:		Line 15:

	5. all dependencies of the above		5. all dependencies of the above

			===Installing needed packages on Ubuntu===
			sudo apt-get install gcc-4.4 make pkg-config libusb-1.0-0-dev libfuse-dev

	===Compiling===		===Compiling===
Line 54:		Line 56:
	* Running FUSE with multithreading breaks file reading because of the way these are implemented on emCORE's side. Workaround: use the "-s" option.		* Running FUSE with multithreading breaks file reading because of the way these are implemented on emCORE's side. Workaround: use the "-s" option.
	* Most errors are not handled properly, EIO (Input/output error) is given in many cases where there's a more descriptive error message available. Will be fixed in the future.		* Most errors are not handled properly, EIO (Input/output error) is given in many cases where there's a more descriptive error message available. Will be fixed in the future.
			* Rename/move in the filesystem itself is currently disabled, since the underlying filesystem call crashes the emCORE kernel. Workaround: move the file/dir on another filesystem, then rename it if needed, then move it back.

	==Future plans==		==Future plans==

User890104 at 17:40, 20 August 2013

2013-08-20T17:40:44Z

← Older revision		Revision as of 17:40, 20 August 2013
Line 1:		Line 1:
			{{Template:Outdated\|reason=emCOREFS is not compatible with emCORE r891+, due to breaking changes (new debugging method)}}
	emCOREFS is a FUSE-based filesystem that uses emCORE's Monitor API to provide communication with device's FS. It is not yet complete, but most features are done. It runs on both Linux and Mac OS X.		emCOREFS is a FUSE-based filesystem that uses emCORE's Monitor API to provide communication with device's FS. It is not yet complete, but most features are done. It runs on both Linux and Mac OS X.

User890104 at 14:17, 19 November 2011

2011-11-19T14:17:39Z

← Older revision		Revision as of 14:17, 19 November 2011
Line 40:		Line 40:
	You need FUSE >= 2.8 installed. (or fuse4x on x64 OS X)		You need FUSE >= 2.8 installed. (or fuse4x on x64 OS X)

	Currently tested on Linux (Ubuntu 11.04) and Mac OS X (10.6.8).		Currently tested on Linux (Ubuntu 11.04 x86) and Mac OS X (10.6.8 x64).

	* Starting:		* Starting:

User890104 at 14:17, 19 November 2011

2011-11-19T14:17:17Z

← Older revision		Revision as of 14:17, 19 November 2011
Line 38:		Line 38:

	==Running==		==Running==
	You need FUSE >= 2.8 installed.		You need FUSE >= 2.8 installed. (or fuse4x on x64 OS X)

	Currently tested on Linux (Ubuntu 11.04) and Mac OS X (10.6.8).		Currently tested on Linux (Ubuntu 11.04) and Mac OS X (10.6.8).

User890104 at 14:14, 19 November 2011

2011-11-19T14:14:08Z

← Older revision		Revision as of 14:14, 19 November 2011
Line 17:		Line 17:

	===Compiling===		===Compiling===
	~~make -~~ standard build, no debug messages, only fatal errors on startup are shown.		* standard build, no debug messages, only fatal errors on startup are shown.
			make

	~~make debug -~~ debug build, some debug/error messages are shown. libusb debug messages are enabled, too.
			* debug build, some debug/error messages are shown. libusb debug messages are enabled, too.
			make debug


			You can prefix any of these with
			CFLAGS="-DDEBUG_USB_PACKETS"
			in order to have a dump of the usb traffic that's being sent and received.

	===Testing===		===Testing===
	~~make test -~~ run the build without FUSE debugging messages, going into the background if it connects to the device successfully.		* run the build without FUSE debugging messages, going into the background if it connects to the device successfully.
			make test


	~~make testdebug -~~ run the build in the foreground, showing FUSE debug messages in the terminal.		* run the build in the foreground, showing FUSE debug messages in the terminal.
			make testdebug

	==Running==		==Running==
Line 31:		Line 42:
	Currently tested on Linux (Ubuntu 11.04) and Mac OS X (10.6.8).		Currently tested on Linux (Ubuntu 11.04) and Mac OS X (10.6.8).

	Starting:		* Starting:
	./emcorefs <mountpoint>		./emcorefs <mountpoint>
	Stopping:

			* Stopping:
	fusermount -u <mountpoint as seen in /etc/mtab>		fusermount -u <mountpoint as seen in /etc/mtab>

User890104 at 18:46, 18 November 2011

2011-11-18T18:46:05Z

← Older revision		Revision as of 18:46, 18 November 2011
Line 6:		Line 6:
	You need:		You need:

	1. GCC/Make		1. GCC/Make (Xcode on OS X)

	2. pkg-config		2. pkg-config
Line 12:		Line 12:
	3. libusb >= 1.0		3. libusb >= 1.0

	4. libfuse >= 2.8		4. libfuse >= 2.8 (or fuse4x on x64 OS X)

	5. ~~maybe other packages~~		5. all dependencies of the above

	===Compiling===		===Compiling===