Skip to content

Add flush to the BLE UART Service #4990

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

Merged
merged 1 commit into from
Sep 28, 2017

Conversation

akosthekiss
Copy link
Contributor

If only buffer-full events and LF characters trigger the flush of
the send buffer then only line-based communication can be
implemented over the BLE UART Service. This patch extends the
service API by adding an explicit flush method to force sending
the buffer contents, thus enabling protocols with short (e.g.,
single character) messages.

Status

READY

Migrations

NO

If only buffer-full events and LF characters trigger the flush of
the send buffer then only line-based communication can be
implemented over the BLE UART Service. This patch extends the
service API by adding an explicit `flush` method to force sending
the buffer contents, thus enabling protocols with short (e.g.,
single character) messages.
@0xc0170
Copy link
Contributor

0xc0170 commented Aug 31, 2017

@pan- please review

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 4, 2017

@pan- Bump

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 8, 2017

Bump for review @pan-

@akosthekiss
Copy link
Contributor Author

Is there any way I can help the progress of this PR?

Copy link
Member

@pan- pan- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm OK with the PR.
However, the UART service, as a whole, needs to be reworked. ATM there is no guarantee that the data has been correctly sent.

@akosthekiss
Copy link
Contributor Author

Is there anything else I should/could do?

@theotherjimmy
Copy link
Contributor

Thanks for the ping @akosthekiss. We're currently working on a release, so testing may be delayed by a few days. In the mean time I have marked this as in the "testing" phase of a PR. We should get to testing many things in the needs: CI category, and merge them, shortly after the release.

@akosthekiss
Copy link
Contributor Author

Thanks for the update!

@theotherjimmy
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1358

Test failed!

@akosthekiss
Copy link
Contributor Author

@theotherjimmy Could these tests be re-executed somehow, perhaps? I don't know what could have failed.

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 24, 2017

/morph test

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1378

Test failed!

@akosthekiss
Copy link
Contributor Author

I'm a bit puzzled. In mbed Build Number 1358, the MAX32630FTHR/GCC_ARM target failed, while in Build 1378, it was the ARM-BEETLE-SOC/GCC_ARM. It was 3 tests that timed out in both runs: tests-mbedmicro-rtos-{queue,isr,signals}. Is this some kind of flakyness of the test suite?

@akosthekiss
Copy link
Contributor Author

@0xc0170 @theotherjimmy @pan- May I ask some help on this? (I mean, on the strange timeouts.)

@pan-
Copy link
Member

pan- commented Sep 26, 2017

Is this some kind of flakyness of the test suite?

Maybe, or an issue in the CI. Those failures are not related to the PR.
@0xc0170 Can we launch a new run ?

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 27, 2017

/morph test

1 similar comment
@studavekar
Copy link
Contributor

/morph test

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 1413

All builds and test passed!

@theotherjimmy theotherjimmy merged commit f0a1075 into ARMmbed:master Sep 28, 2017
@akosthekiss akosthekiss deleted the ble-uart-flush branch October 1, 2017 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants