| 06:22.08 | *** join/#openjtag pleemans (n=toi@cust-240-101-110-94.dyn.versateladsl.be) |
| 07:05.44 | *** join/#openjtag jwalck (n=starkmjo@c-4cc0e455.012-337-6c6b701.cust.bredbandsbolaget.se) |
| 07:16.28 | *** join/#openjtag pleemans (n=toi@d51A49C45.access.telenet.be) |
| 10:03.23 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 15:23.08 | *** join/#openjtag dirk2 (n=dirk@p5B040AD5.dip0.t-ipconnect.de) |
| 16:04.25 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 18:18.39 | *** join/#openjtag pleemans (n=toi@d54C2AAB7.access.telenet.be) |
| 19:28.32 | Circuitsoft | Hello. I'm trying to figure out how to connect OpenOCD to a chip, but the datasheet has too much detail. |
| 19:40.39 | roxfan | you need to find at least tck, tdi, tdo and tms |
| 19:41.06 | roxfan | trst and srst can be necessary, depending on the core |
| 19:51.36 | Circuitsoft | It's connected, but I'm having issues with configuration. |
| 19:51.39 | Circuitsoft | It's an ARM7tdmi |
| 19:52.04 | Circuitsoft | I know that it has three scan chains. 0 is full boundary of core, 1 is bus subset, 2 is ICE. |
| 19:52.09 | Circuitsoft | Is that any standard tdmi? |
| 19:52.45 | roxfan | no idea |
| 19:53.13 | roxfan | but i think you should be to at least get the idcode |
| 19:53.48 | Circuitsoft | All I know so far is that the full IR len is 12. |
| 19:54.08 | Circuitsoft | urjtag started doing an exhaustive search finding the DRs of all possible instructions. |
| 19:54.19 | Circuitsoft | Didn't find anything useful. |
| 19:54.27 | roxfan | did it show you the id? |
| 19:54.32 | Circuitsoft | no. |
| 19:54.37 | roxfan | weird |
| 19:55.05 | roxfan | um, why pm? |
| 19:55.10 | Circuitsoft | The part is an sta8058. |
| 19:55.16 | Circuitsoft | Afraid of flood-ban |
| 19:55.28 | roxfan | for three lines? |
| 19:55.33 | roxfan | use a pastebin then... |
| 19:55.35 | Circuitsoft | I think it's happened before. |
| 19:55.36 | Circuitsoft | ok. |
| 19:56.24 | roxfan | either way, 7e1e1e1f looks fishy... |
| 19:56.43 | Circuitsoft | http://pastebin.ca/1532910 |
| 19:57.01 | Circuitsoft | I don't actually know anything about what the idcodes should be. |
| 19:57.50 | roxfan | well, you can try replacing fc3c3c3f by 7e1e1e1f |
| 19:58.23 | Circuitsoft | I'm not even sure if the flash exists on the scan chain. |
| 19:58.32 | Circuitsoft | It's a multi-chip-module. |
| 19:58.35 | roxfan | unlikely |
| 19:58.53 | roxfan | wait |
| 19:59.00 | roxfan | you mean boundary scan? |
| 19:59.18 | Circuitsoft | I thought I had to declare it in the chain even if I'm not using it directly. |
| 19:59.22 | Circuitsoft | Error: number of discovered devices in JTAG chain (2) does not match (enabled) configuration (1), total taps: 1 |
| 19:59.42 | roxfan | hmm so it found only one device |
| 19:59.58 | Circuitsoft | Uh, vice-versa, I got rid of the flash newtap line. |
| 20:00.10 | roxfan | ah |
| 20:00.36 | roxfan | well it's unlikely than the flash will be in jtag tap chain |
| 20:01.01 | Circuitsoft | ok |
| 20:01.05 | roxfan | usually you either access it via boundary scan or using cpu's debug mode |
| 20:02.53 | Circuitsoft | Datasheet quote: "In this case, the user can store its own "loader" in the internal RAM through JTAG, in a way suitable for production programming equipment. The detailed procedure will be released and described in a separate document." |
| 20:03.16 | roxfan | yeah that's what openocd does |
| 20:03.31 | Circuitsoft | And that's what I'm trying to configure it to do. |
| 20:03.41 | roxfan | it uploads a small code that runs in the core and sends results via jtag |
| 20:04.05 | roxfan | anyway, first you need to make openocd recognize the devices |
| 20:04.42 | Circuitsoft | Info : JTAG tap: sta8058.cpu tap/device found: 0x7e1e1e1f (mfg: 0x70f, part: 0xe1e1, ver: 0x7) |
| 20:04.43 | Circuitsoft | Info : JTAG Tap/device matched |
| 20:04.45 | Circuitsoft | Warn : Tap/Device does not have IDCODE |
| 20:04.51 | roxfan | o.O |
| 20:04.58 | roxfan | never seen this one... |
| 20:05.19 | Circuitsoft | So, perhaps that's not actually an ARM core, and I should be targeting the next device in the chain? |
| 20:06.15 | roxfan | no idea really... |
| 20:06.20 | Circuitsoft | Well, the next item in the chain has a tapid of 0x00000000 |
| 20:07.25 | Circuitsoft | I can't imagine that's an arm7tdmi |
| 20:54.22 | Circuitsoft | Well, I've figured something out. |
| 20:54.28 | Circuitsoft | I have my reset_config wrong. |
| 20:54.33 | Circuitsoft | Now, I just need to figure out what it should be. |
| 20:55.25 | *** join/#openjtag roxfan2 (n=dunno@91.182.211.12) |
| 21:31.22 | Circuitsoft | roxfan: Is it possible to autodetect the reset_config? |
| 21:31.52 | roxfan | umm don't think so |
| 21:32.06 | Circuitsoft | Where can I find a list of all possible flags to try? |
| 21:32.16 | roxfan | in the doc? |
| 21:32.26 | Circuitsoft | Doesn't appear to be there. |
| 21:32.50 | Circuitsoft | http://openocd.berlios.de/doc/html/Reset-Configuration.html makes no mention of a complete list of values. |
| 21:34.38 | roxfan | Possible values are none (the default), trst_only, srst_only and trst_and_srst. |
| 21:34.41 | roxfan | etc |
| 21:36.10 | Circuitsoft | srst_only and trst_only both fail to reset the device. |
| 21:36.18 | Circuitsoft | OpenOCD can only connect immediately after a power cycle. |
| 21:36.35 | Circuitsoft | Given that, is there any chance of it working without needing a power cycle? |
| 21:36.39 | roxfan | are you sure those signals are connected? |
| 21:37.05 | Circuitsoft | Reasonably. I'll have to check the schematic, but I think so. |
| 21:37.45 | Circuitsoft | If neither of them works, though, will I always have to power-cycle the device before it'll connect? |
| 21:41.00 | roxfan | well, i think usually openocd should be able to break the running target |
| 22:03.38 | *** part/#openjtag MarkusBec (n=markusbe@ist.deswahnsinns.de) |