Merge develop into main #880
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-Enabled UART HW overrun interrupt -Optimized time spent in I2C IRQ handler by moving bufffer clearing outside -Add I2C busy singaling mechanism -Add I2C ASCII encoding window command feature
- define DEVELOP_IN_NRF52833 - disable JTAG and SWO
This should result in no change in behaviour.
As this library is only used by micro:bit and not generic enough.
…me it. Also change the magic key used to identify valid data in flash as the structure has changed.
…ents (ARMmbed#932) * Re-apply "LPC55xx: Improve UART TX performance." This reverts commit 08d6cb5. * lpc55xx_hic: Fix circ_buf asserts The assert should be checking that there are more or the same number of bytes in the circular buffer than those that are being removed, not the other way around. This was causing an erroneous assert condition in the UART interrupt handler. * lpc55xx_hic: Abort ongoing TX when changing the UART config Changing the UART config (baudrate, parity, etc) was clearing the RX and TX buffers, but if there was an ongoing TX transfer it would try to remove the bytes from the TX buffer after the transfer completes. This patch cancels any ongoing TX transfer when clearing the buffers on config changes and UART reset.
Also use memcpy in i2c_clearTxBuffer().
As soon as target was done I2C reading from DAPLink it was getting ready the next messsage. Sometime it would send the next I2C write before the TX callback had time to run in the RTOS main thread.
The state should be changed when the target request DAPLink to go into MB_POWER_DOWN mode, not when the reset button has been long pressed.
Nordic EasyDMA needs the data to be 32-bit aligned. The KL27 code to write to flash asserts also for alignment, so ensure the buffers sent to storage_program_flash() are aligned too.
When a 32 bytes data (or custom data) record is processed and the `HEX_PARSE_UNALIGNED` status is triggered, the `line.buffer` index variable `idx` is set to a value one-too-large and causes a write out-of-bounds, which can corrupt other data placed right after it in RAM. Increasing the hex_blob pointer before exiting the function ensures the start of new record is processed before the `line.buf[idx] |= ctoh((uint8_t)(*hex_blob)) & 0xf;`, which resets `idx` back to zero. More info in PR ARMmbed#936
mbrossard
force-pushed
the
feature/merge-develop-to-main
branch
from
8853323
to
fbb36f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
lpc5xxHICnrf52820HIC