| 06:31.06 | *** join/#openjtag pleemans (n=peter@dD577D009.access.telenet.be) |
| 12:47.26 | *** join/#openjtag bjdooks (n=ben@trinity.fluff.org) [NETSPLIT VICTIM] |
| 13:16.28 | *** join/#openjtag prpplague^2 (n=dave@mail.americanmicrosystems.com) |
| 16:16.09 | *** join/#openjtag toi (n=pleemans@d5153128F.access.telenet.be) |
| 16:46.37 | *** join/#openjtag drath (n=vmaster@p5B07DC89.dip.t-dialin.net) |
| 17:26.02 | prpplague | drath: greetings |
| 17:26.24 | prpplague | drath: when you have about 20-30 minutes, i'd like to talk about JRC support in openocd with you |
| 17:48.26 | drath | hey prpplague |
| 17:48.39 | drath | i suppose now is at least as good as any other time |
| 17:49.19 | *** join/#openjtag pleemans (n=peter@d54C2AAB7.access.telenet.be) |
| 17:55.23 | prpplague | drath: ok here is the issue with using jrc's like the TI icepick |
| 17:55.43 | prpplague | drath: when the chain is initialized it will only have one device, the icepick |
| 17:56.11 | prpplague | drath: it needs to come up then issue a series of ir/dr scans that add the arm core to the chain |
| 17:56.46 | prpplague | drath: once the arm core has been added it needs to begin again with the chain but this time with two devices in the chain |
| 17:57.01 | prpplague | drath: i've been digging into the jtag.c/.h stuff |
| 17:57.08 | prpplague | drath: looks like that is the best location |
| 17:57.22 | prpplague | drath: what i had planned on doing was to add a icepick target |
| 17:57.41 | prpplague | drath: and if it is specific it will use the startup sequence i just described |
| 17:57.50 | prpplague | drath: thoughts? |
| 18:45.00 | drath | prpplague: did you check the mailinglist? |
| 18:45.14 | drath | prpplague: there were some postings a few weeks ago on that topic |
| 18:45.31 | drath | prpplague: btw., what does JRC stand for? |
| 19:06.26 | prpplague | drath: yea, keesj was the one doing that posting |
| 19:06.33 | prpplague | drath: Jtag Route Controller |
| 19:07.12 | prpplague | drath: http://focus.ti.com/lit/ml/sprp603/sprp603.pdf |
| 19:07.25 | prpplague | drath: that is a good explaination of the purpose of a JRC |
| 19:07.49 | prpplague | drath: almost all of the multicore SoC's are moving towards using a JRC |
| 19:09.31 | prpplague | drath: keesj and i have been looking into the changes needed to be done to openocd |
| 19:18.54 | drath | prpplague: will the JRC remain in enabled state? or could for example a reset cause the ARM device to disappear from the chain? |
| 19:34.06 | prpplague | drath: a hard reset will cause the arm to disappear from the chain |
| 19:48.57 | *** join/#openjtag Chocobo (n=swinchen@strongbad.eece.maine.edu) |
| 20:08.17 | *** join/#openjtag toi (n=pleemans@d5153128F.access.telenet.be) |
| 20:15.45 | *** join/#openjtag toi (n=pleemans@d5153128F.access.telenet.be) |
| 20:22.16 | *** join/#openjtag nslu2-log (n=nslu2-lo@limax.nslu2-linux.org) |