Can be frustrating when you only have one thing to test against. In general looking at that diagram yes you should tie all grounds together, so GND and Vcc of the part marked USB2TTL should be tied to the Wifi module assuming they are both 3.3V devices.
Yes, it's not really what I'd call a good datasheet but at a quick look I can't see any mention of the UART pins being 5V tolerant. A lot of those devices use ARM processors and them not coping with voltages above the supply input is fairly common. Unlike some small micros the clamp diodes tend to be a lot less 'robust' and a few types I've used can be destroyed by even a few mA (or don't have clamps at all).
@MichelKogan My vote goes to a blown device, after the 5 Volt experiment. Also, if the device "worked" earlier, can you fit it back into that earlier state to verify that it still works?
@MichelKogan It can still be blown. I have an Atmega328 microcontroller here which has its analog input pins blown (at least some of them), yet it blinks LEDs fine on a digital GPIO.
i'm sure its not blown because I tested it before with that voltage and it works just perfectly ... ( the time that I didn't have this new converter with 3.3v mode capability )
@MichelKogan Only way to confirm is to take that module and test it the way you tested it before. Blinking LEDs will not assure against partial damage.
Probably not much consolation but once I destroyed about 20 x $120 modules about 5+ years ago or so by doing a design using somewhat similar modules by connecting 3.3V logic when they needed 2.8V. They worked a while (sometimes weeks) before failing one by one, anyway you always learn from painful mistakes...
Another odd behavior ... if I connect RX to RX and TX to TX, and send any character with my terminal program, it response with double dots ".." ... for example if I send +++ it gives me "......" if I send "AT+WSCAN" response with ".ª.Q....." ... why its functioning like this ?
Possibly a form of crosstalk, but connecting TX to TX (two outputs) together is a bad idea so I'm not really sure what your badly abused chips would be doing now ;-)
@MichelKogan, I'm about to head off (getting late here) but I'd say unfortunately you're likely to be out of luck with that module and maybe need a new one and not connect to over 3.3V and be careful with RX/TX.
Xilinx customer service is on a serious downward slide. I just went to their webpage and pretty much anything you click from the front page gets a 404 if you aren't signed in.
(Well, I clicked on "Support" and "Downloads", maybe they'd still be willing to tell you how great their chips are without a login?)
@rawbrawb You can be an alien, but I am a particle.
@ThePhoton a close freind was regaling me with how obscure some of the some of the usage stuff is. and the documentation was sparse in key areas of some of the larger blocks.
I don't remember the details, but if you followed their examples you were fine, but if you wanted to do some other things you had to "experiment" and he found al sorts of undocumented linkages ...
@rawbrawb Their parts are just so freaking complicated I don't know if it would be possible to document everything.
@rawbrawb I think they kind of changed gears over the last few years...And as an Altera FAE, he didn't actually work for Altera, he worked for a distibutor.
@rawbrawb My Xilinx sales rep still remembers me as the guy who expressed extreme scepticism about their ability to do a 100 MHz to 3 GHz CDR (or whatever they claimed before the silicon was released) in their first generation SERDES.
I think they do a lot of documentation before they get actual silicon delivered. Then not everything gets updated to reflect reality, unless real customers run into problems.
@rawbrawb Dunno what the real issue was, but every other vendor (Vitesse, TriQuint, ..) at that time was just starting to release CDRs with specs like 0.98 to 1.02 Gb/s, and Xilinx came along and claimed more than an octave tuning range (IIRC)...
@ThePhoton that's a smart call... I know someone who had to go pick up his guy at the local bar in the morning, before it was too late ... but it was worth it.