| 01:27.09 | *** join/#openjtag matt_ (n=matt@61-30-10-70.static.tfn.net.tw) |
| 07:43.55 | *** join/#openjtag dirk2 (n=dirk@p5B0407C9.dip0.t-ipconnect.de) |
| 08:00.09 | *** join/#openjtag roxfan (i=dunno@143.131-246-81.adsl-dyn.isp.belgacom.be) |
| 10:11.56 | *** join/#openjtag _julian (n=quassel@dslc-082-083-142-096.pools.arcor-ip.net) |
| 10:54.10 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 10:54.34 | *** part/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 11:02.16 | *** join/#openjtag dirk2 (n=dirk@p5B0404F2.dip0.t-ipconnect.de) |
| 11:46.23 | *** join/#openjtag Kebianizao|work (n=kvirc@106.pool85-53-168.dynamic.orange.es) |
| 11:46.43 | Kebianizao|work | Hello |
| 11:47.24 | Kebianizao|work | what are the constrains to read a physical address using jtag when linux is running? (on ARM926 arch) |
| 11:51.40 | Kebianizao|work | or IOW, I'm attached to target using openocd, I can halt it, but if I try a regular mdw (memory dump word) I get a data abort |
| 16:00.37 | *** join/#openjtag brolin (n=brolin@iner.udea.edu.co) |
| 17:01.02 | *** join/#openjtag _julian (n=quassel@dslc-082-083-142-096.pools.arcor-ip.net) |
| 17:13.26 | *** join/#openjtag toi (n=toi@d54C2A96D.access.telenet.be) |
| 17:17.43 | *** join/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 17:18.10 | *** part/#openjtag pirho (i=pirho@gateway/gpg-tor/key-0x2CEEC9CB) |
| 18:21.11 | *** join/#openjtag liamMT (n=liamMT@adsl-69-236-107-118.dsl.pltn13.pacbell.net) |
| 19:06.33 | *** join/#openjtag roxfan2 (i=dunno@38.223-240-81.adsl-dyn.isp.belgacom.be) |
| 21:26.57 | *** join/#openjtag brolin (n=brolin@201.232.107.129) |
| 22:32.14 | tzanger | hmm |
| 22:32.23 | tzanger | lpc2103 here with an olimex usb jtag |
| 22:32.26 | tzanger | I can see the device |
| 22:33.22 | roxfan | good for you! |
| 22:33.48 | tzanger | but it's reporting back that there's a configuration failure |
| 22:33.50 | tzanger | Error: invalid mode value encountered 0 |
| 22:33.50 | tzanger | Error: cpsr contains invalid mode value - communication failure |
| 22:33.57 | tzanger | I've played with the jtag speed |
| 22:34.06 | tzanger | I don't think it's a connection issue |
| 22:34.25 | roxfan | does it dump the register values it gets? |
| 22:34.37 | tzanger | it does, but I can't do anything |
| 22:34.38 | roxfan | maybe try increasing verbosity |
| 22:34.51 | roxfan | what are the values? do the look right? |
| 22:35.11 | tzanger | it looks like it might be |
| 22:35.19 | tzanger | I mean RAM's at 0x40000000 and a bunch of regs are up there |
| 22:35.23 | tzanger | PC's down in flash (0x338) |
| 22:35.32 | tzanger | trying to flash doesn't work, I get comm failures |
| 22:35.47 | tzanger | now I have read that this device is particularly bad for mangling flash and resetting losing jtag |
| 22:35.50 | tzanger | but I can't seem to get that far |
| 22:36.18 | tzanger | > flash erase_sector 0 0 7 |
| 22:36.18 | tzanger | timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 1 |
| 22:36.25 | tzanger | and then it also says it can't access the RAM at 0x40000000 |
| 22:38.27 | tzanger | yeah if I try to read memory myself I get a data abort |
| 22:38.28 | tzanger | > mdw 0x40000000 1 |
| 22:38.28 | tzanger | memory read caused data abort (address: 0x40000000, size: 0x4, count: 0x1) |
| 22:39.18 | roxfan | weird |
| 22:39.44 | tzanger | I agree. |
| 22:40.06 | tzanger | in JTAG, does the core's clock matter? |
| 22:40.13 | tzanger | i.e. I am running off a 13MHz crystal |
| 22:40.26 | tzanger | if that wasn't working (it should be, I'm just guessing here) would I get oddball errors? |
| 22:41.51 | roxfan | hmm it might... i remember seeing something about luminary(?) chips losing connection after being switched to fast clock... |
| 22:42.07 | roxfan | but 13mhz shouldn't be a problem methinks |
| 22:57.35 | *** join/#openjtag matt_ (n=matt@61-30-10-70.static.tfn.net.tw) |
| 23:00.00 | tzanger | hmm |
| 23:02.38 | *** join/#openjtag matt____ (n=matt@61-30-10-70.static.tfn.net.tw) |