New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release candidate for mbed-os-5.6.4 #5427
Conversation
The generic Flash support for L4 and L0 families is already there, but was not activated by default on 2 recentely added boards: DISCO_L475VG_IOT01A and DISCO_L072CZ_LRWAN1 This is done now.
HAL_RNG_GetRandomNumber is a deprecated API and replaced here with a call to HAL_RNG_GenerateRandomNumber. Doing so, we also rework the driver to use the 4 bytes returned by a call to HAL_RNG_GenerateRandomNumber instead of 1 byte out of 4. HAL_RNG_GenerateRandomNumber was not returning any error code, so now we can also check the return code.
There is only 1 RNG HW IP and we do not support more than one driver user at a time, so let's ensure this is the case and raise an error if needed.
Without this fix the tests-api-analogout test is fail with GCC_ARM.
Cleanup ICF file. No logic change. Signed-off-by: Tony Wu <tonywu@realtek.com>
Remove redundant memory regions, and merge multiple RAM regions into one to solve ielftool zero padding issue. The side effect is less control over object files placement. It's all up to linker's best effort. Signed-off-by: Tony Wu <tonywu@realtek.com>
This file is unused and redundant. Signed-off-by: Tony Wu <tonywu@realtek.com>
They fail right now, Cores are not checked
Fix for Issue #5279 Signed-off-by: Mahadevan Mahesh <Mahesh.Mahadevan@nxp.com>
Fix for Issue #5150 Signed-off-by: Mahadevan Mahesh <Mahesh.Mahadevan@nxp.com>
Was drivers, should be platform, wasn't updated during move
Switch to timer 2 for us_ticker for timer 6 might be used for power saving. Signed-off-by: Tony Wu <tonywu@realtek.com>
The blinky example compiles and runs. The board has a different eth phy component than mbed LPC1768. It requires a driver.
Target of LPC1769 links to mbed LPC1768. The PinNames.h has conditional compile for the pin names. LWIP lpc17xx emac driver modified to allow LPC1769 target
Add test for MemoryPool.
…. Placement of packed attribute was causing warnings due to following typedef
All the examples cloned from Mercurial should use the new os.mbed.com domain. Thus update corrects that. A new option has been added to the update.py script , -s which shows the status of any PRs raised against the examples that are tagged with the current release label.
…e size of the entire block device not the block size
The build system does not do this, so this is a consistency fix
HAL_MspInit/HAL_MspDeInit/HAL_PPP_MspInit/HAL_PPP_MspDeInit weak functions can now be overwritten as it is expected
Variable length flag was lost during attribute settings, so variable length GATT attributes should have been set to the predefined maximum length. This fixes issue #86. Change-Id: Ia0cd236ecd903fdb9e62a21bffef57d1e63764b9
Ensure both the stack and stack size used in the Thread class are aligned to 8 bytes. This prevents the runtime error "Thread 0 error -11: Unknown" due to incorrect stack alignment.
Provide detailled description of the purpose, general concepts and usage.
Make minor copy edits.
On STM32 F767 rev A devices ,Ethernet peripheral had problems on RMII interface, on MII this was not the case. This commits implements a tentative workaround for the issue rerfered to as Ethernet erroneous data received in RMII configuration in the Errata sheet below: http://www.st.com/content/ccc/resource/technical/document/errata_sheet/group0/23/a6/11/0b/30/24/46/a5/DM00257543/files/DM00257543.pdf/jcr:content/translations/en.DM00257543.pdf Note that the issue has been fixed in 'Z' revision. of STM32 F767 MCUs.
In preparation to exporter tests
/morph test-nightly |
/morph mbed2-release |
/morph export-build |
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!
|
@studavekar Can you look at the failure above please? |
/morph build |
Result: FAILUREYour command has finished executing! Here's what you wrote!
|
@0xc0170 latest version of few jenkins plugin were not compatible with older version of Jenkins, updated Jenkins to right version. |
Build : SUCCESSBuild number : 420 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 73 |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Test : SUCCESSBuild number : 211 |
No description provided.