Ok, here are the dumps. The script worked properly on the legacy driver (rt2570), but I had a couple of issues with it on the rt2500usb 1) the register files were in a register subdir instead of as the same level as "chipset", more more importantly 2) the chipset file existed, but had empty contents. I hard-coded the values that were reported in the legacy driver to get the provided dumps.
Strange that the chipset file was empty. S
There are several differences in the values, likely some are strength, etc since the values are close. I have the rt2570 driver built with channels 1-14 enabled in case that shows up in the registers. Most interestingly, the CSR registers on the legacy driver don't seem to be used, or are at least all filled with the same value.
This means the CSR debugfs reading in the legacy driver is broken.
I'll try to check the rt2x00 register and see if that provides sufficient information. (My guess is that the bug is in the BBP registers.
In case it's useful, I've also included a dump (from rt2500usb/frame/dump) of the time period during an attempted association (I haven't done any sanity checking on it).
One other bit I noticed that may or may not be relevant at this stage of association is the mode reported in debugfs - it seems to default to 802.11g but I'll need it at 802.11b, will this get negotiated during the assoociation stage?
802.11G is backwards compatible with 802.11B so it won't change during association but shouldn't hurt either,