Difference between revisions of "CPC M4 xfer tool"
| (6 intermediate revisions by 4 users not shown) | |||
| 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. | + | Current version : 2.0.3 |
| − | Windows Executable : | + | 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 - | + | || xfer -c ipaddr file || Upload cartridge image (.CPR/.BIN) |
|- | |- | ||
| − | || xfer -s ipaddr | + | || 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 | ||
|} | |} | ||
| − | |||
| Line 41: | Line 46: | ||
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) | ||
| − | + | 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 : | ||
| Line 54: | 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]] | ||
Latest revision as of 12:55, 13 January 2019
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.3
Windows Executable : https://github.com/M4Duke/cpcxfer/raw/master/xfer.exe
Repository : https://github.com/M4Duke/cpcxfer
Commands
| Command | Effect |
|---|---|
| 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 -f ipaddr file slot name | Upload rom |
| xfer -c ipaddr file | Upload cartridge image (.CPR/.BIN) |
| 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 |
Example : If your m4 has IP number 192.168.1.11, the following code will run zynaps from given directory.
xfer -x 192.168.1.11 /games/zynaps/zynapsex.bas
Want to leave it again you could reset the cpc by:
xfer -s 192.168.1.11
In a development environment the idea is you ie. do the following to your makefile :
xfer -u 192.168.1.11 mycode.bin / 0 (to upload the file after compilation, additional files could be uploaded too)
xfer -x 192.168.1.11 /mycode.bin (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 :
xfer -f 192.168.1.11 yancc.rom 3 "YANCC" (upload to slot 3)
xfer -f 192.168.1.11 launcher.rom 4 "The Launcher" (upload to slot 4)
xfer -r 192.168.1.11 (Reboot M4 for changes to take effect)
