Commit Graph

25532 Commits (aaf7a133111d367eb47d88df7eed2bd735ada161)

Author SHA1 Message Date
cyliangtw 0eddd52999 Add Nuvoton M261 sub-family 2019-08-23 11:37:41 +01:00
Martin Kojtal 808c45062f
Merge pull request #11195 from ARMmbed/release-candidate
Release candidate for mbed-os-5.13.3
2019-08-14 11:55:15 +02:00
Martin Kojtal d587e73ab3 Cellular unittest: Fix wrong rebase - remove not valid file 2019-08-12 12:54:51 +01:00
Seppo Takalo dd1d867bac Merge pull request #11156 from artokin/nanostack_patch_for_mbed_os_5_13_x
Nanostack patch release for Mbed OS 5.13.x
2019-08-12 12:54:50 +01:00
Seth Itow ec35930848 stm32f413xh: add crash capture support for IAR 2019-08-12 12:54:49 +01:00
Seth Itow 748971d6ce stm32f413xh: add crash capture support for ARM_MICRO 2019-08-12 12:54:48 +01:00
Seth Itow cc5b134cac stm32f413xh: add crash capture support for GCC_ARM 2019-08-12 12:54:47 +01:00
Ireneusz Gaicki 5090d5c190 STM32F7: Do not generate redundant IN tokens
When STM32F746-DISCO board was being used in (unsupported) USBHost mode,
the communication was unreliable. Our investigation revealed that the
problem lied in redundant IN tokens that the host generated even though
it shouldn't. This could lead to endless high-frequency NAKs being
received from device, which caused watchdog reset as USBHost spent all
time in interrupt handlers.

In our application the clocks frequencies are:
  * HCLK = 48 MHz
  * APB1 = 6 MHz
  * APB2 = 12 MHz

We have captured the raw USB High-Speed traffic using OpenVizsla.
Without this change, when USB MSD device connected to the system
responded to IN with NAK, there were excessive IN tokens generated about
667 ns after the NAK. With this commit the IN tokens are generated no
sooner than 10 us after the NAK.

The high frequency of the IN/NAK pairs is not the biggest problem.
The biggest problem is that the USB Host did continue to send the IN token
after DATA and ACK packets were received from device - *without* any request
from upper layer (USB MSD).

The USB MSD devices won't have extra data available on Bulk IN endpoint
after the expected data was received by Host. In such case IN/NAK cycle
time is only houndreds of nanoseconds, the MCU has no time for anything else.

The problem manifested not only on Bulk endpoints, but also during
Control transfers. Example correct scenario (when this fix is applied):
  * SETUP stage
    * SETUP [host -> address 0 endpoint 0]
    * DATA0 [80 06 00 01 00 00 08 00] [CRC16: EB 94]
    * ACK
  * DATA stage
    * IN
    * NAK
    ... the IN/NAK repeated multiple time until device was ready
    * IN
    * DATA1 [12 01 10 02 00 00 00 40] [CRC16: 55 41]
    * ACK
  * STATUS stage
    * OUT
    * DATA1 ZLP
    * ACK

Without this commit, in DATA stage, after the ACK was received, the host
did send extra IN to which device responded with STALL. On bus it was:
  * DATA stage
    ...
    * IN
    * DATA1 [12 01 10 02 00 00 00 40] [CRC16: 55 41]
    * IN
    * STALL
    * IN
    * STALL
  * STATUS stage
    * OUT
    * DATA1 ZLP
    * STALL

In the fault case the next SETUP was sent only after 510 ms, which
indicates timeout in upper layer.

With this commit the next SETUP is sent 120 us after the STATUS stage ACK.
2019-08-12 12:54:47 +01:00
Szymon Szantula 5f4825c5bf __cplusplus guard fixed
This error prevented using this header in cpp code directly.
2019-08-12 12:54:46 +01:00
Maciej Bocianski b2bd371aa8 Xpresso: qspi_write fix
Due to the data buffer is loaded in two steps the whole block needs protection from being interrupted
2019-08-12 12:54:45 +01:00
Seppo Takalo 70af1a518c Zero initialise all NVStore&kvstore members 2019-08-12 12:54:45 +01:00
desmond.chen ef934aea03 Fix include path issues on NRF5x with Cordio 2019-08-12 12:54:44 +01:00
Ari Parkkila d160098651 Cellular: Add DNS servers from PDP contexts to nsapi_dns 2019-08-12 08:44:06 +01:00
Ari Parkkila 527daa0446 Fix nsapi_dns_add_server to add a server just once 2019-08-12 08:42:56 +01:00
Michal Paszta 08f77e1007 Coverity and compilation warnings fixes 2019-08-12 08:42:56 +01:00
Michal Paszta dc55dae623 Bring back SPIF module-specific debug logs
The logs are switched off by default and can be enabled with a
module-specific compile switch in mbed_app.json.

