| 00:15.16 | *** join/#openjtag flyback (n=flyback@c-71-236-75-166.hsd1.pa.comcast.net) |
| 05:35.28 | *** join/#openjtag roxfan (n=dunno@89.165-243-81.adsl-dyn.isp.belgacom.be) |
| 05:53.13 | *** join/#openjtag roxfan2 (n=dunno@25.60-244-81.adsl-dyn.isp.belgacom.be) |
| 06:39.40 | *** join/#openjtag pleemans (n=toi@116.54-246-81.adsl-static.isp.belgacom.be) |
| 07:15.58 | *** join/#openjtag dirk2 (n=dirk@p5B04201B.dip0.t-ipconnect.de) |
| 09:09.27 | *** part/#openjtag dirk2 (n=dirk@p5B04201B.dip0.t-ipconnect.de) |
| 11:31.51 | *** join/#openjtag dirk2 (n=dirk@p5B0410D0.dip0.t-ipconnect.de) |
| 15:17.56 | *** join/#openjtag prpplague (n=dave@mail.americanmicrosystems.com) |
| 15:49.03 | *** join/#openjtag dirk2 (n=dirk@p5B043348.dip0.t-ipconnect.de) |
| 15:58.11 | prpplague | dirk2: hey bud |
| 15:58.14 | prpplague | dirk2: how goes the battle |
| 15:58.59 | dirk2 | prpplague: You can read my progress at http://elinux.org/BeagleBoardOpenOCD :) |
| 15:59.09 | prpplague | looks |
| 15:59.19 | dirk2 | prpplague: I'm still at the learning & reproducing level |
| 16:00.43 | dirk2 | prpplague: I was successfully able to execute the *command* "jtag tapenable omap3530.cpu", but I'm not sure if it was successful |
| 16:01.10 | dirk2 | prpplague: And I still have to learn how to verify that ;) |
| 16:01.14 | prpplague | dirk2: if you are able to re-scan the chain and it shows up, it is enabled |
| 16:01.25 | prpplague | dirk2: right, which is why i was using the dm355 board |
| 16:01.48 | prpplague | dirk2: the davinci already has openocd support, so i'd be able to do the tests on it |
| 16:02.24 | dirk2 | prpplague: There are we again at "learn level": How do I "re-scan" or/and what does this mean? |
| 16:03.51 | prpplague | dirk2: the scan chain has a feature where you can get the ID's of everything on the chain, normally when the ICEPick is the only item enabled, you will only see the ID for the ICEPick on the chain |
| 16:04.23 | prpplague | dirk2: once you successfully enable the arm tap, you should be able to scan again, this time getting two id's, one for the ICEPick and one for the arm |
| 16:04.52 | dirk2 | prpplague: You mean the command "scan_chain"? |
| 16:05.04 | prpplague | dirk2: yea |
| 16:05.19 | prpplague | dirk2: i was just looking at your output on the page |
| 16:05.25 | prpplague | dirk2: looks like that is what you did |
| 16:06.00 | prpplague | dirk2: something doesn't look right |
| 16:06.06 | dirk2 | prpplague: Yes, and i got 0x00000000 which means it doesn't work, right? |
| 16:06.08 | prpplague | dirk2: there is a no ID information for the cpu |
| 16:06.24 | prpplague | dirk2: yea, looks like something isn't working or misconfigured |
| 16:07.06 | dirk2 | prpplague: Can you have a look to the scripts in the middle of the page. there is a jtag configure $_CHIPNAME.cpu -event tap-enable |
| 16:07.19 | prpplague | dirk2: one sec |
| 16:07.46 | dirk2 | prpplague: Is there a chance I can verify that each command is successful? |
| 16:08.11 | dirk2 | prpplague: What I understand is that we wirte some "JTAG registers" by this |
| 16:08.11 | prpplague | dirk2: no way of knowing with out knowing what they do, and that is the black magic TI isn't giving up |
| 16:08.16 | prpplague | dirk2: yea |
| 16:08.39 | prpplague | <PROTECTED> |
| 16:08.39 | prpplague | <PROTECTED> |
| 16:08.40 | dirk2 | prpplague: Am I able to read these "registers" back and look what are in them? |
| 16:08.55 | prpplague | dirk2: as far as i know, no |
| 16:09.35 | dirk2 | prpplague: Hm :( I thought of it as something like I2C: Write registers, read registers |
| 16:10.28 | prpplague | dirk2: right, i should qualify myself with that statement, i am sure there is a way to read back the registers, but since we have no idea what the registers are or the method for reading it back.......... |
| 16:11.16 | dirk2 | prpplague: Then, I think an additional hint is in https://lists.berlios.de/pipermail/openocd-development/2008-December/004166.html |
| 16:11.34 | dirk2 | prpplague: I think we have to do a reset and then wait 10 TCK |
| 16:12.53 | dirk2 | prpplague: Rick mentioned "I think we can address this in the config fairly easily", but I have no idea how to do this. Main question is if there is already a command to wait 10 TCK, or if it has to be implemented (what most probably is 'easy') |
| 16:13.19 | prpplague | dirk2: yea |
| 16:14.28 | dirk2 | prpplague: At the moment I'm thinking about something like |
| 16:14.31 | dirk2 | jtag_reset |
| 16:14.36 | dirk2 | wait 10 TCK |
| 16:14.49 | dirk2 | irscan omap3530.jrc 7 |
| 16:14.51 | dirk2 | ... |
| 16:14.55 | dirk2 | to add to the script |
| 16:17.11 | prpplague | sounds doable |
| 16:17.33 | dirk2 | yes, but the details ;) |
| 16:19.01 | dirk2 | prpplague: Conclusion is that I have success if I get something else than 0x00000000 IdCode, right? |
| 16:19.20 | prpplague | dirk2: correct |
| 16:20.09 | dirk2 | prpplague: Do you know if Rick or Duane are sometimes here? |
| 16:20.37 | prpplague | i've seen duane on the #beagle a few times |
| 16:21.04 | dirk2 | As "duane" ? |
| 16:22.35 | prpplague | yea iirc |
| 16:24.32 | dirk2 | ok, will send a mail to mailing list if Rick would have some more details regarding "waiting 10 TCK". |
| 16:28.49 | prpplague | good deal, sorry i can't spend more time on it right now, we have a product release scheduled for jan9, so not much time to finish up some of the details |
| 16:31.10 | dirk2 | np. You help already a lot with a short chat :) |
| 16:31.42 | dirk2 | And I learn a lot :) |
| 16:32.44 | prpplague | dirk2: good deal then! |
| 17:02.55 | *** part/#openjtag dirk2 (n=dirk@p5B043348.dip0.t-ipconnect.de) |
| 18:32.07 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 20:40.21 | *** join/#openjtag prpplague^2 (n=dave@mail.americanmicrosystems.com) |
| 22:20.04 | flyback | m00 |
| 22:21.39 | L_Deluxe | o1nk |
| 23:16.47 | flyback | is feeling a little better about his life in some ways but still feels his body and mind are deteriating |