This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
digispark:tutorials:debugging [2013/05/05 08:19] RC Navy [Bi-directional Serial Debugging with a single I/O] |
digispark:tutorials:debugging [2013/05/05 08:30] RC Navy [Bi-directional Serial Debugging with a single I/O] |
||
|---|---|---|---|
| Line 51: | Line 51: | ||
| If you didn't plan to use DigiUSB in your final sketch, the following proposed alternative consumes less pin and program memory than USB.\\ Since the last version of <SoftSerial> library (may 2013), <SoftSerial> is an alternative for debugging Digispark just using a single I/O.\\ By declaring a <SoftSerial> object with the __same__ pin for Tx and Rx: it's possible to use a half duplex (request/response) software serial port using a __single__ I/O. | If you didn't plan to use DigiUSB in your final sketch, the following proposed alternative consumes less pin and program memory than USB.\\ Since the last version of <SoftSerial> library (may 2013), <SoftSerial> is an alternative for debugging Digispark just using a single I/O.\\ By declaring a <SoftSerial> object with the __same__ pin for Tx and Rx: it's possible to use a half duplex (request/response) software serial port using a __single__ I/O. | ||
| - | The external interface is composed of 2 resistors and a regular diode (See below).\\ Please, note this solution requires a native RS232 port (rare today) or a RS232/USB adapter on the development PC. | + | The external interface is composed of 2 resistors and a regular diode (See below).\\ This approach allows to use the built-in Serial Monitor of the arduino IDE.\\ Please, note this solution requires a native RS232 port (rare today) or a RS232/USB adapter on the development PC. |
| ==== How to use this debugging capabilities? ==== | ==== How to use this debugging capabilities? ==== | ||