Ø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 dealing with this situation: Sorry, but it's my personal impression from one or two discussions that the way we deal at the moment with this is "OMAP3 is broken, I don't understand it, add even stronger error messages that everybody knows it". Well, we already know ;) I would vote to do instead: - Tell exactly what is broken (from a technical point of view, maybe on a level a not so experienced OpenOCD engineer could understand, too ;) ). Example from this script: "endstate command probably didn't do what the script writers expected anyway". Why not better use two sentences explaining the potential technical problem seen? - Instead of spending time implementing even stronger error messages, better spend the time in discussion or detailed description how to fix the broken stuff. > so > I'll await specific feedback. This is fine. But in the starting point of this thread there wasn't a question for feedback. It was "because I have no idea what the script expected that command to do I disable it". And, if others like to help with missing information (see above "what do you like to know?") the answer is "I have no time". Again, that's fine, but if the answer for people trying to help is "I have no time", this doesn't seem to really work. > I just know that the endstate command > was broken in seven different ways. > > There was a discussion on the many shortcomings of ir/drscan > commands. Also there isn't(I don't think) a pathmove/statemove > command, which I can easily imagine is necessary too. > > What I believe is required to get OMAP up and running is: > > - a good OpenOCD engineer dedicating enough time at the problem. From my point of view Magus is a good candidate for this. So seems we already have one :) >There > are plenty of those around, but nobody who currently has the > motivation to > address all the problems and install OMAP into his brain. > - clean up & support the ir/drscan commands + add pathmove/statemove > commands > - create a way to robustely execute sequences that do not get bowled over > by background polling > - use all of the above to write robust configuration scripts Anyway, let's go on with Magnus' answer to this (see other mail). Best regards Dirk _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
