| 00:22.26 | *** join/#openjtag roxfan (dunno@91.180.79.164) |
| 00:35.37 | *** join/#openjtag _julian_ (~quassel@hmbg-4d06853a.pool.mediaWays.net) |
| 00:52.23 | *** join/#openjtag Nattgris (~andreas@c-c0f170d5.026-401-67626721.cust.bredbandsbolaget.se) |
| 01:43.04 | *** join/#openjtag jaeckel (~jaeckel@jaeckel.eu) |
| 05:47.47 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 08:56.01 | *** join/#openjtag Volkan-K (volkan-k@unaffiliated/volkan-k) |
| 08:56.17 | Volkan-K | hi guys |
| 08:56.20 | Volkan-K | and gals |
| 08:57.46 | karlp | g'monring |
| 08:58.44 | Volkan-K | so which jtag tool do u use |
| 09:11.36 | karlp | stm32 discovery boards, with swd |
| 09:42.52 | Weaselweb | is there a benefit in swd compared to jtag? |
| 09:43.51 | Volkan-K | Weaselweb: u using urJTAG? |
| 09:49.58 | karlp | Weaselweb: less pins, for starters |
| 09:50.23 | karlp | but it's not chainable like jtag |
| 09:51.13 | Volkan-K | how many pins |
| 09:52.37 | Volkan-K | AFAIK jtag has 4+1optional pins |
| 09:52.53 | Volkan-K | <PROTECTED> |
| 09:52.53 | Volkan-K | <PROTECTED> |
| 09:52.53 | Volkan-K | <PROTECTED> |
| 09:52.53 | Volkan-K | <PROTECTED> |
| 09:52.53 | Volkan-K | <PROTECTED> |
| 09:52.53 | Volkan-K | wiki says so |
| 09:54.16 | Volkan-K | wow swd is 2-pins |
| 09:55.23 | Volkan-K | amazingo |
| 10:04.51 | Volkan-K | whats the speed |
| 10:04.59 | Volkan-K | 4 Mbytes/sec @ 50 MHz |
| 10:05.02 | Volkan-K | wow |
| 10:05.09 | Volkan-K | fast fast |
| 10:05.41 | karlp | in practice both jtag and swd are more pins, but yes, it _can be fast |
| 10:05.47 | Volkan-K | May I ask |
| 10:05.56 | karlp | you may ask anything, this in the interet |
| 10:06.01 | Volkan-K | how do you detect errors in JTAG? |
| 10:06.10 | Volkan-K | write, then reread to check? |
| 10:06.21 | karlp | what sort of errors do you mean? |
| 10:06.26 | karlp | are you on fire? |
| 10:06.35 | karlp | is the led on? |
| 10:06.35 | Volkan-K | data write errors |
| 10:07.16 | Volkan-K | don't you check accuracy of the data on the flash after write? |
| 10:07.23 | karlp | if you want to, yes. |
| 10:07.23 | Volkan-K | or while writing? |
| 10:07.29 | karlp | but that's optional of course, |
| 10:07.56 | Volkan-K | how do you do it? |
| 10:08.08 | Volkan-K | write one byte, check it, then continue to another? |
| 10:08.21 | karlp | whatever the flash writing tool felt was best |
| 10:08.26 | Volkan-K | or write all data, then check whole? |
| 10:08.51 | karlp | both will work, in most cases I would assume the second method to be much faster |
| 10:09.03 | Volkan-K | hmm |
| 10:09.37 | Volkan-K | do you use jtag? |
| 10:10.03 | Volkan-K | whats the speed? |
| 10:10.11 | karlp | no, like I said earlier |
| 10:10.20 | Volkan-K | ah only swd |
| 10:10.31 | karlp | speed of anything has nothing to do with swd or4 jtag, but the tools and software in use. |
| 10:10.36 | karlp | _and_ the target |
| 10:11.14 | Volkan-K | it takes 20hrs! to flash 4mb in my system :( |
| 10:11.25 | karlp | then you're doing it wrong :) |
| 10:11.31 | Volkan-K | and eats %100 cpu! |
| 10:12.11 | Volkan-K | its unbuffered poor man cable |
| 10:12.17 | karlp | see? wrong. |
| 10:12.34 | Volkan-K | so you use hardware jtag? |
| 10:13.15 | Volkan-K | bitbanging done on jtag chip? |
| 10:13.37 | karlp | I've said I don't use jtag a few times now.... |
| 10:22.09 | Volkan-K | why not |
| 10:22.13 | Volkan-K | :D |
| 10:22.21 | Volkan-K | you should use |
| 10:41.28 | *** join/#openjtag flyback- (~flyback@c-98-219-134-156.hsd1.pa.comcast.net) |
| 11:11.19 | Volkan-K | i mean never used in your life |
| 11:11.21 | Volkan-K | ? |
| 12:42.14 | *** part/#openjtag Volkan-K (volkan-k@unaffiliated/volkan-k) |
| 18:28.52 | *** join/#openjtag pytey (~pytey@howler.blatero.com) |
| 18:34.16 | *** join/#openjtag aSmig (silly@ta.failte.romhat.net) |
| 18:39.55 | *** join/#openjtag joelholdsworth (~joel@179.158.187.81.in-addr.arpa) |
| 23:07.13 | flyback- | 100% cpu and 512KB/hr is normal for a parallell port wiggler jtag |