Release candidate for mbed-os-5.7.6 #6195
Closed
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
Renesas mbed boards incorporate NVIC Wrapper because Cortex-A9 use GIC. For example, NVIC_SystemReset() is defined in nvic_wrapper.c and declared in nvic_wrapper.h. Because I removed one of include processing accidentally, I fixed the lack. This supplements PR #5890.
…eSystem::dir_seek()
Regression after ChanFS update: Due to parameter changes in the f_mkfs function, the option to use a separate block for MBR (FDISK) was turned back on. This should be off as it conflicts with an explicit MBR when using the MBRBlockDevice.
The introduction of pretty-bar had broken the handling of "mbed compile"'s "--stats-depth" argument. No matter what one gave as parameter to it, the result output is just using the default 2. Fix the logic in build_api.
Fix Details: HAL API for loguart is different that UART. Initially we didnt have support for loguart in the mbed api. These changes have been made to support the loguart from the mbed api by using the correct HAL api calls
As mut['mcu'] can be "None" on unknown targets, the detect_targets script crashes when one of these boards is connected. This happens when "mbed-cli detect -vv" is ran when a STEVAL-3DP001V1 board is connected. Which does not provide a html file with a target_id, and thus cannot be looked up in the mbedls platform database. http://www.st.com/en/evaluation-tools/steval-3dp001v1.html
When ticker is not driven by the 1 MHz clock and HAL driver need to perform conversion between microseconds and ticks, then the interrupt might be scheduled in the past. For details see: #6054. This patch provides fix for such case. Interrupt is fired immidiatelly when last read tick is equal to the calculated tick when interrupt should be generated.
Cortex v8 architecture based devices support secure/non-secure builds. Secure build should generate the object file/library from elf during link process which is used by non-secure binary during linking. --out-implib=file specifies output library in which symbols are exported --cmse-implib requests libraries mentioned above are secure gateway libraries Creation of secure library is done as part of linking process in GCC/ARMC6/IAR Non-Secure project should add this secure object file as part of the linking process. Secure library is named as cmse_lib.o.
RTX5: Added TrustZone Module Identifier configuration for Idle and Timer Thread
Default value for timer/idle thread trustzone identifier is 0, updated it to 1 to allow threads to access secure functions when timer is secure device.
CMSIS repo does not support pre-processor defines, hence multiple assembly files are added for secure/non-secure and floating point tools. Mbed OS tools support assembly file pre-processing, but the build system does not support multiple assembly files for each target, hence updating the assembly files.
Systick handler switch to secure/nonsecure issues addressed: 1. Switch to secure/nonsecure context save/restore is based on 6th bit in LR register, correct the bug (R7 instead of LR was used for decision) 2. Prevent R7 from being corrupted in Sys_ContextSave 3. Branch when non-secure rather than secure
MbedTLS doesn't support point multiplication for MBEDTLS_ECP_INTERNAL_ALT acceleration configuration.
wiki page https://os.mbed.com/teams/ST/wiki/STDIO updated
Delta calculation from lp_ticker_set_interrupt() function: delta_us = timestamp > now_us ? timestamp - now_us : (uint32_t)((uint64_t)timestamp + 0xFFFFFFFF - now_us); Lets assume that timestam == now_us. Expected delta value should be 0 and in this current version is 0xFFFFFFFF. The following condition: timestamp > now_us should have the following form: timestamp >= now_us Additionally modified us ticker driver to provide the same logic.
Rather than tracking all in-flight blocks blocks during a lookahead, littlefs uses an ack scheme to mark the first allocated block that hasn't reached the disk yet. littlefs assumes all blocks since the last ack are bad or in-flight, and uses this to know when it's out of storage. However, these unacked allocations were still being populated in the lookahead buffer. If the whole block device fits in the lookahead buffer, _and_ littlefs managed to scan around the whole storage while an unacked block was still in-flight, it would assume the block was free and misallocate it. The fix is to only fill the lookahead buffer up to the last ack. The internal free structure was restructured to simplify the runtime calculation of lookahead size.
How you write and ersae the flash on the NRF52 changes depending on whether the SoftDevice is enabled or not. This change does a runtime check before erasing and writing, and then chooses the correct function to perform the action.
IPv6 header requires 20 more bytes compared to IPv4 header.
The test case is executed succesfully when usage of wrong channel is detected
New version of the PR template. Ideal PR should contain: - detailed description of changes - how it was tested - dependencies - PR type (one of)
Current behaviour ends up undefined when the constructor leaves early. Now FilePath just discards leading slashes and otherwise asserts if the path is bad.
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>
…for irq (or output)
sleep_manager_racecondition test fix for devices with low CPU clock This RP contains fix for sleep_manager_racecondition test for very slow devices (like NRF51). It fixes the test itself as well as side effects of fix introduced in #5046 (us ticker: fix fire interrupt handling) The idea of the test was to test race condition between main thread and interrupt handler calling the same function. To efficiently test this, each handler call should interrupt main thread to make race more likely. On very slow devices (like NRF51) when we set very low ticker period (e.g less then 1000us for NRF51) there is no much time for thread scheduling. On such slow devices, setting period to 500 us cause that main thread is scheduled very rarely and only handler is constantly called making test unreliable. Fix introduced in #5046 (us ticker: fix fire interrupt handling) changed fire_interrupt function implementation causing more interrupt tailing thus even less time for main thread scheduling. After introduction of #5046 (us ticker: fix fire interrupt handling) when running sleep_manager_racecondition test on NRF51 (with ticker1.attach_us(&sleep_manager_locking_irq_test, 500);) test is failing with timeout due to the fact that interrupt handler is constantly called and main thread is never scheduled.
|
/morph build |
|
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Build : SUCCESSBuild number : 1238 Triggering tests/morph test |
Test : SUCCESSBuild number : 1038 |
Exporter Build : SUCCESSBuild number : 905 |
|
An issue with Travis CI builds was found involving a PR that should have failed. Removing said PR and regenerating 5.7.6 release PR. |
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.