Øyvind Harboe wrote: >> The idea behind the the u8 * and buf stuff is to handle host endianness. >> > > the size of the integers in the array is orthogonal to solving the endianess. > > >> I cannot really see the need. Yes it takes a little while to learn, but >> any work where you stuff bits into the drscan chain needs a lot of >> careful consideration. >> The present way of doing this is clear, not very difficult to understand >> so what IS the problem ? >> > > Shouldn't I have brought it up? > No problem, but I have this experience every time start with a new processor or supplier.
- The Reference manual list all register and bit combinations, in good cases ther are defines correspoinding exactly to this structure using the same names. - The there is a programming library/api, different for every supplier, hiding what is actually going on. - When there is a problem, and there usually are a lot of problems, I have decode the library function, look up what happens in the registers, check the bitfields etc ... - So for me want a programming manual with the exact sequence of register writes, not the "nice" helper function. - I find it less work to do the register programming than learning a new api for every traget platform. Thats why :) Regards Magnus _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
