Bootloader Command Reference
The Seco-bootloader for Trizeps-modules supports many different commands to:
Update/Modify the flash-contents ( bootloader, WinCE-Image, registry,…).
Modify hardware registers or memory.
Test Trizeps functionality.
Modify boot-behaviour.
Boot from different devices.
These commands may be used in a boot script ( autoboot.bat).
Not all commands are supported on all modules.
You enter the bootloader by using a Hyperterminal:
Connect your Trizeps-module with your PC using a serial-cable (level-shifter like max232 needed).
Open Hyperterminal (or similiar program) with 38k4 Baud, 8 Bit, No Parity, 1 Stop-bit.
Press <ESC> while powering up the Trizeps.
Now you should see the boot-prompt.
Numbers can be entered in decimal or hexadecimal. If 0x
is preceeding a number hexadecimal is assumed.
Misc commands
?
List the known commands
sleep
Sleep specified amount of micro-seconds.
Usage: sleep <micro-seconds>
getfreq
Get current processor frequency.
Usage: getfreq
setfreq
Set current processor frequency.
Usage: setfreq <processor-specific….>
gpio
A list of the current gpio-settings.
Usage: gpio
initgpio
Set level and direction of a specified gpio-pin.
Usage: initgpio <gpio-pin> <0: Output, 1: Input> <level>
setgpio
Set level of a gpio.
Usage: setgpio <gpio-pin> <level>
getgpio
Get level of a gpio.
Usage: getgpio <gpio-pin>
setpwm
Set PWM (pulse-width-modulation) value of a gpio. GPIO must be capable of PWM.
Usage: setpwm <gpio-pin> <value in percent>
display
Show stored boot-bitmap.
Usage: display
contr
Set value of contrast-eepot.
Usage: contr <steps +/- up/down>
backlight
Set value of backlight-eepot.
Usage: backlight <steps +/- up/down>
ad5242_contr
Set contrast-channel of ad5242-poti. Boot-Bitmap with ad5242-configuration must be loaded.
Usage: ad5242_contr <value in percent>
ad5242_back
Set backlight-channel of ad5243-poti. Boot-Bitmap with ad5242-configuration must be loaded.
Usage: ad5242_back <value in percent>
rtc
Show realtime-clock. This only works for a PCF8593.
Usage: rtc
srtc
Set realtime-clock. This only works for a PCF8593.
Usage: srtc DDMMYY HHMMSS
jump
Start execution at the specified memory-address.
Usage: jump <memory-address>
Flash and Bootloader-Configuration Routines
eflashb0
Erases whole flash, except the bootloader.
Usage: eflashb0
epsm
Erase flashdisk-contents. The default flash-memoryarea for the flashdisk is assumed.
Usage: epsm
ereg
Erase persistant registry. Fallback registy of Windows CE will be used.
Usage: ereg
store
Store a boot-script from a memory-card to flash. This script will be run on every start.
Usage: store <device-name> <filename>
showbfile
Show stored boot-script.
Usage: showbfile
ebfile
Delete boot-script.
Usage: ebfile
fuselist
Shows configuration options. i.e. if to look for autoboot.bat on startup.
Usage: fuselist
fuseburn
Burns a fuse. For a list of fusenumbers see fuselist.
Fuses can only be restored by re-flashing the bootloader.
Usage: fuseburn <fusenumber>
Commands for memory/register-access
cb
Change byte (8bit) at given address.
Usage: cb <address> <value>
cw
Change word (16bit) at given address.
Usage: cw <address> <value>
cl
Change long (32bit) at given address.
Usage: cl <address> <value>
dump
Dump bytes (8bit) at given address and length.
Usage: dump <address> <length>
dumpw
Dump words (16bit) at given address and length.
Usage: dumpw <address> <length>
dumpl
Dump long (32bit) at given address and length.
Usage: dumpl <address> <length>
Test Routines
ramtest
Tests RAM.
Usage: ramtest
memtest
Tests memory in a given region.
Usage: memtest <start-address> <stop-address>
bursttest
Copy memory-contents from one location to another and returns speed and error-rate.
Usage: bursttest <from-address> <to-address> <length>
touch
Shows measured touch-values.
Usage: touch
adc
Shows values measured on analog-inputs.
Usage: adc
sja1000
Tests sja1000-CAN-controller.
Usage: sja1000 <controller: 1 or 2>
Bootloader Device Interface
Usable in Trizeps4/5 bootloader.
The bootloader device interface allows a more generic way of handling devices integrated in the bootloader.
devices
List all known devices.
Usage: devices
device
Set the current active device on which other device-interface-commands should act on.
Usage: device <device-name>
open
Open device. This initializes the specified device.
Usage: open <device-name>
close
Close device. This deinitializes the specified device.
Usage: close <device-name>
probe
Probe if device is present.
Usage: probe <device-name>
reset
Reset device.
Usage: reset <device-name>
read
Read from the current device. i.e. capture bytes from COM-port.
Usage: read <address> <number of bytes>
write
Write to the current device. i.e. output bytes on a COM-port.
Usage: write <address> <number of bytes>
seek
Set the file-pointer of the current device. i.e. when using flash or memory-cards.
Usage: seek <new position>
help
Display help on the current device. Typically variables of the device are shown.
Usage: help
set
Set variable of the current device.
Usage: set <variable-index> <new value>
get
Get variable of the current device.
Usage: get <variable-index>
monitor
Set the specified device as interpreter-source. i.e. another COM-port.
Usage: monitor <device-name>
setbaud
Set baudrate of the specified device.
Usage: setbaud <device-name> <baudrate>
Filesytem and Storage-Card functions
There are two different interfaces.
These functions are used with the newer bootloader-device-intferface:
mount
Mounts volume of specified device.
Usage: mount <device-name> <volume-number: 0 is default>
boot
Boots a file from mounted volume.
Usage: boot <device-name> <filename>
dir
Shows contents of current directory of mounted volume.
Usage: dir
cd
Changes directory of mounted volume.
Usage: cd <directory-name>
cat
Show files contents.
Usage: cat <filename>
Special Commands
These commands are not visible in the command-list.
Consider them as not documented.
.noflash
Do everything without changing the flashdisk-contents.
i.e. very usefull if you want to boot a zipped image without storing it to flash.
Usage: .noflash
.storeburn
Used in conjunction with a deployment-board. The deployment board is board capable of flashing multiple Trizeps-modules at the same time. It indicates success/failure of update procedure through the LED's of the board.
Usage: .storeburn <device-name> <filename>