I'd like to interject here - chris is having similar problems to mine with X-CTU; you are right in using XB24-B for series 2, but I think I damaged my end device when just connecting 3.3, gnd and sensor (off for now) to D0 (you are using D1). I am trying to track down what to do with the din/dout pins. Digi says to connect them (to what?) but then they say idle pins need not be connected.

I'm having some serious problems with X-CTU and an Xbee chip that is supposed to operate as a sensor only. Its board connects only ground, vcc and d0, and led/resistor to ad5. I am wondering what to do with din and dout - the manual does not specify anything.
After successfully flashing the chip with X-CTU it started acting up on its board (assoc led flashes randomly and varies depending on hand proximity.) It seems to communicate using Andrew Rapp's library, but X-CTU will not recognize it anymore. I checked for any board shorts or opens.

Thanks - it looks like this might be a cloned board (I'm going to visit the reseller tomorrow) and it's not providing what the usual Xbee shield provides. Beware of clones!

Hi - I got an XbeePro shield for the Arduino and it seems to have blown the Xbee chip; I notice the Arduino (328) sends 5V up the din/dout lines into the Xbee. I don't think that is supported by an Xbee Series 2.
Anybody seen this problem before?

Dont forget ... no EEPROM on netduino.