ice:enclosure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
ice:enclosure [2015/05/05 17:32] jtshugrue Corrected mistakes in EVENT system pin definitions. |
ice:enclosure [2016/03/15 16:23] (current) jtshugrue Clarified labeling of TTL serial signals |
||
|---|---|---|---|
| Line 84: | Line 84: | ||
| ^ **Pin** | ^ **Pin** | ||
| | 1 | EVENT_ADDR0 | | 1 | EVENT_ADDR0 | ||
| - | | 2 | | + | | 2 | |
| - | | 3 | | + | | 3 | |
| | 4 | 5V In((leave unconnected if USB is also connected)) | | 4 | 5V In((leave unconnected if USB is also connected)) | ||
| | 5 | Ground | | 5 | Ground | ||
| Line 96: | Line 96: | ||
| == TTL Serial == | == TTL Serial == | ||
| - | This provides a TTL (low-voltage) asynchronous serial interface (USART) to communicate with the ICE Platform. Note that this serial interface is **not** compatible with RS-232 signalling levels, as found on the COM ports of older PC's. The serial interface operates at 3.3V signalling levels, | + | This provides a LVTTL (low-voltage, 3.3V signalling) asynchronous serial interface (USART) to communicate with the ICE Platform. Note that this serial interface is **not** compatible with RS-232 signalling levels, as found on the COM ports of older PC's. The serial interface operates at 3.3V signalling levels, |
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| - | Either the TTL serial interface or USB can be used to receive commands, but **not** simultaneously (e.g. interleaved bytes). | + | Either the TTL serial interface or USB can be used to receive commands, but **not** simultaneously (e.g. interleaved bytes). Taking turns sending complete commands and responses is okay. |
| </ | </ | ||
ice/enclosure.txt · Last modified: 2016/03/15 16:23 by jtshugrue
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
