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

BLE broken pipe unrecoverable #813

Closed
3 tasks done
mrx23dot opened this issue Mar 12, 2024 · 3 comments
Closed
3 tasks done

BLE broken pipe unrecoverable #813

mrx23dot opened this issue Mar 12, 2024 · 3 comments

Comments

@mrx23dot
Copy link

Answers checklist.

  • I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
  • I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

After first BLE connection failure with broken pipe it cannot connect to anything without a reboot.

So it's getting stuck.

AT+BLEINIT=1

# ensure not connected
AT+BLEDISCONN=0
ERROR

# connection fails 
AT+BLECONN=0,"73:f7:7c:18:70:b1",1,5
+BLESCANDONE
+BLECONN:0,-1
ERROR

# ensure not connected
AT+BLEDISCONN=0
ERROR

# connect to any other
AT+BLECONN=0,"5f:29:72:aa:82:c4",1,5
+BLESCANDONE
+BLECONN:0,-1
ERROR

# same error to any other addresses without reboot

It doesn't even seem to wait for timeout period, fails instantly.

Reboot solves the issue.
AT+BLEINIT=0 seems to simply reboot the system, which is slow.

AT+BLEINIT=0
ready

version

AT+GMR
AT+GMR
AT version:3.2.0.0(s-ec2dec2 - ESP32 - Jul 28 2023 07:05:28)
SDK version:v5.0.2-376-g24b9d38a24-dirty
compile time(6118fc22):Jul 28 2023 10:14:50
Bin version:v3.2.0.0(PICO-D4)
@ustccw
Copy link
Collaborator

ustccw commented May 17, 2024

@Luxin812 PTAL

@Luxin812
Copy link
Contributor

Luxin812 commented Jul 1, 2024

Answers checklist.

  • I have read the documentation ESP-AT Programming Guide and the issue is not addressed there.
  • I have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

After first BLE connection failure with broken pipe it cannot connect to anything without a reboot.

So it's getting stuck.

AT+BLEINIT=1

# ensure not connected
AT+BLEDISCONN=0
ERROR

# connection fails 
AT+BLECONN=0,"73:f7:7c:18:70:b1",1,5
+BLESCANDONE
+BLECONN:0,-1
ERROR

# ensure not connected
AT+BLEDISCONN=0
ERROR

# connect to any other
AT+BLECONN=0,"5f:29:72:aa:82:c4",1,5
+BLESCANDONE
+BLECONN:0,-1
ERROR

# same error to any other addresses without reboot

It doesn't even seem to wait for timeout period, fails instantly.

Reboot solves the issue. AT+BLEINIT=0 seems to simply reboot the system, which is slow.

AT+BLEINIT=0
ready

version

AT+GMR
AT+GMR
AT version:3.2.0.0(s-ec2dec2 - ESP32 - Jul 28 2023 07:05:28)
SDK version:v5.0.2-376-g24b9d38a24-dirty
compile time(6118fc22):Jul 28 2023 10:14:50
Bin version:v3.2.0.0(PICO-D4)

This issue has been fixed. Can you test it using release v3.4.0.0 or the latest firmware on the master branch to test it.

@ustccw
Copy link
Collaborator

ustccw commented Oct 10, 2024

We assume this worked for you, and will close it. If that's not the case, please open another github issue.

@ustccw ustccw closed this as completed Oct 10, 2024
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

4 participants