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
NUCLEO_L432KC: Fixed async serial #5535
NUCLEO_L432KC: Fixed async serial #5535
Conversation
PS: sorry about the duplicate pull request ... i was not able to remove the unnecessary merge commit ... i did a reset to the mbed-os master, which removed my commits and thus automatically closed the previous pull request ;) |
@MikeDK Thanks ! Good to see that coming from a branch, you can now use master to follow upstream/master 💯 |
@ARMmbed/team-st-mcd Please review |
@MikeDK any tests done with this fix? |
/morph test |
@0xc0170 Yes I did some testing with the logger class I wrote for our project. The class supports blocking and non-blocking output (the latter is useful for logging something from within interrupt context) and both is working like a charm with the fix. |
/morph build. |
/morph build |
Build : SUCCESSBuild number : 561 Triggering tests/morph test |
1 similar comment
Build : SUCCESSBuild number : 561 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 174 |
Test : SUCCESSBuild number : 375 |
Description
In targets.json there is no SERIAL_ASYNC defined for the NUCLEO_L432KC developer board.
When adding this option, a bug in targets/TARGET_STM/TARGET_STM32L4 was encountered which was leading to compile errors.