Re: [Openocd-development] Retired endstate command

2009-06-12 Thread David Brownell
On Monday 08 June 2009, Øyvind Harboe wrote: > What I believe is required to get OMAP up and running is: ... a superset of what's needed to get JRCs working on DaVinci. Hence my poking at the simple sub-problem. ;) > - clean up & support the ir/drscan commands + add pathmove/statemove > command

Re: [Openocd-development] Retired endstate command

2009-06-12 Thread David Brownell
On Friday 12 June 2009, David Brownell wrote: > On Monday 08 June 2009, Dirk Behme wrote: > > - Tell exactly what is broken (from a technical point of view, maybe > > on a level a not so experienced OpenOCD engineer could understand... > > Here's a start. Maybe other folk can add more. ... Bri

Re: [Openocd-development] Retired endstate command

2009-06-12 Thread David Brownell
On Monday 08 June 2009, Dirk Behme wrote: > - Tell exactly what is broken (from a technical point of view, maybe > on a level a not so experienced OpenOCD engineer could understand... Here's a start. Maybe other folk can add more. From the docs I have, I don't think Beagle actually needed stand

Re: [Openocd-development] Retired endstate command

2009-06-08 Thread Dirk Behme
Øyvind Harboe wrote: >> Which information do you need to get an idea what the beagle script is >> expected to do? > > I can't dive into the OMAP stuff with the time I have for OpenOCD, While this is fine (it's not different with me, else I would help more ;) ), I think we could try to improve de

Re: [Openocd-development] Retired endstate command

2009-06-08 Thread Magnus Lundin
Øyvind Harboe wrote: >> Which information do you need to get an idea what the beagle script is >> expected to do? >> > > I can't dive into the OMAP stuff with the time I have for OpenOCD, so > I'll await specific feedback. I just know that the endstate command > was broken in seven different w

Re: [Openocd-development] Retired endstate command

2009-06-08 Thread Øyvind Harboe
> Which information do you need to get an idea what the beagle script is > expected to do? I can't dive into the OMAP stuff with the time I have for OpenOCD, so I'll await specific feedback. I just know that the endstate command was broken in seven different ways. There was a discussion on the ma

Re: [Openocd-development] Retired endstate command

2009-06-08 Thread Dirk Behme
Øyvind Harboe wrote: > Committed. > Retired endstate(and updated docs). Background polling would > overwrite any changes to the endstate. From the command > line point of with the recent changes to ir/drscan the "endstate" command > wasn't used anyway. > > The best I can do for the beagleboard con

[Openocd-development] Retired endstate command

2009-06-07 Thread Øyvind Harboe
Committed. Retired endstate(and updated docs). Background polling would overwrite any changes to the endstate. From the command line point of with the recent changes to ir/drscan the "endstate" command wasn't used anyway. The best I can do for the beagleboard config files that use "endstate" is to