Logs brought back from PR #10501
2019-08-12 08:35:16 +01:00
Kyle Kearney 0bde671c86 Fix inout pins not functioning correctly
Update the drive mode when setting the GPIO direction.
2019-08-12 08:35:16 +01:00
desmond.chen edfdc946c3 NRF52 need to call TIMER_TASK_SHUTDOWN for current consumption 2019-08-12 08:35:16 +01:00
maclobdell a83dc21e97 fix rom start & size for psoc6 targets for 5.13 2019-08-12 08:35:15 +01:00
Maciej Bocianski 29aa19379b freescale: fix i2c_byte_read function 2019-08-12 08:32:07 +01:00
Chun-Chieh Li d8dff83fcb Nuvoton: Remove dead code nu_delay_cycle_x4(...)
Originally, nu_delay_cycle_x4(...) is borrowed from mbed test code for delay
cycle. Currently, it is not used on Nuvoton targets. If delay cycle is needed,
use wait_ns(...) instead which has strict implementation and has passed tests.
2019-08-12 08:32:07 +01:00
Leszek Rusinowicz 0fabceea00 FUTURE_SEQUANA: Add missing serial_free() implementation 2019-08-12 08:32:07 +01:00
int_szyk ef369dd926 Newline at the end of files 2019-08-12 08:32:07 +01:00
int_szyk 2e7c7f754f Astyle 2019-08-12 08:32:06 +01:00
int_szyk 50edb3d920 Update main.cpp 2019-08-12 08:32:06 +01:00
int_szyk 6d38596a27 Updated testcases 2019-08-12 08:32:06 +01:00
Kimmo Vaisanen 195d8febd3 Fix MBED_ASSERT for UTs
For UTs mbed_assert_internal should not be declared as MBED_NORETURN
as UT stub for mbed_assert_internal only prints out the assert trace
and returns back to original code.
2019-08-12 08:32:06 +01:00
Neil Tuttle 22238f8187 PSOC6: Remove USBDEVICE from FUTURE_SEQUANA targets 2019-08-12 08:32:05 +01:00
Neil Tuttle 227b6ce027 PSOC6: USB device implementation 2019-08-12 08:32:05 +01:00
Ari Parkkila a1ffecca00 Cellular: Fix statemachine stop 2019-08-12 08:32:05 +01:00
Ari Parkkila e80e0cfc68 Cellular: Fix BG96 power up 2019-08-12 08:32:05 +01:00
Kyle Kearney 217a1da362 Bug fixes to I2C and SPI drivers
- Fix assert when spi_master_block_write called with 0 size
- Fix assert when spi_format called before spi_frequency
- Simplify implementation of spi_master_write
- Simplify pointer arithmetic expressions in cyhal_spi_transfer and
  cyhal_spi_transfer_async
- Fix I2C driver not honoring the frequency specified during init.
2019-08-12 08:32:05 +01:00
int_szyk 200e7055de Can compile without serial 2019-08-12 08:32:05 +01:00
Kyle Kearney b9e9ff94a7 Add target for CY8CKIT_062S2_43012 2019-08-12 08:32:05 +01:00
Evelyne Donnaes b81aeff1a3
Merge pull request #11110 from ARMmbed/release-candidate
Release candidate for mbed-os-5.13.2
2019-07-26 19:24:03 +01:00
Evelyne Donnaes 337c5b424f "Update secure binaries for LPC55S69_S (ARMC6)" 2019-07-26 15:58:04 +01:00
Ari Parkkila 23986f1eb6 Cellular: Fix to delete context just once 2019-07-26 10:18:24 +01:00
Evelyne Donnaes dbe9bfc685 Update Mbed version block 2019-07-25 15:18:28 +01:00
Vladislav Talanov 01bd07c9a2 add defines sectors for STM32F446ZE 2019-07-25 15:18:28 +01:00
Ben Cooke 6e1dc84263 nrf52840: remove align instructions from gcc linker for ARM.extab exidx sections 2019-07-25 15:18:28 +01:00
Tomasz Moń 3c6348d04d GCC ARM: Increase develop and release debug level
Do not specify the debug level for develop and release profiles. Instead
rely on the compiler to choose sensible default (-g2). Note that -g1 is
minimal debugging information and does not include structure definitions
which quite heavily reduces debugging experience.

For develop and release profiles this results in elf file containing
structure definitions. This does not impact debug profile as it already
did use -g3 which is the highest debug level.

Compatible debuggers (eg. gdb, SEGGER Ozone) can use the extra information
to provide better debugging experience. For example, when compiled .elf is
loaded in gdb, this change makes it trivial to access internal RTX data.

Without this change on develop profile:
  (gdb) print osRtxInfo.thread.run
  'osRtxInfo' has unknown type; cast it to its declared type

With this change on develop profile:
  (gdb) print osRtxInfo.thread.run
  $1 = {curr = 0x20014F04, next = 0x20014F04}
2019-07-25 15:18:28 +01:00
George Beckstein fa620d55ce Fix SAADC resolution for nRF52-based targets... again 2019-07-25 15:18:28 +01:00
Ben Cooke 2d1f7fa78c NRF52840: fix include path issues for cordio ll and gcc 2019-07-25 15:18:28 +01:00
Ben Cooke 30e747760a NRF52840: enable TRNG in Nordic SDK config 2019-07-25 15:18:28 +01:00
Mahesh Mahadevan ecb444b989 MCUXpresso: Fix the LPC GPIO IRQ driver
The IRQ disable was always disabling both rising
and falling edges of the interrupt thereby causing
failures in cases when one of the two should stay enabled.

Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
2019-07-25 15:18:28 +01:00
Mahesh Mahadevan f23bb080d6 LPC54114: Fix compile warnings
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
2019-07-25 15:18:27 +01:00
Mahesh Mahadevan e019d7a64f MCUXpresso: Update LPC SPI HAL driver
Add support for different slave selects

Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
2019-07-25 15:18:27 +01:00
Jaeden Amero ccb8f25872 mbedtls: Update to Mbed TLS 2.18.1
Update to Mbed TLS 2.18.1 and Mbed Crypto 1.1.1.
2019-07-25 15:18:27 +01:00
Mahesh Mahadevan df8cf28084 MCUXpresso: Update the Analogin driver for LPC devices
1. Update the clock divider setting
2. ADC resolution is 12-bits, update the API return value
   to return 16-bit result
3. Update IOMUX setup

Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
2019-07-25 15:18:27 +01:00
Mahesh Mahadevan dc5ff9ecd6 LPC54114: Update the ADC SDK driver
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
2019-07-25 15:18:27 +01:00