Timeline for scoping a UART interface
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 5, 2015 at 4:49 | vote | accept | kolosy | ||
| Mar 5, 2015 at 4:02 | comment | added | kolosy | @geometrikal soldering seems fine | |
| Mar 5, 2015 at 1:09 | comment | added | Samuel | Ah, it's not marked correctly, should be RESETN (or !RESET). Maybe it's not the right baud. Try watching the TX and RX lines as the device turns on, you may get a glimpse of its default baud rate. | |
| Mar 5, 2015 at 1:02 | answer | added | Oleg Mazurov | timeline score: 3 | |
| Mar 5, 2015 at 1:01 | comment | added | geometrikal | It might sound simple, but double check your soldering. :D | |
| Mar 5, 2015 at 0:31 | comment | added | tcrosley | Nice scope capture, often they're pretty unreadable. | |
| Mar 5, 2015 at 0:29 | comment | added | Samuel | Is the part marked incorrectly or have you pulled the active-high reset high? | |
| Mar 5, 2015 at 0:20 | comment | added | Ignacio Vazquez-Abrams | No, the response signal would be superimposed on the crosstalk noise. | |
| Mar 5, 2015 at 0:16 | comment | added | kolosy | it's possible - the UART is just for debug purposes, and I've got a 4" long ribbon cable taking it off-board. If that were the case, would the cross-talk prevent the module from responding? | |
| Mar 5, 2015 at 0:15 | comment | added | Ignacio Vazquez-Abrams | That's an incredible amount of crosstalk... | |
| Mar 5, 2015 at 0:13 | history | asked | kolosy | CC BY-SA 3.0 |