snap ethernet-based i/o units protocols and programming guide
snap ethernet-based i/o units protocols and programming guide
snap ethernet-based i/o units protocols and programming guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Bytes 0–3<br />
Bytes 4–7<br />
Bytes 8–11<br />
Bytes 12–15<br />
Bytes 16–19<br />
Last four bytes<br />
Error Codes<br />
CHAPTER 4: USING THE IEEE 1394-BASED PROTOCOL<br />
Read Block Response<br />
Tcode = 7<br />
destination_ID tl rt tcode pri<br />
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0<br />
source_ID rcode reserved<br />
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />
reserved<br />
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />
data_length extended_tcode<br />
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />
data_block<br />
last quadlet of data block (padded if necessary)<br />
Response packets contain an rcode parameter, which shows whether the response is an ACK or<br />
a NAK. An rcode of 0 is an ACK; anything else is a NAK. If a NAK appears in the rcode parameter,<br />
check the Status area of the memory map (see page 105) to find out the reason for the NAK.<br />
The following table lists the error codes that may appear in the Status area of the memory map:<br />
Code<br />
(Hex)<br />
Meaning Code<br />
(Hex)<br />
0000 No error E008 Busy<br />
98 SNAP Ethernet-Based I/O Units Protocols <strong>and</strong> Programming Guide<br />
Meaning<br />
E001 Undefined comm<strong>and</strong> E009 Cannot erase flash<br />
E002 Invalid point type E00A Cannot program flash<br />
E003 Invalid float E00B Downloaded image too small<br />
E004 Powerup Clear expected E00C Image CRC mismatch<br />
E005 Invalid memory address or invalid<br />
data for the memory address<br />
E00D Image length mismatch<br />
E006 Invalid comm<strong>and</strong> length E00E Feature is not yet implemented<br />
E007 Reserved E00F Communications watchdog timout