Ø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 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. 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 > > > > > There are two separate issues here:
- The jtag scans that are used to add the Cortex-A8 cpu to the Omap3530 IcePicker. This works. It even works if it is called again when the Cortex-A8 Jtag tap is already configured. The only thing is that the OpenOCD JTAG scan chain identification and verification code gets a bit confused, it receives responses from two configured TAPs but it only expects one. The alternative is to hard reset the target, and we really do not want to do this, we want a nondestructive attach. - Using TAP_IDLE as default end state for all scans. This is the default in all arm_adi_v5 scans. So the issue is a nonissue. Regards, Magnus _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
