| 05:18.13 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 07:24.07 | *** join/#openjtag matthsu (~matt@61-30-10-70.static.tfn.net.tw) |
| 08:04.14 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 10:41.09 | *** join/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
| 10:41.24 | *** part/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
| 14:13.00 | *** join/#openjtag StrontiumDog (~Strontium@89.12.50.60.kmr02-home.tm.net.my) |
| 14:33.26 | *** join/#openjtag wookey_ (~wookey@stoneboat.aleph1.co.uk) |
| 15:05.41 | *** join/#openjtag roxfan (dunno@91.180.21.165) |
| 15:16.19 | *** join/#openjtag roxfan (dunno@91.180.71.142) |
| 16:03.08 | *** join/#openjtag toi (~toi@d54C2AA76.access.telenet.be) |
| 19:30.04 | penguinece | I'm trying to communicate with an arm cortex m3 processor on a custom pcb. I have one board put together that works flawlessly, both jtag and in every other way. I have a second board that has the error "Error: 115 589 core.c:938 jtag_examine_chain_check(): JTAG scan chain interrogation failed: all ones" and "Error: 116 590 core.c:939 jtag_examine_chain_check(): Check JTAG interface, timings, target power, etc.". Any ideas? could the proc |
| 19:30.04 | penguinece | essor on the second board be broken? |
| 20:08.44 | roxfan | might be almost anything |
| 20:08.59 | roxfan | bad soldering/solder bridge/ESD etc |
| 20:09.50 | roxfan | maybe check if you can get into the serial bootloader |
| 21:33.28 | wookey_ | allones generally means 'nothing happened' e.g. no power, stuck in reset, wries not connected. |
| 21:53.18 | *** join/#openjtag twarren (~twarren@ip70-190-110-83.ph.ph.cox.net) |
| 22:37.10 | *** part/#openjtag twarren (~twarren@ip70-190-110-83.ph.ph.cox.net) |