> So you would say the "JTAG API" is dealing with -- I'm guessing > here -- just (a) state transitions/TMS (b) clocking during RUN, > and (c) data shifting during IRSCAN/DRSCAN? Plus maybe basic > policy for scan entry/exit, to ensure that free-running clocks > don't cause un-requested state transitions?
Essentially yes. More specifically I'm thinking about the functions which sit directly on top of the minindrivers. > That'd be OK. So long as there's a simple representation of > the bit arrays to be shifted in/out. Again, that's one thing > I like about the Linux framework: it basically takes a pointer > to an "unsigned long", and a bit count. I guess we *could* use unsigned long + bit count, but if unsigned long is 32 & 64 bit respectively, then I'm not familiar with how to write code using unsigned long for >32 bit arrays. If you look at the invocation sites of the JTAG scan fn's, then >95% are <= 32 bits... -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
