Release candidate for mbed-os-5.13.4 #11308
Merged
Conversation
This file contains hidden or 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
This change is required by the Samsung S111(S5JS100). On this board timer clock used for us ticker operates at 26MHz. According to current requirements, 8 MHz is the top limit for us ticker timer. This change relaxes top limit to 100 MHz, but only for 32-bit timers. Ticker common layer schedules one interrupt per timer rollover to trace elapsed time. We need to ensure that this operation is not performed too frequently. I.e. in case of 16-bit timer at 32 MHz, the timer rollover will happen after ~2 ms. This may cause that there will be no time for other tasks. That is why we increase the top limit, but only for 32-bit timers.
…a test The `unity` dir needs to be ignore differently.
This bug prevented using this header in cpp code directly.
Macro which restricted compilation to GCC_ARM is removed. Existing read_write() test is amended to call stat() and check that correct size is returned.
This test requires total latency (tot = h/w + s/w) (wakeup from deepsleep) be under 1ms. To check the issue, measure total latency on Nuvoton targets: TARGET EXP(us) EXP+TOL(us) ACT(us) NANO130 42000 43000 42939 NUC472 42000 43000 42236 M453 42000 43000 43274 M487 42000 43000 42877 M2351 42000 43000 43213 Checking h/w spec, h/w latency (wakeup time from normal power-down mode) on M487/M2351 is just 1us (n/a on other targets). S/W latency plays the major part here. S/W latency relies on system performance. On Nuvoton targets, 'LPTICKER_DELAY_TICKS' possibly complicates the test. Anyway, to pass the test, add extra 1ms latency (deep-sleep-latency) in targets.json for Nuvoton targets.
On Nuvoton targets, lp_ticker_set_interrupt(...) needs around 3 lp-ticker ticks to take effect. It may miss when current tick and match tick are very close (see hal/LowPowerTickerWrapper.cpp). Enlarge LPTICKER_DELAY_TICKS to 4 from 3 to address this boundary case.
Fixes a bug where it has not been possible to have KVStore in internal flash while an update image image has been kept in external storage.
Thus far the default position has been after the application plus two spare sectors. For simplicity and to have a predictable location for the TDBStore with the default configuration the location is now switched to the end of the flash. Two last sectors to be exact.
…reating cc3220sf a target
1. Update to handle 12-bit resolution 2. Properly handle the pin configuration 3. Update the pin setup to handle the ADC B channel Signed-off-by: Mahesh Mahadevan <[email protected]>
UNITTEST added. TLSSocketWrapper unittest does not use stoip4_stub anymore.
… targets pass the test in worst cases
Forked 3 threads plus misc, so minimum (4 * OS_STACK_SIZE) heap are required.
…rity is IRAM1 to help maximise heap availability. Most beneficial when LWIP is not in use.
It's 2019 now.
IAR compilation fails at `_fs = { 0 };` due to
```
[Error] FATFileSystem.cpp@285,0: [Pe029]: expected an expression
```
Changing that object initializer list instead, as that seems
to pass IAR compilation, too.
Changed original memset to object initialiser list based on review
feedback from Kevin Bracey.
- Added dummy data setup API to allow users to configure the dummy data to be transferred. - Added new APIs for half-duplex transfer function. Users can send and receive data by one API in the polling/interrupt/EDMA way, and they can choose either to transmit first or to receive first. Additionally, the PCS pin can be configured as assert status in transmission (between transmit and receive) by setting the isPcsAssertInTransfer to true. - Fix for MISRA issues Signed-off-by: Mahesh Mahadevan <[email protected]>
Added dummy data setup API to allow users to configure the dummy data to be transferred. Signed-off-by: Mahesh Mahadevan <[email protected]>
Signed-off-by: Mahesh Mahadevan <[email protected]>
Update to the latest version from K66F Signed-off-by: Mahesh Mahadevan <[email protected]>
Use the K66F driver that has the latest Signed-off-by: Mahesh Mahadevan <[email protected]>
Use the latest driver from K66F Signed-off-by: Mahesh Mahadevan <[email protected]>
Signed-off-by: Mahesh Mahadevan <[email protected]>
0xc0170
approved these changes
Aug 23, 2019
|
CI started |
|
https://mbed-os.mbedcloudtesting.com/job/mbed-os-ci/job/release-candidate/ ci job also started. Results for this need to be checked separately. |
Test run: FAILEDSummary: 1 of 4 test jobs failed Failed test jobs:
|
This reverts commit 7ea8e0e.
|
CI restarted |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
|
Waiting for client to approve . Otherwise looks all good. |
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.
No description provided.