DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...
DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ... DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...
2.3.1 Microprocessor Port-Pin Attachments As the only prerequisite, this configuration requires a microprocessor with a spare bidirectional port pin and some spare space in the program memory. Figure 2.3 shows the most basic implementation of this 1 – Wire® Master. The upside of this implementation is its low, additional hardware cost, since it requires just a pullup resistor. On the downside, the 1 – Wire® timing, to communicate with slave devices, is generated through software, which can increase the initial software development time and cost. Depending on the number of 1 – Wire® slaves on the bus and the 1 – Wire® pullup voltage, an additional port pin may be required to implement a strong pullup. With more than one slave device on the 1 – Wire® bus, the value of RPUP needs to be lowered. If communicating with 1 – Wire® slaves at overdrive speed, a microcontroller with a high clock frequency and/or a low number of clock cycles per instruction is required. A variation of the implementation shown in Figure 2.3 is shown in Figure 2.4. As a prerequisite, this new implementation requires two spare unidirectional port pins, a pulldown transistor, and some spare space in the program memory. The upside of this design is that it does not need a bidirectional port pin, but on the downside, the 1 – Wire® timing is generated through software, which can increase the initial software development time and cost. Depending on the number of 1 – Wire® slaves on the bus and the 1 – Wire® pullup voltage, an additional port pin may be required to implement a strong pullup. With more than one slave device on the 1 – Wire® bus, the value of RPUP needs to be lowered. If communicating with 1 – Wire® slaves at overdrive speed, a microcontroller with a high clock frequency and/or a low number of clock cycles per instruction is required. 11
Figure 2.3 Bidirectional port pin with optional circuit for strong pullup (dashed lines) [8]. Figure 2.4 Unidirectional port pins with optional circuit for strong pullup (dashed lines) [8]. 12
- Page 1 and 2: DESIGN OF A CUSTOM ASIC INCORPORATI
- Page 3 and 4: ABSTRACT The vast majority of today
- Page 5 and 6: LIST OF ABBREVIATIONS AND SYMBOLS A
- Page 7 and 8: ISO International Organization for
- Page 9 and 10: SI Serial In SO Serial Out SOF Star
- Page 11 and 12: ACKNOWLEDGEMENTS I would like to ex
- Page 13 and 14: 2.4 Types of Devices...............
- Page 15 and 16: 4.3.5 Communication Speed Different
- Page 17 and 18: 5.3.21.1 Synchronization Test (test
- Page 19 and 20: 5.3 Resource Utilization...........
- Page 21 and 22: LIST OF FIGURES 2.1 1 - Wire® Netw
- Page 23 and 24: 4.12 Read-Data Time Slot...........
- Page 25 and 26: 6.4 DS1996 Address Registers ......
- Page 27 and 28: manufacturing process. Structured o
- Page 29 and 30: describes the 1 - Wire® and CAN co
- Page 31 and 32: 2.2 1 - Wire® Overview The basis o
- Page 33 and 34: All 1 - Wire® masters described in
- Page 35: attachments, microcontroller with b
- Page 39 and 40: 2.3.3 Synthesizable 1 - Wire® Bus
- Page 41 and 42: Figure 2.7 UART/RS232 Serial Port I
- Page 43 and 44: hardware. Through control registers
- Page 45 and 46: Table 2.2 1 - Wire® Bus Operations
- Page 47 and 48: 2.3.6 1 - Wire® Search Algorithm F
- Page 49 and 50: detected. This ‘read two bits’
- Page 51 and 52: in Figure 2.15. Alternatively, the
- Page 53 and 54: of the bit, then write the desired
- Page 55 and 56: 2.4.2 Device Functions and Typical
- Page 57 and 58: and development (R&D) investments b
- Page 59 and 60: 2.5 Network Types and Precedents As
- Page 61 and 62: 2.5.2 1 - Wire® Network Topologies
- Page 63 and 64: 2.5.3 1 - Wire® Network Limitation
- Page 65 and 66: with a single selected slave. If an
- Page 67 and 68: user group was founded in March of
- Page 69 and 70: protocol on multiple media for maxi
- Page 71 and 72: ecessive bit and the monitored stat
- Page 73 and 74: specification: Start-Of-Frame, Arbi
- Page 75 and 76: Cyclic Redundancy Check (CRC) Field
- Page 77 and 78: Arbitration FieldThe Arbitration Fi
- Page 79 and 80: SOF SOF Bit 28 Bit 27 Arbitration f
- Page 81 and 82: Afterwards it starts transmitting s
- Page 83 and 84: Figure 3.9 Structure of the Interfr
- Page 85 and 86: error occurs, an Error Frame is gen
2.3.1 Microprocessor Port-Pin Attachments<br />
As the only prerequisite, this configuration requires a microprocessor with a spare<br />
bidirectional port pin and some spare space in the program memory. Figure 2.3 shows the most<br />
basic implementation of this 1 – Wire® Master. The upside of this implementation is its low,<br />
additional hardware cost, since it requires just a pullup resistor. On the downside, the 1 – Wire®<br />
timing, to communicate with slave devices, is generated through software, which can increase<br />
the initial software development time and cost. Depending on the number of 1 – Wire® slaves<br />
on the bus and the 1 – Wire® pullup voltage, an additional port pin may be required to<br />
implement a strong pullup. With more than one slave device on the 1 – Wire® bus, the value of<br />
RPUP needs to be lowered. If communicating with 1 – Wire® slaves at overdrive speed, a<br />
microcontroller with a high clock frequency and/or a low number of clock cycles per instruction<br />
is required.<br />
A variation of the implementation shown in Figure 2.3 is shown in Figure 2.4. As a<br />
prerequisite, this new implementation requires two spare unidirectional port pins, a pulldown<br />
transistor, and some spare space in the program memory. The upside of this design is that it does<br />
not need a bidirectional port pin, but on the downside, the 1 – Wire® timing is generated through<br />
software, which can increase the initial software development time and cost. Depending on the<br />
number of 1 – Wire® slaves on the bus and the 1 – Wire® pullup voltage, an additional port pin<br />
may be required to implement a strong pullup. With more than one slave device on the 1 –<br />
Wire® bus, the value of RPUP needs to be lowered. If communicating with 1 – Wire® slaves at<br />
overdrive speed, a microcontroller with a high clock frequency and/or a low number of clock<br />
cycles per instruction is required.<br />
11