Release candidate for mbed-os-5.3.2 #3510
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
just change the place of code to have i2c_read and i2c_write together
Some device drivers use a data lenght of 0 to check if device is ready. STM32 HAL provides a dedicated service for that, so let's use it.
In case the user applicaiton makes a mixed usage of unitary function (start, stop, byte write & read) with SYNC operation (write and read of data buffers with start and stop management), we need to reset the STM32 HAL state as it is by-passed by a direct call to STOP
In continuation of previous IsDeviceReady case, let's add 1 in case length is 0 (even though not recommended)
- GPIO: mode was not allowed by ST HAL API - PIN map: assert has highlighted an issue for pullup/pulldown setting - RTC: year after 2000 was not taken into account
- GPIO: mode was not allowed by ST HAL API
- CAN: compilation issue with assert enabled - GPIO: mode was not allowed by ST HAL API
During open, the socket checked the internal stack variable, assuming it would alway be null on a socket not connected to the network. However, when a socket is closed, the stack variable was not updated, causing the socket to incorrectly return a parameter error if reopened. The simple fix was to set the stack to null on close. A non-null stack is a predicate for a non-null socket variable, so no additional checks are needed in socket functions.
- ll_utils: compilation issue - GPIO: mode was not allowed by ST HAL API
Change test slave address to 0x80 because 0x90 is used by a real slave (temperature sensor) on few boards like the CI shield.
This is a partial update of HAL drivers, especially for I2C driver update
Applying the same fix as in L1 and F4. This is an alignement to F4 HAL as the same IP is used.
Now that F1 HAL has been updated to support required APIs, the F1 family can also be moved to common code.
If an example's GitHub repository contains multiple child examples, the script was incorrectly filtering out all the child examples when compiling and exporting. This patch now handles this case correctly.
Signed-off-by: Mahadevan Mahesh <[email protected]>
Delete page because an exact duplicate exists in the Handbook
Delete page because an exact duplicate exists in the Handbook
Delete page because duplicate exists in Handbook
Delete page because duplicate exists in Handbook
Delete page because an exact duplicate exists in the Handbook
…RX interface is used.
I modified the TTB setting of RO_DATA area. The current setting of this area is "not executable". Therefore, when trying to execute a program placed in this area, a prefetch abort will occur. So I changed from "Sect_Normal_RO" to "Sect_Normal_Cod".
Previously, the RTOS threads test was conditionally change the thread stack size for all test cases based on the target. Now, it uses the default stack size for all targets when threads are created serially, and uses a 512 byte stack for the threads that are created in parallel.
It was possible to remove an entire project if clean was specified on the command line. That's a Bad Thing(tm).
Duplicate page exists in Handbook
Exact duplicate of page exists in Handbook
This change was spurred by a confusing error. I attempted to compile for the RZ_A1H (a Cortex-A device), and I had the standalone ARM compiler in my system path, which supports Cortex-A. However, the default path for the ARM compiler in settings.py uses a Keil installation, which only supports Cortex-M. It found my Keil installation and used that instead. This change proposes to remove this default behavior and instead requires the user to explicitly set the intended compiler, either by a settings file, mbed CLI, environment variables, or by placing the compiler in your PATH.
…h header file comment
…DMA descriptors if they are located in SRAM1 and SRAM2
Delete this page because an exact duplicate exists in the Handbook
Thread spawning constructors are deprecated, start function should be used instead.
Signed-off-by: Mahadevan Mahesh <[email protected]>
1. Add targets into build_travis.py and tests.py. 2. Add target SPI pins into SPI SD test samples. 3. Rename target TOOLCHAIN_GCC_ARM/retarget.c to avoid name collision of compiled retarget.o with platform/retargets.cpp.
Use MBED_CONF_RTOS_PRESENT to filter out mbedtls alternative for mbed OS 2.
… NXP Signed-off-by: Mahadevan Mahesh <[email protected]>
|
/morph test-nightly |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
continuous-integration/jenkins/branch and continuous-integration/jenkins/pr-head both appear to have hung (either that or there is a large queue at which this is the back)! mbed-os 2 release testing will be kicked off again as the first run contained a huge number of timeouts, which indicate we may have some board problems in the ci. |
|
@VeliMattiLahtela @marhil01 CI fails with a git error, seems to me to be config related? Can you help us? |
Resolved |
|
+1 |
|
Mbed-os 2 results are on a par with the previous release so this candidate looks good to me. |
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.