Notes on Uploading to a DOM Mainboard

Prerequistes for JTAG uploading:


You might want to check that you have a readable JTAG chain with the jtagconfig command:


C:\> jtagconfig

You'll need a split release.hex.0 and release.hex.1. Erase the existing flash contents:


C:\> exc_flash_programmer -a
C:\> exc_flash_programmer -a -e 1


Now program the flash with the release.hex.0 and release.hex.1 files:


C:\> exc_flash_programmer -p -g release.hex.0
C:\> exc_flash_programmer -p -g -e 1 release.hex.1


If you're bootstrapping your way up to a full installation, and are going to send a release.hex later, you can also just upload an iceboot.hex over the JTAG cable. Now just power-cycle the DOM, and you're done.

Prerequisites for normal (terminal server or DOR card) uploading:

To upload a single file with a DOR card connection, I suggest Kael's "xymodem" binary:

% xymodem /dev/dhc0w0dA ~/demo/dom-ws/epxa10/bin/iceboot.bin.gz iceboot


If you are using a terminal server, first telnet into the DOM and start the
ymodem receiver in iceboot:


% telnet <terminal_server> <2000+port>
> ymodem1k
[escape out of telnet]
% sz -k --ymodem --tcp-client=<terminal_server:3000+port> iceboot.bin.gz
% telnet <terminal_server> <2000+port>
> gunzip
> s" iceboot" create

To upload an entire release.hex, telnet to the DOM and execute the install command (if your iceboot doesn't have this command, you'll have to upgrade iceboot first):

% telnet localhost 5000
> install
[escape from telnet]
% sendfile release.hex localhost 5000

If everything went well, you should be able to reboot, and the new software will be there. If something went wrong, your flash is probably corrupted, and you'll need to install a release with the JTAG cable, since you can no longer communicate normally with the DOM.