-
Notifications
You must be signed in to change notification settings - Fork 3k
Improve serial performance for NRF52 series #7323
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
Conversation
Previous implementation would block until character had been completely sent, which is not what the API specifies.
Time sensitive user callbacks are called through lowest priority SWI handlers instead of the highest priority UART handler.
/morph build |
Build : SUCCESSBuild number : 2444 Triggering tests/morph test |
Test : SUCCESSBuild number : 2223 |
Exporter Build : SUCCESSBuild number : 2075 |
@kjbracey-arm Thank you for the suggestions in the other thread! The ESP8266 seems a bit more robust now. @0xc0170 Please don't merge it just yet, I'm waiting for feedback from people testing it. |
Hi @marcuschangarm. We recently found an issue with the way Astyle in Travis CI was being setup such that it was always failing PRs. The PR will need to be rebased to get the fix which is now in master (#7338). Once this PR is rebased, we'll prioritize getting it back into CI as soon as possible. |
Nvm on the rebase, for now. SourceForge appears to be working for the time being. If the issue comes back a rebase will resolve the issue. |
I'm not sure if I'm doing something wrong, but it looks like that this patch is causing some problem using the serial after the
Trying to add a Everything is working trying the same example on the commit before this patch was applied. |
@tanoc Thanks for pointing that out, looks like level 4 is reserved to softdevice non time critical processing (see here). @marcuschangarm Could you fix the issue caused by this change ? |
I can't reproduce the error. I tried the BLE_Beacon example on my NRF52840_DK and NRF52_DK board and both print out the MAC address. There is a new PR up with changes to the serial driver: #7369 but that should be unrelated to Tx. Regarding the interrupt priority, the #define changes value depending on whether the SoftDevice is included or not, and |
I tried it on a custom board with an NRF52832 but I think the only different setting I have in the configuration |
That part of the code shouldn't have changed. Can you double check that your setup works with the commit just prior to this PR please? |
Sure, I'll double check it again on Monday with the BLE_Beacon example. I'm pretty sure I've tested it on commit d3641fd and faa31de. And I'm sure in the other project I'm working on I'm using d3641fd without problems (I initially had the problem working on it and then tried the BLE Beacon example to be sure it was not something wrong in my code). |
Did a couple more test. Trying with the "clean" BLE_Beacon example I get the mac address printed, but trying it with an added |
@tanoc, what's the value of |
I have it set to |
@tanoc If this is still an issue, would you mind opening an issue so that we can track it on our end? Conversations on PRs that are closed can have a tendency to be lost over time. |
Description
Pull request type