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

nrf52: SPI transfer failure and corruption #1777

Merged
merged 1 commit into from
Sep 14, 2020

Commits on Sep 13, 2020

  1. nrf52: SPI transfer failure and corruption

    The current EasyDMA implementation will fail if a transfer of over
    255 bytes is requested with no warning.
    
    Also we do not set the RX and TX transfer lengths to 0 if the
    buffer is NULL which can cause data to be written to the old
    address as well as cause unexpected transaction lenghts.
    Example:
      transfer 1:
       rx_len  = 10
       rx_buff != NULL
       tx_len  = 10
       tx_buff != NULL
      transfer 2:
       rx_len = 2
       rx_buff != NULL
       tx_buff == NULL
      Total transaction length for the second would be 10 because it
      would still be using the old rx length of 10 and would
      corrupt data in the old rx buffer.
    
    Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
    btashton committed Sep 13, 2020
    Configuration menu
    Copy the full SHA
    66cf4eb View commit details
    Browse the repository at this point in the history