Release candidate for mbed-os-5.9.3 #7518
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
|
/morph build |
This will make incremental compile more complete, taking device_has and inheritance hierarchy into account.
Keep same clock configuration as done before this PR (LSE and PCLK1). Use a JSON file to change it.
* Elevate RTC2 interrupt priority to same level as UARTE to prevent race condition on shared variables. * Remove unused TXDRDY event code. * Fix typo in macro.
UART configuration parameters mispelled.
Use of MSG_FLAGS was updated in previous PRs but the doc was not updated accordingly.
Copy edit for precise language and comma use.
Copy edit for precise language and comma use.
Setting ""nsapi.dns-cache-size": 0" still left some of the DNS caching code in. Add crude #if to remove all of it. This allows one to save 429 bytes of flash and 48 bytes of RAM on ARMC5 builds.
1. Add USTICKER in device_has option of targets.json file. 2. Disable ticker interrupt in us_ticker_init 3. Add us_ticker_free 4. Enable interrupt in us_ticker_set_interrupt
1. Add LPTICKER in device_has option of targets.json file. 2. Disable ticker interrupt in lp_ticker_init 3. Add lp_ticker_free 4. Enable interrupt in lp_ticker_set_interrupt
This can happen with CLK_PowerDown() called first and then CLK_Idle() called.
Mark mbed-os-tests-mbed_hal-common_tickers/time_cpu_cycles not in-lined. Otherwise, time_cpu_cycles may be in-lined somewhere and takes different CPU cycles on invocation.
1. Introduce S/W interrupt enable/disable to reduce calls to TIMER_EnableInt/TIMER_DisableInt. 2. Allow dummy interrupt because clear interrupt flag is not synchronized. 3. Enable LPTICKER_DELAY_TICKS to make lp_ticker_set_interrupt non-blocking.
This is to make us_ticker/lp_ticker code consistent.
This is to make us_ticker/lp_ticker code consistent.
It is because dummy interrupt is very rare or pending time caused by it is very short.
This is to make us_ticker/lp_ticker code consistent.
Deprecated API thus no changes there
The test sometimes fails on NRF51_DK (test case: "Test: LowPowerTimer - time measurement 1 ms.") in morph tests. The test verifies if LowPowerTimer class correctly counts elapsed time. Sometimes we got measured ~1600 us for delay 1000 us (delta 550 us). The delay is performed using `wait_us()` function which for delays greater than or equal to 1 ms (our case) calls `Thread::wait((uint32_t)ms);`. This causes rescheduling and potentially can put board into sleep (deep sleep mode is disabled by `wait_us()`). For our test purposes we don't need rescheduling/sleep since this actions takes extra time and have influence on the time measurement accuracy. The solution is to implement function for delay which is based on busy loop and uses us ticker. It has been verified that this solves the problem. With this fix when measurement of 1 ms is repeated 1000 times we got usually measured time equal to ~1080 us, and sometimes ~1300us (checked that this is caused by systick interrupt handling). Since this is test for drivers layer and the results are acceptable I decided to not disabling systick in the test).
No files to build - should not be in targets Reverts part of the #6178
This is a remedy for the issue #7230. While the device is joining, LORAWAN_STATUS_CONNECT_IN_PROGRESS is returned. However, if the device is already joined, we will return LORAWAN_STATUS_ALREADY_CONNECTED.
API documentation is updated to clear how the connection related return codes will work from now on.
For ABP: First call to connect() or connect(params) will return LORAWAN_STATUS_OK
and a CONNECTED event will be sent. Any subsequent call will return
LORAWAN_STATUS_ALREADY_CONNECTED (posix EISCONN) and no event is generated.
FOR OTAA: First call to connect() or connect(params) will return LORAWAN_STATUS_CONNECT_IN_PROGRESS
and a CONNECTED event will be sent whenever the JoinAccept is received. If the application
calls connect again before receiving the CONNECTED event, LORAWAN_STATUS_BUSY will be returned.
After the CONNECTED event is dispatched, any subsequent call to connect() or connect(params) API
will be returned with LORWAN_STATUS_ALREADY_CONNECTED.
No new parameters are accepted after the first call. The application must disconnect before making
a connect() call with new parameters.
…eep-sleep. Serial buffer must be flushed before entering deep sleep mode. In the test this is done by the additional delay which is implemented on the busy loop which decrements given value down to 0 (`void wait_cycles(volatile unsigned int cycles)`). This solution is not appropriate since it is very target specific and the cycles value has been already increased few times. Additionally very big number of loop cycles which is suitable for fast targets may take much longer on slower boards and results in test timeout. It has been verified that 20ms is sufficient delay for the green-tea transmission. In this test we cannot simply use `wait_ms(20)` since this potentially may put board to sleep and wake up using lp ticker. The test re-initialzies the lp ticker(disables ticker interrupt) and this operation may break the schedule and time tracing by the upper layer. But we can use us ticker which is not affected by this test. The solution is to add a delay routine based on busy loop and us ticker only. This way are able to wait exactly 20 ms.
Code cleaning (L0 Cube update, comment precision)
This should allow custom targets to be transferred to each process when building in parallel
|
Updated branch afrer removing: #7277 (comment). |
|
/morph build |
Build : FAILUREBuild number : 2609 |
Build : SUCCESSBuild number : 2610 Triggering tests/morph test |
Test : SUCCESSBuild number : 2361 |
Exporter Build : SUCCESSBuild number : 2252 |
0xc0170
approved these changes
Jul 16, 2018
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.