> Hi all, > Does anyone here use the facilities in C-Spy, Quadravox, etc. to get a > concise display of all the registers in a peripheral? People are asking > me if this can be provided in the mspgcc toolchain. Well, of course it > can, by modifying insight, GVD, or whatever. However, is it worth it?
> I have a lousy memory, so I have to look up locations every time I want > to inspect something. I still don't find the C-Spy display very useful, > though. They have done only the minimum they could. They don't group > registers together in a meaningful way, to make it easier to visualise a > peripheral's state. More importantly. they don't break down all the bit > fields, which might be quite useful. Something like the attached example > might be somewhat useful. It could be quite pretty too, with tasteful > colouring :-) > Any input appreciated (well legal, decent, honest, truthful input at > least).. > Regards, > Steve I use the peripheral views of debuggers for the various micros I regularly work with. They can be very useful when first getting hardware to work (you can manually turn outputs on and off, for example - no need for test programs), and they can be useful when debugging. Regarding the view, you should maybe have a look at some screenshots from AVR Studio - they have quite neat tree-based layout, with little checkboxes for individual bits. When making something like this, remember that some registers are affected by reading - I don't think access through the jtag port activates the side-effects, but it's worth checking (I'm thinking of things like the uart receive register). Is it possible for more than one program to attach to rproxy at the same time? For example, could you have gdb running and a nice little python/tkinter program connected to show these registers?
