I reread the post and I didn't find the answer of my post I did earlier.
Maybe you could start by this if you need us to have a better understanding.
1- First A layout picture of your settings
2- Maybe just use a pc and the Raspberry PI and see if you are able to connect both Xbee using terminal application.
minicom for the RPi and the Xbee application for the pc. Do they communicate manually.
3- Add leds with a resistor to the TXM and RCV pins to the XBee connected to the Raspberry PI. This way you could see if something transmit. (Anode on 3.3V, cathode with a 2K resistor on the XBee pins).
Also don't send and waiting to receive using SerialGetChar(). You are creating a lockup. Change attribute and set a time out with the termios options (tcgetattr and tcsetatr). http://ulisse.elettra.trieste.it/servic ... onfig.html
Or use "struct timeval"
http://stackoverflow.com/questions/1052 ... l-port-c-c
The other simpler method is to check the number of available character "serialDataAvail" before SerialGetChar(). This way you don't create lockup because you could add your own time out routine if you don't received anything.
On your P.C. what king of Xbee setup you have? I assumed a USB XBee Adapter. If it is true you could removed the XBee and connect the TXM and RCV pins of the adapter directly to the RCV,TXM of the RPI since the USB adapter will already set the pins to 3.3V. This way you could check the direct link without any Xbee adapters and see if you have communication.
Since You give just little code without showing us How the layout is, it is very hard to figure out what you are doing wrong.