| 00:34.45 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) [NETSPLIT VICTIM] |
| 00:45.59 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) |
| 01:13.25 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) |
| 01:13.49 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
| 01:13.50 | *** join/#openjtag bjdooks_ (n=ben@trinity.fluff.org) [NETSPLIT VICTIM] |
| 01:38.10 | *** join/#openjtag bjdooks (n=ben@trinity.fluff.org) |
| 06:12.33 | *** join/#openjtag drath_ (i=vmaster@p5B07F070.dip.t-dialin.net) |
| 11:19.44 | *** join/#openjtag davygravy (n=davygrav@h75-100-82-203.75-100.unk.tds.net) |
| 11:39.01 | *** join/#openjtag davygravy_ (n=davygrav@h75-100-89-252.75-100.unk.tds.net) |
| 12:49.27 | *** join/#openjtag roxfan (n=dunno@28.63-136-217.adsl-dyn.isp.belgacom.be) |
| 13:09.29 | *** join/#openjtag drath_ (i=vmaster@p5B07FD53.dip.t-dialin.net) |
| 13:14.08 | *** join/#openjtag prpplague (n=dave@mail.americanmicrosystems.com) |
| 13:20.17 | prpplague | drath: greetings |
| 13:20.25 | drath | hey prpplague |
| 13:21.55 | drath | prpplague: regarding your reset issues: you're using a script - how's that called? |
| 13:35.14 | prpplague | drath: hey sorry was getting coffee |
| 13:35.27 | prpplague | drath: yea its called as part of the reset |
| 13:35.47 | prpplague | drath: one sec and i'll pastebin |
| 13:36.49 | prpplague | drath: http://pastebin.ca/1003889 |
| 13:37.38 | prpplague | drath: http://pastebin.ca/1003890 |
| 13:37.46 | prpplague | drath: thats a typical example |
| 13:38.30 | prpplague | drath: normally what would occure is a shell script would run openocd which then flashes the device, as it leaves openocd the device is reset |
| 13:39.09 | prpplague | drath: as the shell script continues to run it starts a chat session which does some basic tests of the device via the rs-232 and makes some measurements via a ADC |
| 13:39.22 | prpplague | drath: once the device has passed the tests its marked as ready |
| 13:39.33 | prpplague | drath: and the shell script terminates |
| 13:49.53 | *** join/#openjtag toi (n=pleemans@d5152D3B4.access.telenet.be) |
| 13:59.05 | drath | prpplague: did you try "reset run" instead of "reset" in the script? |
| 13:59.14 | drath | prpplague: you configure reset action "run_and_init" |
| 13:59.27 | prpplague | drath: yes, the reset run does work but it complains about timeouts |
| 13:59.29 | drath | prpplague: i guess it's correct for the openocd to reexecute your script |
| 13:59.39 | prpplague | drath: yes |
| 14:00.05 | prpplague | drath: that is correct, however,the question is how can i can tell openocd what condition to leave the device on exit |
| 14:00.11 | prpplague | drath: thats the real issue |
| 14:00.29 | drath | prpplague: hum, i guess the answer is "what ever you did last" |
| 14:00.35 | drath | prpplague: not sure if we really need an option here |
| 14:00.46 | drath | prpplague: reset run, followed by "shutdown" should do exactly what you want |
| 14:01.04 | prpplague | drath: it does, but it produces a whole range of error and warning messages |
| 14:01.16 | drath | prpplague: ok, then we need to fix those :) |
| 14:01.26 | prpplague | drath: essentially its trying to check and make sure that the first reset has completed |
| 14:01.52 | prpplague | drath: personally i'd prefer to see an option which specifies what action to take when shutdown is called |
| 17:19.21 | *** join/#openjtag ali_as (n=as@ambix.plus.com) |
| 19:55.46 | *** join/#openjtag ali_as_ (n=as@ambix.plus.com) |
| 22:37.34 | *** join/#openjtag ali_as (n=as@ambix.plus.com) |