Release candidate for mbed-os-5.7.5 #6057
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
…nd tests.py I added GR-LYCHEE's configuration in targets.json file. Also, I added GR_LYCHEE as a Renesas new target board in build_travis.py and tests.py.
I added GR_LYCHEE as a new target board in DS-5, e2studio and IAR export.
For supporting to CMSIS5/RTX5, I added the start-up processing of 3 toolchains (ARMCC, GCC_ARM, IAR) and the register definition of RZ/A1LU specific. In addition, I added the linker script files to implement the dynamic HEAP the same as GR-PEACH(RZ/A1H).
In mbed_rtx.h file, I added the definition for GR-LYCHEE to use the "Dynamic Heap" processing when the target is GR_LYCHEE.
I supported the TRNG function when target is GR-LYCHEE. GR-LYCHEE generates TRNG by acquiring the random number of Wifi module(ESP32) incorporated in it using I2C.
I modified the lack of license header in the below header files. - targets/TARGET_RENESAS/TARGET_RZ_A1XX/TARGET_RZ_A1H/TARGET_MBED_MBRZA1H/reserved_pins.h - targets/TARGET_RENESAS/TARGET_RZ_A1XX/TARGET_GR_LYCHEE/TARGET_MBED_MBRZA1LU/reserved_pins.h
Regarding "{" that show the function start, I modified the the arrangement from right of function to new line.
To get cmsis nvic definitions, I added the process that include "cmsis_nvic.h" in cmsis.h. Relation PR is #5890.
#5795 patches are missing for these 2 targets STDIO_UART_TX and STDIO_UART_RX can be now user defined
Documentation states that nsapi_dns_query_multiple returns the number of addresses found on success - it was returning 0. Overloads using SocketAddress are relying on the return value, meaning those calls didn't work at all. Fixes #5921.
Looks like this:
Building project mbed-os-prettyoutput (ARCH_PRO, GCC_ARM)
Scan: .
Scan: env
Scan: mbed
Scan: FEATURE_LWIP
Text 70.5KB Data 2.72KB BSS 7.43KB ROM 73.2KB RAM 10.1KB
ROM [||||||| ] 73.2KB/512KB
RAM [|||||||||||||||| ] 10.1KB/32KB
Image: BUILD/ARCH_PRO/GCC_ARM/mbed-os-prettyoutput.bin
If you build a target without a cmsis-pack it looks like this:
Building project mbed-os-prettyoutput (ARM_BEETLE_SOC, GCC_ARM)
Scan: .
Scan: env
Scan: mbed
Scan: FEATURE_BLE
Text 99KB Data 2.84KB BSS 13KB ROM 102KB RAM 15.8KB
Image: BUILD/ARM_BEETLE_SOC/GCC_ARM/mbed-os-prettyoutput.bin
And the old behaviour of displaying the memap table can be brought back
by passing the --stats-depth parameter
…d-in function zip()
To enable/disable UART Clock in Stop Mode
Modify arm_pack_manager to look for new keys in pdsc files, because some vendors have changed their format
Aligns application start address to sector boundary Aligns application end address to sector boundary
Use ceiling for bootloader end address Use floor for application size
Correct spacing.
This allow custom overwrites
Related to the review of #5857, I fixed the TRNG function for GR-LYCHEE. - I modified to zeroize "recv_data" before the function return. - I added the processing that check the return value of I2C.read function. If return value is error, "output" is zeroized before function return. - In trng_get_bytes_esp32 function, there is a time lag in the period from ESP32 reset to start working, error may occur when "Write" is called. Thus, I added a retry counter due to address this concern. There is not this counter for "Read" since it is called after "Write".
GCC_ARM throws warning if both architecture and core are set (though correct). If CPU option is set correctly, architecture is set by compiler itself.
This commit fixes ticker cross-schedule bug in test_case_2x_callbacks subtest
In effect of this bug:
ticker_callback_1_switch_to_2 was called only once
ticker2 was never been fired because it was repeatedly detached just before fire and attached again
test_case_2x_callbacks test was redesigned to eliminate ticker rescheduling and improve time mesure accuracy. Constant ticker rescheduling (detach()/attach_us() calls) was causing the gap between consecutive callback calls was not exact 1ms but 1ms + time needed to call the callback and attach new one. New design just uses two tickers to update counter alternatively every 1ms without rescheduling them
Cortex-M23 doesn't support ARMv8-M Main Extension and so doesn't support:
ldm r0, {r0, r1, r2, pc}
Fix it by going Cortex-M0/M0+ way:
ldm r0, {r0, r1, r2, r3}
bx r3
A call to
`TCPSocket::recv(void *data, nsapi_size_t size)`
returns, following the mbed documentation, the number of received bytes on
success, and a negative error code on failure.
So in case of success, the return value depends on both the value of parameter
`size` but also on the amount of data already available. This means, that the
value returned can be lower than or equal to the `size` of the `data` buffer
passed as argument to the call.
Therefore, in the cases of `test_tcp_hello_world()` & `find_substring()`
(i.e. test `socket_sigio`), the calls to `TCPSocket::recv()` might return from
one byte up to `sizeof(buffer) - 1` (i.e. 511) bytes for each single call,
while the tests expect to receive the whole response string with a single call.
This commit applies a fix to this situation by implementing a receive loop
which exits once there is no data anymore available to be read from the socket.
|
/morph build |
Build : SUCCESSBuild number : 1106 Triggering tests/morph test |
Exporter Build : FAILUREBuild number : 784 |
Test : FAILUREBuild number : 914 |
|
/morph test |
Test : FAILUREBuild number : 915 |
Exporter Build : SUCCESSBuild number : 786 |
|
/morph test |
This reverts commit b812918.
|
/morph build |
Build : SUCCESSBuild number : 1115 Triggering tests/morph test |
Test : FAILUREBuild number : 919 |
Exporter Build : SUCCESSBuild number : 793 |
Test : SUCCESSBuild number : 922 |
|
/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.