Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i am not able to connect to xm125, it says unable to connect recv timeout #146

Open
ksenthurkumaran18052004 opened this issue Jun 11, 2024 · 13 comments

Comments

@ksenthurkumaran18052004

i am not able to connect to xm125, it says unable to connect recv timeout
Screenshot 2024-06-11 124851
But i amble to flash
please help

@vackraetraed
Copy link
Contributor

Hello @ksenthurkumaran18052004

Are you using XE125 or have you used XM125 directly and try to make your own connecting board?

@sulaco67
Copy link

sulaco67 commented Jun 15, 2024

Hi. Exact same issue here. Using XE125 board with Silabs 11.3.0.176 driver.
Flashed OK
Please assist

@trent-lane
Copy link

Hi to all! I've encountered the same problem. The module is barebone XM125 with 3v3 power and UART levels, CH340 is used for serial connection.
XM125 dev

Connections:

1    VIN    3v3
2    GND    GND
3    1v8    1v8
4    GND    GND
5    TX     RX_CH340
6    RX     TX_CH430
13   GND    GND
14   nRST   button to GND
26   BOOT0  button to 3v3

I am able to flash it:
image

But when trying to connect all I get is "recv timeuot". I've tried to set baudrates manually, but 9600, 57600 or 115200 didn't work. The oscilloscope shows that TX pin of CH340 goes low for a brief time (XM125's RX), but nothing changes at it's RX (XM125's TX, accordingly).

@vackraetraed
Copy link
Contributor

@sulaco67 There are two COM ports on XE125, try using both. Both are able to flash the module but only the enhanced COM port supports running the Exploration Tool.

@trent-lane In a similar manner, only one of the UARTs support the Exploration Tool protocol, which UART TX and RX have you connected? Could it be the one that only supports flashing?
Both the default module binary and the Exploration Tool uses flow control, you can either connect the the flow control pins or disable it by re-building the Exploration Server binary without flow control in the XM125 SDK.

@trent-lane
Copy link

trent-lane commented Jul 24, 2024

@trent-lane In a similar manner, only one of the UARTs support the Exploration Tool protocol, which UART TX and RX have you connected?

First I've tried:

5    UART_TX     RX_CH340
6    UART_RX     TX_CH430

My next try was:

21    DEBUG_UART_RX     TX_CH340
23    DEBUG_UART_TX     RX_CH430

Pin mapping and names are taken from "Entry+ Module XM125 Datasheet, v1.2".

I can flash the module using either UART, but still can't connect it even when using DEBUG_UART connection. I've also tried some common baudrates and swapped to another USB ports.

image

UPD

I've tried both Full and Quick start (portable) versions for Windows, still the results are the same - the XM125 can't be connected to.

@trent-lane
Copy link

I've found a solution. There are additional pins that need to be connected for bootloader to communicate with desktop app:

8    UART_CTS     DTR_CH340
9    UART_RTS     CTS_CH430

Thank you, vackraetraed!

@vackraetraed
Copy link
Contributor

@trent-lane Glad it helped with flow control.

As for the other peoples issue, I am not sure it helps.
XE125 has flow control automatically setup on the USB.
However, if they are wiring UART from the header pins, they should use CTS/RTS.
Also, solder bridges on XE125 have to be cut for the UART pins if the header pins are used.
Otherwise the on-board UART->USB chip will be driving the pins.
Looking at the schematic, it is specifically SB1, SB2, SB3, SB4.

@caspersauce
Copy link

caspersauce commented Aug 9, 2024

@vackraetraed @sulaco67 @ksenthurkumaran18052004 Was this resolved?

I am getting the exact same issue on Windows 10. I have a brand new XE125, a fresh install of the explorer tool, fresh install of the CP210X drivers. The tool opens just fine, flashes the most recent firmware just fine, but refuses to connect. I get "recv timeout" no matter what I do. Both ports give the same error, despite baud rate, flow control etc...

@caspersauce
Copy link

No idea if this helps anyone else, but I reflashed both ports multiple times, still no progress. Unplugged everything, rebooted everything, no progress.

I then flipped the USB-C over because of something I saw in another post. Everything now works... No idea what this means, but maybe it will help somebody.

@skypopcorn1
Copy link

flipping the USB-C over fixed the issue for me as well. Hours wasted trying to debug this. @acconneer team - any thoughts on this?

@vackraetraed
Copy link
Contributor

@skypopcorn1
It is not unthinkable that parts of the connector might be broken which could potentially break the symmetry of the USB-C connection.

Glad to hear that it still works though.

@Jean-BaptistePerrier
Copy link

Fixed by swapping the usb cable as well. I'm betting the DP/DM pins are only routed for one row of the connector.

@vackraetraed
Copy link
Contributor

@caspersauce @skypopcorn1 @Jean-BaptistePerrier

If possible, could you scan the QR codes and post the serial numbers of your XE125 devices?

Also, any info on the USB cables used would help as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants