CPC M4 xfer tool - Revision history

Arnoldemu at 17:55, 13 January 2019

2019-01-13T17:55:37Z

← Older revision		Revision as of 17:55, 13 January 2019
Line 60:		Line 60:
	<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)		<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)

	[Category::Hardware]		[[Category:Hardware]]

Arnoldemu at 17:55, 13 January 2019

2019-01-13T17:55:19Z

← Older revision		Revision as of 17:55, 13 January 2019
Line 60:		Line 60:
	<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)		<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)

	[[Category::Hardware]]		[Category::Hardware]

Arnoldemu at 17:55, 13 January 2019

2019-01-13T17:55:00Z

← Older revision		Revision as of 17:55, 13 January 2019
Line 59:		Line 59:

	<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)		<code>xfer -r 192.168.1.11</code> (Reboot M4 for changes to take effect)

			[[Category::Hardware]]

Emashzed at 16:26, 8 August 2018

2018-08-08T16:26:49Z

← Older revision		Revision as of 16:26, 8 August 2018
Line 1:		Line 1:
	Command-line tool that allow to send files and receive from an [[M4 Board]]. Possibility to add an AMSDOS header too.		Command-line tool that allow to send files and receive from an [[M4 Board]]. Possibility to add an AMSDOS header too.

	Current version : 2.0.0		Current version : 2.0.3

	Windows Executable : ~~[[Media~~:~~Xfer~~.~~zip\|Xfer~~.~~zip]]~~		Windows Executable : https://github.com/M4Duke/cpcxfer/raw/master/xfer.exe

	Repository : https://github.com/M4Duke/cpcxfer		Repository : https://github.com/M4Duke/cpcxfer
Line 13:		Line 13:
	!Effect		!Effect
	\|-		\|-
	\|\| xfer -u ipaddr file path opt \|\| Upload file, opt 0: no header add, 1: add ascii header		\|\| xfer -u ipaddr file path opt \|\| Upload file, opt 0: no header add, 1: add ascii header, 2: add binary header (specify start and exec addr. in hex)
	\|-		\|-
	\|\| xfer -d ipaddr file path opt \|\| Download file, opt 0: leave header, 1: remove header		\|\| xfer -d ipaddr file path opt \|\| Download file, opt 0: leave header, 1: remove header
Line 19:		Line 19:
	\|\| xfer -f ipaddr file slot name \|\| Upload rom		\|\| xfer -f ipaddr file slot name \|\| Upload rom
	\|-		\|-
	\|\| xfer -x ipaddr ~~path+~~file \|\| ~~Execute remote file~~		\|\| xfer -c ipaddr file \|\| Upload cartridge image (.CPR/.BIN)
	\|-		\|-
	\|\| xfer -s ipaddr \|\| Reset CPC		\|\| xfer -x ipaddr path+file \|\| Execute file on CPC
			\|-
			\|\| xfer -y ipaddr local_file \|\| Upload file on CPC and execute it immediatly (the sd card must contain folder '/tmp')
			\|-
			\|\| xfer -p ipaddr \|\| Start (plus) cartridge
			\|-
			\|\| xfer -s ipaddr \|\| Reset CPC
	\|-		\|-
	\|\| xfer -r ipaddr \|\| Reboot M4		\|\| xfer -r ipaddr \|\| Reboot M4
	\|}		\|}

Duke: /* Commands */

2017-03-14T15:27:41Z

Commands

← Older revision		Revision as of 15:27, 14 March 2017
Line 45:		Line 45:
	<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)		<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)

			Remote files can be basic/binary or SNA (emulator snapshot format).

	If you are deving roms, they can be remotely uploaded too :		If you are deving roms, they can be remotely uploaded too :

Remax at 16:13, 6 February 2017

2017-02-06T16:13:54Z

← Older revision		Revision as of 16:13, 6 February 2017
Line 1:		Line 1:
	Command-line tool that allow to send files and receive from an M4 Board. Possibility to add an AMSDOS header too.		Command-line tool that allow to send files and receive from an [[M4 Board]]. Possibility to add an AMSDOS header too.

	Current version : 2.0.0		Current version : 2.0.0

Remax: Undo revision 97165 by Remax (talk)

2017-02-06T15:50:57Z

Undo revision 97165 by Remax (talk)

← Older revision		Revision as of 15:50, 6 February 2017
Line 41:		Line 41:
	In a development environment the idea is you ie. do the following to your makefile :		In a development environment the idea is you ie. do the following to your makefile :

	<code>xfer -u 192.168.1.11 mycode.bin /0</code> (to upload the file after compilation, additional files could be uploaded too)		<code>xfer -u 192.168.1.11 mycode.bin / 0</code> (to upload the file after compilation, additional files could be uploaded too)

	<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)		<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)

Remax at 15:50, 6 February 2017

2017-02-06T15:50:15Z

← Older revision		Revision as of 15:50, 6 February 2017
Line 41:		Line 41:
	In a development environment the idea is you ie. do the following to your makefile :		In a development environment the idea is you ie. do the following to your makefile :

	<code>xfer -u 192.168.1.11 mycode.bin / 0</code> (to upload the file after compilation, additional files could be uploaded too)		<code>xfer -u 192.168.1.11 mycode.bin /0</code> (to upload the file after compilation, additional files could be uploaded too)

	<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)		<code>xfer -x 192.168.1.11 /mycode.bin</code> (to execute it)

Remax at 15:49, 6 February 2017

2017-02-06T15:49:49Z

← Older revision		Revision as of 15:49, 6 February 2017
Line 4:		Line 4:

	Windows Executable : [[Media:Xfer.zip\|Xfer.zip]]		Windows Executable : [[Media:Xfer.zip\|Xfer.zip]]

			Repository : https://github.com/M4Duke/cpcxfer

	== Commands ==		== Commands ==

Remax at 15:48, 6 February 2017

2017-02-06T15:48:38Z

← Older revision		Revision as of 15:48, 6 February 2017
Line 2:		Line 2:

	Current version : 2.0.0		Current version : 2.0.0

			Windows Executable : [[Media:Xfer.zip\|Xfer.zip]]

	== Commands ==		== Commands ==