If your VxWorks box talks to the outside world, these are vital.
| Command | Description | Example |
| :--- | :--- | :--- |
| ifConfig | Show or configure network interfaces. | ifConfig "fei0" |
| inetAddrShow | Display IP address table. | inetAddrShow |
| routeShow | Display routing table. | routeShow |
| ping | Send ICMP echo request. | ping "192.168.1.1" |
| netStat | Show network statistics and connections. | netStat |
| rpcBindShow | Show RPC bindings. | rpcBindShow |
| mRouteShow | Show multicast routes. | mRouteShow |
-> i # list tasks, find suspicious task ID
-> ti 0x8032a4c0 # inspect task 0x8032a4c0
-> checkStack 0x8032a4c0
-> semShow # see if it's waiting on a semaphore
-> d 0x80401000, 4, 64 # examine memory region
-> lkup "myFunc" # check if myFunc is loaded
-> reboot
| Command | Description |
|---------|-------------|
| intShow | Show interrupt vector usage (counts per vector) |
| intConnect <vector>, <isr>, <arg> | Connect ISR to vector (shell use limited) |
| excShow | Show exception handling vectors |
| excHookAdd <func> | Add exception handler |
| Command | Description |
|---------|-------------|
| help [command] | Show help (or help for specific command) |
| print <value> | Print value (e.g., print 0x1234) |
| printf "<fmt>", <args> | Formatted print (like C printf) |
| logShow | Show system log messages |
| timex <function> | Time execution of a function |
| period <seconds>, <function> | Run function periodically |
| repeat <count>, <command> | Repeat command N times |
| Command | Description |
|---------|-------------|
| tr | Trace tasks (context switch logging) |
| trc | Start task tracing |
| trcStop | Stop task tracing |
| b <funcName> | Set breakpoint |
| t <taskId> | Show task stack trace |
| d printf "format", args | Print to console |
| logShow | Show system log |
| logFdShow | Show log file descriptors |
| Command | Description |
|---------|-------------|
| help [cmd] | Show help |
| echo <text> | Print text |
| sleep <seconds> | Sleep for seconds |
| time <function> | Measure execution time of a function |
| benchmark | Run performance benchmarks |
| checkMem | Simple memory integrity check |
Note:
Managing a real-time operating system (RTOS) like VxWorks requires a specialized set of commands, primarily executed through its Kernel Shell
. Unlike standard Linux or Windows prompts, the VxWorks shell often allows you to call C functions directly as commands, meaning syntax usually requires parentheses and quoted strings. Stack Overflow Essential Task Management
These commands allow you to control and monitor individual processes (tasks) in the system.
: Displays a summary of all active tasks, including their IDs and status. sp(entryPt, arg1, ...) : Spawns a new task starting at the specified function. td(taskId) : Deletes a task by its ID or name. ts(taskId) : Suspends a task, pausing its execution. tr(taskId) : Resumes a suspended task. ti(taskId)
: Displays detailed information from the Task Control Block (TCB), including register values. tt(taskId) : Shows a task's stack trace, useful for debugging crashes. Google Groups System & Memory Diagnostics
Use these to inspect the target hardware's state and memory contents. d(address, units, width) vxworks command cheat sheet
: Dumps memory contents starting at a specific hexadecimal address. m(address, width) : Modifies memory at a given address interactively.
: Displays overall system memory usage, including free and allocated blocks.
: Lists all hardware devices currently recognized by the system. lkup "string"
: Searches the system symbol table for functions or variables containing that string. printErrno(value)
: Decodes a numeric error code into a human-readable description. Stack Overflow Networking Commands For troubleshooting connectivity and protocol stacks: VxWorks Command Cheat Sheet | PDF | Booting - Scribd
VxWorks supports TCP/IP stacks and network configuration via shell commands. If your VxWorks box talks to the outside
routeAdd / routeShow — Manage routing table entries.
hostGetByName / inet_ntoa — DNS and address utilities.
ftp, tftp, rlogin, telnet utilities — Transfer files and get shell access; often used for loading modules or transferring configuration.
Best practice: ensure correct endianness and cache coherency when transferring binary modules; prefer TFTP for small development images, NFS for root file systems.
| Command | Description |
|---------|-------------|
| ls [path] | List directory contents |
| cd <path> | Change directory |
| pwd | Show current directory |
| cat <file> | Print file contents |
| copy <src> <dest> | Copy file |
| rm <file> | Delete file |
| mkdir <dir> | Create directory |
| rmdir <dir> | Remove empty directory |
| devs | List all devices |