|
|
|
|
|
|
|
||
|
||
|
|
||
Aug 1999 |
Revision 1.05 |
|
Persistor Instruments Inc. |
© 1998 All rights reserved. |
|
|
|
|
|
|
|
|
||
|
||
|
|
||
Aug 1999 |
Revision 1.05 |
|
Persistor Instruments Inc. |
© 1998 All rights reserved. |
|
PicoDOS Command ShellThe PicoDOS command shell provides a very DOS-like interface for program development and file maintanance. Wherever practical, PicoDOS uses the same commands and command switches that DOS machines use to minimize the amount of new things you have to learn to work with the CF1.Where necessary, PicoDOS adds several new commands to accomodate the special needs of this deeply embedded controller.
You have complete control over how the CF1 behaves at startup, but as delivered and by default, the CF1 starts up in the PicoDOS command shell and displays a signon message and prompt similar to the following:
--------------------------------------------------------------
Persistor CF1 - Persistor Instruments Inc. - www.persistor.com
SN 10507 - PicoDOS V2.00 - BIOS V2.00 - PBM V2.00
(C) 1998 Peripheral Issues - www.periph.com
--------------------------------------------------------------
C:\>The "C:\>" prompt should look fairly familiar to DOS users and this is what you'll see if a CompactFlash card with a valid DOS partition is installed when you start up. With no card installed, you'll instead see the "PicoDOS>" prompt and some of the card and file related commands will be unavailable. At any time, you can get a list of the PicoDOS commands by typing "H", "HE", "HELP", or "?" followed by the enter key. You'll then see something like:
C:\>? ========= PicoDOS built-in commands (plus .PXE and .BAT Files) ========= ATTRIB [+ - RASH] [d:][p][name] BACKROM [d:][path] [/SVI] BAUD [newrate] [/Q/P/E/O/N/2] BOOT [PICO][PBM][APP] CAPTURE [d:][p]fn [/Dx/B/N/E] CCC Card Change [delay secs] CHDIR [drive:][path] CHKDSK [d:][p][fn] [/F][/I] COPY source dest [/V] DUMP file[start[,end]] DATE [mm-dd-yy[yy] [time] DEL [drv:][pth][name] [/P] DIR [d:][p][fn] [/PWBLV4A:a] ERASE [drv:][pth][name] [/P] FDISK [/P][/Q] FORMAT [drv:][/V[:label]] [/Q/E] GO args... | addr /A | /Fn LO [ofs][;Bx[+]] [;G] MOUNT V: DEV [0..3] MKDIR [drive:][path] MD display [range] MM modify [address] ML disassemble [range] MON (or PBM) Reset to PBM PROMPT [text] PR pin read <1..50> PC pin clear <1..50> PS pin set <1..50> PT pin toggle <1..50> PM pin mirror <1..50> TIME [hh:mm[:ss[.xx][a|p]] TYPE [drv:][pth][name] REN [d:][p]oldname newname RESET (hard reset) RMDIR [drive:][path] SAVE file[start][end] SD sector dump [d:][range] SET [var=[str]] [/SLFE?] XS [/Q][/X][/C]file XR [/Q][/X][/C][file] YS [/Q][/G]file[,file...] YR [/Q][/G] VER Firmware versions ZOOM Check PicoZOOM
If you're reading this online with a browser, you can click on any of the above commands to get to their full descriptions. When your working on the CF1 and want more details on any of the commands, you can type HELP followed by the command name, or the command name followed by the "/?" switch. For example, both of the following commnds yield the same results:
C:\>help dir ( or C:\>dir /? )
Displays a list of files and subdirectories in a directory.
DIR [drive:][path][filename] [/P] [/W] [/A[[:]attributes]]
[/S] [/B] [/L] [/V] [/4]
[drive:][path][filename]
Specifies drive, directory, and/or files to list.
(Could be enhanced file specification or multiple filespecs.)
/P Pauses after each screenful of information.
/W Uses wide list format.
/A Displays files with specified attributes.
attributes D Directories R Read-only files
H Hidden files A Files ready for archiving
S System files - Prefix meaning not
/B Uses bare format (no heading information or summary).
/L Uses lowercase.
/V Verbose mode.
/4 Displays year with 4 digits (ignored if /V also given).Like DOS, PicoDOS also supports batch files (text files with the ".BAT" extension) and EXE files (binary applications with the ".PXE" extension). PicoDOS uses a different naming convention for binary executables - not to confuse you, but to keep from confusing DOS or Windows when you move the CompactFlash to your PC to offload data. Some interesting and unpleasant things can happen when you double-click a 68K binary with a ".EXE" name from Windows.
Also like DOS, PicoDOS looks for a file named "AUTOEXEC.BAT" on the root directory of the first partition of an installed CompactFlash card and automatically runs that batch file from startup or resets. This capability, combined with tha ability to run EXE (".PXE") files, provides you with tremendous flexibility in structuring how your application executes and interacts with its environment. You're no longer forces to create huge monolithic programs that run from flash (though with 750KB of free flash you still can!).
You can now, for example, create a run-time application suite consisting of several discrete applications that execute and perform specific functions at various stages of a deployment. One application could perform all of the initial user interface and options selections during setup and it could save these options to a configuration file that would be used by other applications at runtime and by data analysis programs on recovery. The setup program could also automatically create the AUTOEXEC.BAT file that would run an appropriate version of one of the data collection programs (remember, we have sub-directorys and up to 48MB to work with). The collection program could periodically pass control to data reduction or garbage collection programs to extend the deployment.
Constructed this way, you could much more easily deal with a request for foriegn language version of your program. You could alse create a friendly graphical interface for your PC using VB or Java that would normally generate the runtime configuration file, but that could still allow crucial changes in the field with more primitive methods. When you approach a design using the CF1, try to get away from the mindset of traditional little controllers and make use of some of the new tools that come with a real file based operating system.
To get an executable file onto a CF card, just use MotoCross to load it the way you would for a normal run from RAM. When MotoCross finishes the load, it sends PicoDOS a 'G' so that you can simply hit the <enter> key to start the program. Don't do it. Instead, type an 'S', followed by a space, followed by the name you want for the file (PicoDOS will fill in the .PXE if you don't specify the extension), then hit enter. GS is an alias for the SAVE command, so PicoDOS will save the loaded image to a .PXE file which can then be run by typing the first part of the name. The example below shows the load and save session for the PicoDAQ example with your input shown in red.
C:\> ### 31252 bytes loaded, <return> to GO 10000 Gs picodaq <enter> Saving 31252 bytes to PICODAQ.PXE...
You can get .BAT text files onto the card by copying or XMODEMing them over from your PC, or you can use the CAPTURE command as described ahead.
Custom Command ShellsYou can't change the appearance or command set offerred by PicoDOS since its hard-wired into flash. You can however build your own command shell using any or all of the PicoDOS commands within you own application. You may, for example, want your end users to be able to enter a mode where they can perform limited file maintainance, but you do not want them accidentally doing a FORMAT or FDISK. The CMD Demos examples show how easy it is to add this capability to your own applications.
Non-DOS CommandsThe follow PicoDOS command reference provides details on all of the PicoDOS commands, but we just want to introduce you to some of the CF1 specific commands that won't already know from having worked with DOS on a PC.
The PicoDOS command shell does not replace the Persistor Boot Monitor - it continues to live at the base of flash, and you can always get back to the PBM from the command shell by typing "PBM", or tying /IRQ5, which is pin 39 on connector C to ground while cycling the power
The command shell does however replicate some of the PBM functions so that you can conduct the majority of your business in PicoDOS which is more versatile than the PBM. The following PBM commands have PicoDOS equivalents:
GO args... | addr /A | /Fn LO [ofs][;Bx[+]] [;G] MD display [range] MM modify [address] ML disassemble [range] PR pin read <1..50> PC pin clear <1..50> PS pin set <1..50> PT pin toggle <1..50> PM pin mirror <1..50>
Though you can directly transfer files between the CompactFlash cards and a DOS computer with PC Card slots using the PC Card adapter or using any number of external readers that are available, it's sometimes more convenient to just transfer the files serially. The PicoDOS command shell supports XMODEM (128, 1K, and CRC) and YMODEM (including batch) file transfers in both directions, and at rates up to 230,400 baud.
XS [/Q][/X][/C]file XR [/Q][/X][/C][file] YS [/Q][/G]file[,file...] YR [/Q][/G] BAUD [newrate] [/Q] SAVE file[start][end] DUMP file[start[,end]] CAPTURE [d:][p]fn [/Dx/B/N/E]
The remaining PicoDOS commands allow you to control the Persistor's behavior at power-up or reset, as well as access the Persistor Boot Monitor and reset the Persistor.
BOOT [PICO][PBM][APP] CCC (card change) RESET (hard reset) PBM (exit to PBM)
PicoDOS Command
ReferenceATTRIB [+ - RASH] [d:][p][name] BACKROM [d:][path] [/SVI] BAUD [newrate] [/Q/P/E/O/N/2] BOOT [PICO][PBM][APP] CAPTURE [d:][p]fn [/Dx/B/N/E] CCC Card Change [delay secs] CHDIR [drive:][path] CHKDSK [d:][p][fn] [/F][/I] COPY source dest [/V] DUMP file[start[,end]] DATE [mm-dd-yy[yy] [time] DEL [drv:][pth][name] [/P] DIR [d:][p][fn] [/PWBLV4A:a] ERASE [drv:][pth][name] [/P] FDISK [/P][/Q] FORMAT [drv:][/V[:label]] [/Q/E] GO args... | addr /A | /Fn LO [ofs][;Bx[+]] [;G] MOUNT V: DEV [0..3] MKDIR [drive:][path] MD display [range] MM modify [address] ML disassemble [range] MON (or PBM) Reset to PBM PROMPT [text] PR pin read <1..50> PC pin clear <1..50> PS pin set <1..50> PT pin toggle <1..50> PM pin mirror <1..50> TIME [hh:mm[:ss[.xx][a|p]] TYPE [drv:][pth][name] REN [d:][p]oldname newname RESET (hard reset) RMDIR [drive:][path] SAVE file[start][end] SD sector dump [d:][range] SET [var=[str]] [/SLFE?] XS [/Q][/X][/C]file XR [/Q][/X][/C][file] YS [/Q][/G]file[,file...] YR [/Q][/G] VER Firmware versions ZOOM Check PicoZOOM
ATTRIB -- ?|
Usage: |
ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [[drive:][path]filename]
+ Sets an attribute
- Clears an attribute
R Read-only file attribute
A Archive file attribute
S System file attribute
H Hidden file attribute
|
|
Description: |
Displays or changes file attributes. |
BACKROM --
Backup/Restore ROM to/from CompactFlash files|
Usage: |
BACKROM [drive:][path]filename [/B] [/P] [/I]
filename Specifies the file to save to
/S System only (PicoDOS & BIOS)
/V Include Virtual EEPROM
/I Just binary image (no CPM68K header)
|
|
Description: |
Backup application in flash memory to CPM68K file |
BAUD -- View/Change the
baud rate of the main UART|
Usage: |
BAUD [newrate] [/Q/P/E/O/N/2]
/Q Quiet mode. Do not prompt
/P Persistant change (sets SYS.BAUD)
/E Even parity, 1 stop bit
/O (letter) Odd parity, 1 stop bit
/N (default) No parity, 1 stop bit
/2 No parity, 2 stop bits
BAUD with no arguments displays the current setting.
|
|
Description: |
When you request a new baud rate, PicoDOS prompts you to change your host baud rate then hit a key to continue. The CF1 can handle any standard rate from 75 to 230,400, though most PC's can only go up to 115,200. PicoDOS always reverts back to 9600 baud at reset, though you can make an AUTOEXEC.BAT file entry to force any other rate at startup. Typing baud by itself displays the current baud rate which is rarely exactly what you specified, instead being the actual closest baud rate the hardware can produce. If you specify the optional quiet flag (-Q or /Q), there will be no messages or prompts. This is primarily for use in batch files where interaction may not be desirable. |
BOOT -- Specify action
to take on reset or power-up|
Usage: |
BOOT [PICO][PBM][APP]
PICO Run PicoDOS at startup.
PBM Run the Permanent Boot Monitor at startup.
APP Run the application at 0xE4000 at startup.
BOOT with no arguments displays the current setting.
|
|
Description: |
The BOOT command with no arguments displays the current bootup operation which will be either to the PBM monitor, to PicoDOS, or to the main user application area in flash. Specifying 'PICO' as the argument causes the Persistor to launch PicoDOS by default at reset or power-up. Using the "PBM" option tells the Persistor to boot up into the Persistor Boot Monitor on power-up or reset. You can always force the Persistor to boot into the PBM by tying /IRQ5 to ground at power-up. |
CAPTURE -- Capture
bytes from main UART into a file|
Usage: |
Capture incomming RS-232 characters to a file
CAPTURE [drive:][path]filename [/D delim] [/B] [/N] [/E]
filename Specifies the file to save to.
/D delim Stop capture on detection of the specified value.
/B Stop capture on detection of BREAK.
/N Insert line feeds after carriage returns.
/E Echo received characters.
|
|
Description: |
The CAPTURE command copies everything coming in from the serial port into RAM until you send a CTRL-C character (the default), or until it sees the specified delimiter. It then copies the whole thing to the filename you specified. Using TYPE with CAPTURE is a convenient way to edit small batch files with most modern terminal programs (like MotoCross). TYPE the current file from PicoDOS, select and copy the text from your terminal program, paste into an editor and make the changes, select and copy again, the paste the update back after issuing the CAPTURE command. It's actually easier than it reads. The option /N switch causes capture to append linefeed characters '\n' to incoming carriage returns '\r'. If your captures don't display correctly when you TYPE them back, try using this switch. |
CCC -- Cooperative Card
Change|
Usage: |
Change (Insert or Remove) a CompactFlash card.
CCC [delay secs]
delay secs Timeout in seconds for remove/insert
|
|
Description: |
The CCC command puts the CF1 into SUSPEND mode until it detects a card change. In this mode, it may be possible to remove or insert a CompactFlash card without crashing the CF1. This command is offered as a convenience only. |
CD -- Change
directory|
Usage: |
CHDIR [drive:][path]
CHDIR[..]
CD [drive:][path]
CD[..]
.. Specifies that you want to change to the parent directory.
Type CD drive: to display the current directory in the specified drive.
Type CD without parameters to display the current drive and directory.
|
|
Description: |
Select the current working directory |
CHKDSK -- Checks a
disk and displays a status report|
Usage: |
CHKDSK [drive:][[path]filename] [/F] [/I]
[drive:][path] Specifies the drive and directory to check.
filename Specifies the file(s) to check for fragmentation.
/F Fixes errors on the disk.
Type CHKDSK without parameters to check the current disk.
|
|
Description: |
Checks a disk and displays a status report. |
COPY -- Copy a
file|
Usage: |
COPY source destination [/V]
source Specifies the file to be copied.
destination Specifies the directory and/or filename for the new file(s).
/V Verifies that new files are written correctly.
|
|
Description: |
This command is similar to the DOS copy command. It will copy the file specified in source to the filename specified in destination. Bear in mind that this operation will fail if there is not enough space remaining on the CompactFlash card, if source does not exist or if destination already exists. |
DATE -- Set or retrieve
the date|
Usage: |
DATE [mm-dd-yy[yy] [time] [/I] [/E] [/P]
Type DATE without parameters to display the current date settings
Default is US date format mm/dd/yy
/I Expect ISO date format: yy/mm/dd
/E Expect European date format: dd/mm/yy
/P Prompt for date and time.
|
|
Description: |
Set the real time clock from the date (and optionally time) based on parameters in the form: [mm/dd/yy[yy] [hh:mm:ss [a|p]]. The date defaults to U.S. conventions but can be changed to European or ISO format with command switches. Valid field separaters are dashes, periods, or slashes ('-./'). Two digit years are assumed to be 19yyfor 70 and above, 20yy for all other two digit values below that. |
DEL -- Delete a file|
Usage: |
DEL [drive:][path]filename [/P]
ERASE [drive:][path]filename [/P]
[drive:][path]filename Specifies the file(s) to delete. Specify multiple
files by using wildcards.
/P Prompts for confirmation before deleting each file.
|
|
Description: |
This command is similar to the DOS delete command. It will delete the file specified in filename. Once deleted, there is no way to recover a file. The DEL command will not prompt you before deleting the specified file. The ERASE command is synonymous with the DEL command. |
DIR -- List the
directory of the CompactFlash card|
Usage: |
DIR [drive:][path][filename] [/P] [/W] [/A[[:]attributes]]
[/S] [/B] [/L] [/V] [/4]
[drive:][path][filename]
Specifies drive, directory, and/or files to list.
(Could be enhanced file specification or multiple filespecs.)
/P Pauses after each screenful of information.
/W Uses wide list format.
/A Displays files with specified attributes.
attributes D Directories R Read-only files
H Hidden files A Files ready for archiving
S System files - Prefix meaning not
/B Uses bare format (no heading information or summary).
/L Uses lowercase.
/V Verbose mode.
/4 Displays year with 4 digits (ignored if /V also given).
|
|
Description: |
This command is identical to the DOS DIR command. It will give you a list of all the files on the currently inserted CompactFlash card. As of the writing of this documentation, PicoDOS did not support subdirectories but when this functionality is added, subdirectories will also be listed by the DIR command in a similar fashion as in DOS. The DIR command will display an error message if there is no card inserted. Use CTRL-C to abort a long directory listing. |
DUMP -- Dump file in
Hex and ASCII|
Usage: |
DUMP [drive:][path]filename [start [,end]]
|
|
Description: |
The DUMP command displays the contents of the specified file as lines of hexadecimal numbers followed by the mating ASCII characters (where valid). You can also specify an optional starting and ending byte offset into the file where display should begin and end. Any output will be in the following form: 00005850 1F2D 7320 222B 012E 593F 325F 2133 3072 .-s "+..Y?2_!30r 00005860 0839 2E77 323D 116D 6A4C 437C 404F 0B02 .9.w2=.mjLC|@O.. |
FDISK -- Partition
a CompactFlash card|
Usage: |
FDISK [/Q] [/P] [/M]
/P Partition as single, maximum capacity volume
/M Partition multiple volumes with an interactive session
/Q Quite mode - no prompts or messages
Type FDISK without parameters to view the current partitions
|
|
Description: |
Displays or modifies a cards partitions |
FORMAT --
Initialize a CompactFlash card for use|
Usage: |
FORMAT drive: [/V[:label]] [/Q]
/V[:label] Specifies the volume label
/Q Quite mode - no prompts or messages
/E Erase each and every sector
|
|
Description: |
Formats a card for use with PicoDOS. |
GO -- Run a program in
memory|
Usage: |
Run program in memory
G or GO [addr] [arg1] [argN...] [/A] [/F[n]]
addr Absolute hex address for /A switch.
argN Command line arguments to pass.
/A First argument is an absolute hex address.
/Fn Target is standard flash application at 0xE40000
or 0xEn0000 where n is typically 4, 8, or C
|
|
Description: |
The GO command causes execution to jump to the address specified. This command is normally executed after downloading a new application, during the development cycle, or to start execution of an application stored in the flash memory from PicoDOS. |
HELP -- Display
command list and usage information|
Usage: |
HELP or ?
|
|
Description: |
This command displays a short list of all the commands documented here, along with brief usage templates. At this time detailed command descriptions are not available by using the HELP command. |
LO -- Load Motorola
S-Records Over the Serial Port|
Usage: |
LO [offset] [Bx[+]] [G]
|
|
Description: |
The LO command prepares the CF1 to receive executable code in the form of Motorola S-Records. Most often the LO command is invoked behind the scenes by MotoCross when downloading the latest trial in your development cycle. Offset specifies where in memory the CF1 should load the new code. The B option controls the baud rate of the transfer for the period of the transfer only and G tells the Persistor to "go" to the code for execution immediately after loading. The + option allows to load to overwrite the Persistor Boot Monitor; a highly dangerous activity unless you're updating the PBM. The syntax and number codes for the B option is as follows: 0 = 9600 1 = 19200 2 = 38400 3 = 57600 4 = 76800 6 = 115200 Examples: C:\> LO B3 ; Loads at 57600 baud C:\> LO B1G ; Loads at 19200 baud and executes C:\> LO 00010000 B2 ; Loads to offset 10000 at 38400 baud |
MD -- Memory Display|
Usage: |
MD start [end]
|
|
Description: |
The MD command displays the contents of the memory starting at start and displaying 16 bytes or until end, if it was specified. The output of the MD command looks like the following: 0000E2F0 1086 0008 0000 1000 0004 0002 1900 4000 ..............@. Displaying a large area of memory with the MD command can be aborted by pressing <Control C>. A better method of viewing large chunks of memory might be to use the SAVE command and offload the memory as a file, depending on your specific situation. |
MKD -- Make
directory|
Usage: |
MKDIR [drive:]path
MKD [drive:]path
|
|
Description: |
Creates a directory. |
ML -- List Memory
Contents With Disassembly
|
Usage: |
ML start [end]
|
|
Description: |
The ML command lists the contents of the specified address or range of addresses and disassembles their contents if possible. It will produce listings like the following: C:\> ML C070 C07A 00C070 SBCD D4,D3 00C072 ORI.B #$02,D0 00C076 DC.W $FFDA ; ???? 00C078 ORI.B #$1B78,D1 ; 'x' |
MM -- Memory Modify|
Usage: |
MM [address]
|
|
Description: |
Invoking the MM command starts a line editor that allows you to modify memory starting at address. The editor has four commands, "^", "v", "=", ".", which move back two bytes, forward two bytes, redisplay the current address, and stop editing, respectively. Each line displayed by the editor looks like the following: 0000C012 0001 ? At this prompt, for each address, you can use any of the editor commands or you can enter a new hex value for that pair of bytes. |
MOUNT -- Mount a
CompactFlash card|
Usage: |
not yet
|
|
Description: |
not yet |
PBM -- Exit to the
Persistor Boot Monitor|
Usage: |
PBM
MON
|
|
Description: |
The PBM command forces execution back to the Persistor Boot Monitor, whether or not there's an application burned in flash, and independent of the BOOT setting. This is the same a calling ResetToMon() from inside your application. |
PROMPT -- ?|
Usage: |
PROMPT [text]
text Specifies a new command prompt
/P Persistant change (sets SYS.PICOBAUD)
Prompt can be made up of normal characters and the following special codes:
$Q = (equal sign)
$$ $ (dollar sign)
$T Current time
$D Current date
$P Current drive and path
$V PicoDOS version number
$N Current drive
$G > (greater-than sign)
$L < (less-than sign)
// "$B | (pipe)
$H Backspace (erases previous character)
$E Escape code (ASCII code 27)
$_ Carriage return and linefeed
$S Space character (ASCII code 32)
$C Comma character (ASCII code 44)
$Xhh Any hexadecimal character
Type PROMPT without parameters to reset the prompt to the default setting
|
|
Description: |
Changes the PicoDOS command prompt. |
PC -- Pin Clear|
Usage: |
PC <1..50>
|
|
Description: |
The PC command sets the designated I/O pin to logic 0. If the pin was previously configured as an input, it will be configured as an output after the execution of the PC command. |
PM -- Pin Mirror|
Usage: |
PM <1..50>
|
|
Description: |
The PM command reads the value of the specified pin at the time the PM command is executed as an input then reconfigures the pin as an output and asserts the value that was read immediately beforehand. |
PR -- Pin Read|
Usage: |
PR <1..50>
|
|
Description: |
The PR command displays the current logic value (0 or 1) of the specified pin. If the specified pin was configured as an output before the use of the PR command, it will be configured as an input afterwards. |
PS -- Pin Set|
Usage: |
PS <1..50>
|
|
Description: |
The PS command sets the designated I/O pin to logic 1. If the pin was previously designated as an input, it will be configured as an output after the execution of the PS command. |
PT -- Pin Toggle|
Usage: |
PT <1..50>
|
|
Description: |
The PT command sets the designated I/O pin to the logical inverse of its current value. (i.e.. Logic 1 becomes logic 0 and vice versa) If the pin was previously designated as an input, it will be configured as an output after the execution of the PC command. |
RD -- Remove
directory|
Usage: |
Removes (deletes) a directory.
RMDIR [drive:]path
RD [drive:]path
|
|
Description: |
REN -- Rename a
file
|
Usage: |
REN oldname newname
|
|
Description: |
REN changes the name of a file stored on the CompactFlash card from oldname to newname. If a file named newname already exists or if the file oldname does not exist, the command will fail. |
RESET -- Perform a
hardware reset|
Usage: |
RESET
|
|
Description: |
The RESET command causes a complete system reset, which will either enter the Persistor Boot Monitor, run an application, or put you back into PicoDOS, depending on the current BOOT setting. This is the same a calling Reset() from inside your application. |
SAVE -- Save a file|
Usage: |
Save a block of memory to a file
SAVE [drive:][path]filename startaddr endaddr
|
|
Description: |
The SAVE command command copies a block of memory to a file on the CompactFlash. This could be used to capture the results of a RAM logging session, but is more likely used to move programs loaded into RAM onto the CompactFlash for later execution. If no start and end address parameters are provided, SAVE uses the information from the last LO command (or from MotoCross high speed loads) to get the address range. Do not run a program in RAM prior to saving it. It may work, but you should expect some bizarre results. You can run the program immediately after saving if you like. The GS and GSAVE variations are provided as a convenience for saving the last load from MotoCross, which has already automatically entered the initial G for the typical <enter> to GO and test. You can instead just type S filename <enter> which forms the GS filename command (without your needing to specify the ".RUN" extension) and save the executable image to CompactFlash. |
SD -- Display the
contents of drive sectors in hexadecimal
|
Usage: |
SD [start [,end]]
|
|
Description: |
Displays the contents of drive sectors in hexadecimal |
SET -- Display, set, or
remove PicoDOS environment variables|
Usage: |
SET [variable=[string]] [/SLFE?]"
variable Specifies the environment-variable name
string Specifies a series of characters to assign to the variable
/S Query for variable name and string data
/L Query for variable name and long integer data
/F Query for variable name and floating point data
/E Erase all of the environment variables
Type SET without parameters to display the current environment variables
|
|
Description: |
Displays, sets, or removes PicoDOS environment variables. |
TIME -- Set or retrieve
the time|
Usage: |
TIME [hh:mm[:ss[.xx][a|p]]
|
|
Description: |
Set the real time clock time in the form: [hh:mm:ss [a|p]]. Type TIME without parameters to display the current date settings |
TYPE -- Display the
contents of a file|
Usage: |
Displays the contents of text files.
TYPE [drive:][path]filename
|
|
Description: |
The TYPE command outputs the contents of filename to the serial port. This can often be helpful while debugging batch files or checking data. Be cautious when viewing large files with the TYPE command, it does not stop after each page and can take a very long time to view a large file at 9600 baud. You can abort the TYPE command by pressing <Control-C> |
VER -- Display PicoDOS
version information|
Usage: |
Displays the CF1 and PicoDOS version numbers.
|
|
Description: |
This command displays returns the PicoDOS target, serial number, and version and release numbers. |
XR -- Receive File Using
XMODEM Protocol|
Usage: |
XR [/Q] [/X] [/C] [file]
|
|
Description: |
The XR command initiates an XMODEM session on the CF1 end of the serial connection at the baud rate specified by the BAUD command. It is expected that you will initiate the sending side of the XMODEM session on your terminal program (or MotoCross.) XR implements a smart XMODEM protocol hunt and should synchronize with hosts that support original 128 byte block XMODEM, CRC, and 1k XMODEM. You can force it to try original XMODEM first by using the -X or /X option, or XMODEM CRC with the -C or /C option. The /Q option is for quiet operation and will suppress prompts and messages. If you don't specify a filename, the XR command names the incoming file "RECEIVE.NNN" where NNN is the next available extension number. |
XS -- Send File Using
XMODEM Protocol|
Usage: |
XS [/Q] [/X] [/C] file
|
|
Description: |
The XS commands initiates an XMODEM session at the CF1 end, and it's expected that you have already told the host computer to prepare to receive a file with the XMODEM protocol. The XS command implements a smart XMODEM protocol hunt and should synchronize with hosts that support original 128 byte block XMODEM, CRC, and 1k XMODEM. You can force it to first try original XMODEM with the -X or /X option, or XMODEM CRC with the -C or /C option. The /Q option is for quiet operation and will suppress prompts and messages. |
YR -- Receive File Using
YMODEM Protocol|
Usage: |
YR [/Q] [/G]
|
|
Description: |
The YR commands is similar to the XR command, but prepares the CF1 to receive a file with the YMODEM file transfer protocol. It is assumed that after you invoke YR you will initiate the YMODEM send function of your host terminal program. The YMODEM protocol supports batch file transfers with automatic file naming. This is the preferred protocol if it is supported by your host terminal program (MotoCross is not capable of executing YMODEM transfers) for speed and convenience. YR defaults to normal YMODEM batch, but can be forced to YMODEMG (no error checking/recovery) with the -G or /G option. -Q inhibits the routines from emitting messages. |
YS -- Send File Using
YMODEM Protocol|
Usage: |
YS [/Q] [/G] file [,file...]
|
|
Description: |
The YS commands is similar to the XS command, but prepares the CF1 to send a file with the YMODEM file transfer protocol. It is assumed that when you invoke YS you will immediately initiate the YMODEM receive function of your host terminal program. The YMODEM protocol supports batch file transfers with automatic file naming. This is the preferred protocol if it is supported by your host terminal program(MotoCross is not capable of executing YMODEM transfers) for speed and convenience. YS defaults to normal YMODEM batch, but can be forced to YMODEMG (no error checking/recovery) with the -G or /G option. -Q inhibits the routines from emitting messages. |
ZOOM -- Tests card for
PicoZOOM acceleration
|
Usage: |
ZOOM
|
|
Description: |
This command check the CompactFlash card and reports on whether or not it is PicoZOOM accelerated |
|
|
|
|
|
|
Tel: 508-759-6434 |
|
Fax: 508-759-6436 |
|
|
||