Release candidate for mbed-os-5.7.4 (take three) #5954
Merged
Conversation
This file contains 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
cmonr
force-pushed
the
release-candidate
branch
from
b379de1
to
fd07de4
Compare
The current 0.1% clock tolerance is too small for certain platforms which natural variance is larger than this. This commit increases the tolerance to 0.5% instead. Sample output from time_cpu_cycles called repeatedly in init, before running any flash tests: [1515706585.63][CONN][RXD] diff: 49316 [1515706585.69][CONN][RXD] diff: 49256 [1515706585.75][CONN][RXD] diff: 49286 [1515706585.81][CONN][RXD] diff: 49256 [1515706585.87][CONN][RXD] diff: 49225 [1515706585.94][CONN][RXD] diff: 49286 [1515706585.99][CONN][RXD] diff: 49317 [1515706586.06][CONN][RXD] diff: 49255 [1515706586.12][CONN][RXD] diff: 49286 [1515706586.18][CONN][RXD] diff: 49285 [1515706586.24][CONN][RXD] diff: 49286 [1515706586.31][CONN][RXD] diff: 49347 [1515706586.36][CONN][RXD] diff: 49347 [1515706586.43][CONN][RXD] diff: 49286 [1515706586.49][CONN][RXD] diff: 49286 [1515706586.55][CONN][RXD] diff: 49256 [1515706586.61][CONN][RXD] diff: 49286 [1515706586.68][CONN][RXD] diff: 49346 [1515706586.74][CONN][RXD] diff: 49347 [1515706586.80][CONN][RXD] diff: 49256 Notice the outliers will cause intermittent CI failures.
FATFilesystem declares sector count and size as uint32_t and block device class arguments are addr and size which is uint64_t While passing arguments to program/read/write API's of block device, multiplication of uint32_t*uint32_t was not typecasted properly to uint64_t which resulted in MSB truncation. Eg. If block 0x800000 is accessed with block size 0x200, addr to be passed (0x800000*0x200)0x100000000, but actual address passed was 0x0 which resulted in over-writting the root directory, and hence corrupted filesystem
- clock source is now a user choice - IAR tool chain is available
Copy edit docs changes for active voice.
Copy edit file for active voice and agreement.
Copy edit file for active voice and American English.
Copy edit file for active voice.
Copy edit file for active voice.
Copy edit file for active voice.
Copy edit file for active voice.
Copy edit file for active voice.
Copy edit file for active voice.
STM32L0, L4, F7 and few F4 chip are supporting LPTIM feature. We propose to allow user to use LPTIM for MBED LowPowerTimer API instead of using RTC wakeup timers. By default, all targets that are supporting this feature have been configured.
All documentation is now in Handbook
The C++ "operator new" and "operator delete" (and their array variants) were logging the the caller address wrong. In practice if one used "operator new", the logged caller address pointed to mbed_retarget.cpp, not to the client. Fix this by exposing the alloc wrappers to the the retarget. Note: this fixes only the ARMCC variants, as the GCC ones have different different API and implementation.
Fix the caller address logging on the GCC compilation too. Previously the code logged the caller address as C++ wrapper, not the actual caller of the C++ operator new or delete.
Allow custom targets to override the DCDC settings by defining EMU_DCDCINIT_STK_DEFAULT to target-specific initialization values.
deepikabhavnani did the hard work in tracking this issue down. Block addresses are not cast to the correct type until after multiplying to convert to byte addresses. This results in an overflow when the storage is larger than 4 GB.
This commit fixes #5840. Fix verified by running mbed_hal-lp_ticker test suite with preloaded RTC counter such that it wrapped in the middle of the suite. Also removes explicit sleep blocking from the us_ticker implementation, since sleep blocking for us tickers is done at mbed HAL level now. This was causing one of the lp_ticker tests to fail.
- STDIO_UART define is no more used - configuring a new serial with the same UART as STDIO is no more allowed
restructure target files to better sync with Ameba sdk base
In the below "features/FEATURE_LWIP" folders, same as Cortex-M targets, I changed the folder structure to combine files that can be shared as RZ/A1 related. And I renamed the folder name to "TARGET_RZ_A1XX" in order to make commonality explicit. - "features/FEATURE_LWIP" folder <before> \features\FEATURE_LWIP\lwip-interface\lwip-eth\arch\TARGET_RZ_A1H \features\FEATURE_LWIP\lwip-interface\lwip-eth\arch\TARGET_VK_RZ_A1H <after> \features\FEATURE_LWIP\lwip-interface\lwip-eth\arch\TARGET_RZ_A1XX
In "targets/TARGET_RENESAS" folders, same as Cortex-M targets, I changed the folder structure to combine files that can be shared as RZ/A1 related. And I renamed the folder name to "TARGET_RZ_A1XX" in order to make commonality explicit. - "targets/TARGET_RENESAS" folder <before> \targets\TARGET_RENESAS\TARGET_RZ_A1H \targets\TARGET_RENESAS\TARGET_VK_RZ_A1H <after> \targets\TARGET_RENESAS\TARGET_RZ_A1XX
…ctory I made be available in common whatever the board related to RZ_A1 in the below files. - Since there are the table code of Pinmap differs for each board, I moved the code to "PeripheralPins" file for each board, and changed to include PeripheralPins.h. analogin_api.c, can_api.c, gpio_irq_api.c, i2c_api.c, pinmap.c, port_api.c, pwmout_api.c, serial_api.c, spi_api.c and us_ticker.c - Since there are some board-specific processes, I enclosed the processes with "#ifdef" and rearranged the functions to make be easier to enclose. can_api.c, ethernet_api.c and serial_api.c - Since there are the driver configuration values differs for each board, I added "mbed_drv_cfg.h" file for each board and defined macros for the values, and changed to refer to the macros. can_api.c, gpio_api.c, pwmout_api.c and rtc_api.c
As a result of revision of folder structure, I changed the values of "extra_labels" of RZ_A1-related in targets.json.
For LWIP communication speedup in RZ_A1 related, I changed the below macro value and added the definition processing in RZ/A1 related header file(lwipopts_conf.h). For this reason, those macros are overrode by RZ/A1 related values, not default values.
I modified the debug message when using LWIP in RZ/A1 related mbed boards. In eth_arch_enetif_init(), sys_thread_new() was called and task name is appeared as debug information, but task name for debug was a mistake.
I added the function declarations of Ethernet functions that have a WEAK attribute. Although several Ethernet functions was called in rza1_emac.c, GR-LYCHEE don't have Ethernert feature. But there may be case that GR-LYCHEE uses LWIP feature. In this case, since GR-LYCHEE will occur the build error, I addressed the error by defining the functions with a WEAK attribute. For reason of WEAK attribute, there is no influence in GR-PEACH and VK_RZ_A1H that have Ethernet feature.
I modified the lack of copyright in the below header files that I added for commonizing the RZ_A1 related files. - targets/TARGET_RENESAS/TARGET_RZ_A1XX/TARGET_RZ_A1H/mbed_drv_cfg.h - targets/TARGET_RENESAS/TARGET_RZ_A1XX/TARGET_VK_RZ_A1H/mbed_drv_cfg.h
I added the "RZ_A1XX" label for commonizing the setting in targets.json, and inherited in both RZ_A1H and VK_RZ_A1H.
|
/morph build |
Build : SUCCESSBuild number : 984 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 675 |
Test : SUCCESSBuild number : 805 |
|
/morph mbed2-release |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
|
/morph mbed2-release |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
|
+1 |
|
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
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.