10:19.37 | *** join/#openjtag rd_ (n=rd@vnsecurity.net) |
11:19.48 | *** join/#openjtag rd__ (n=rd@vnsecurity.net) |
13:47.57 | *** join/#openjtag prpplague (n=billybob@mail.americanmicrosystems.com) |
14:02.06 | *** join/#openjtag drath_ (i=vmaster@p5B07CC31.dip.t-dialin.net) |
14:52.19 | *** join/#openjtag prpplague^2 (n=billybob@mail.americanmicrosystems.com) |
16:50.28 | sn9 | what is currently the most recommended jtag software? is it this? http://star.oai.pp.ru/jtag/jtag-brecis-ok.zip |
16:55.30 | prpplague | openocd |
16:55.40 | prpplague | atleast in OSS community |
16:56.20 | sn9 | url? |
16:56.42 | drath | sn9: what is it that you want to do with JTAG? |
16:57.32 | sn9 | external access to SoC & memory |
16:57.49 | drath | just for programming, or also for debugging? |
16:58.21 | drath | and most importantly - which SoC? |
16:58.53 | sn9 | programming first, and debugging if things go wrong |
16:59.03 | sn9 | arm, mips, and x86 |
16:59.33 | drath | well, the OpenOCD only supports ARM at this point |
16:59.42 | sn9 | ah |
16:59.43 | drath | the zip you mentioned seems to be a release of the openwince jtag tools |
16:59.53 | sn9 | it's a fork, yes |
17:00.32 | drath | they're suitable for programming |
17:00.45 | drath | but not for debugging |
17:00.50 | drath | speed is quite low |
17:06.36 | *** join/#openjtag p2-mate (n=p2@cable-87-244-173-194.upc.chello.be) |
18:19.54 | keesj | happy happy joy joy openfacts is backonline , I can look at the docs again |
22:35.46 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |