-
Notifications
You must be signed in to change notification settings - Fork 3k
Release candidate for mbed-os-5.5.1 #4596
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
Conversation
…ic file Signed-off-by: Mahadevan Mahesh <[email protected]>
- Creates new target in targets.json - Creates device specific files under ARM_SSG/CM3DS_MPS2 directory - Driver layer files under CM3DS_MPS2 are based on Beid target - Device specific files under CM3DS_MPS2/device are based on CMSIS_5 and Beetle Change-Id: I29ea7a7f42b11cf25b516cce4b9255ab828ca019 Signed-off-by: Tamas Kaman <[email protected]> Signed-off-by: Marc Moreno <[email protected]>
Based on lwip_ethernetif.c skeleton file, use init, receive and transfer functionality of SMSC9220 Ethernet driver for the lightweight IP stack. Receive mechanism is interrupt driven. HW buffer sizes: Tx = 4608 bytes (MTU) Rx = 10560 bytes lwIP fine tuning: mbed-os/features/FEATURE_LWIP/lwip-interface/lwip/src/include/lwip/opt.h Change-Id: I0ea95650c65fb32cafb5c2d3dde11420c61dba66 Signed-off-by: Gabor Kertesz <[email protected]>
Refactor SMSC9220 Ethernet controller driver Change-Id: I75c3c42d5675441de1292100a54c50d990070c6f Signed-off-by: Gabor Kertesz <[email protected]>
- Modify CMSDK_CM3DS.h: add register interface - Modify targets.json: add RTC as available device to CM3DS - Create rtc_api.c: implement mandatory API functions Change-Id: I14bc1074a9ac0d5e4cbada46d3c90ca82c1e28b0 Signed-off-by: Tamas Ban <[email protected]>
1. Add startup code and linker script for IAR and GCC_ARM compilers. 2. Enable IAR and GCC_ARM compilers in targets.json. Change-Id: I742a89ae73a4e5ede980a8af0821c3f0e5a461ef Signed-off-by: Mate Toth-Pal <[email protected]>
Note that this could have side effects on the application as it would not be aware that data has been missed. This may be later solved by adding an error management parameter to the Serial API in mbed. The advantage is that the serial link can work again.
At some point the "mount" parameter for "f_mount" was name "force". This led to a bit of confusion that ended with the default mount function never calling block device init. This is fine, since the block device can be manually initialized, but a better user experience is where the filesystem initializes the block device for the user. This is backwards compatible due to the repeatability of the block device init functions.
Note: Reporting of reserved stack is already performed by the thread layer
Following Merge pull request #4063 from LMESTM/17q2_L4_bootloader the NUCLEO_L476RG binairies could not boot anymore. The change done in #4063 was derived from work on NUCLEO_L429ZI target which supports uvisor. The VECTORS defintiion is introduced as part of uvisor support and requires further changes in ld file which were missing. As uvisor is not considered yet, we remove VECTORS for now and will introduce only when needed.
MBED_APP_SIZE was erroneously defined to 2MB for this target, while it's only 1MB.
Bump the background stack size to 512 bytes to fix stack overflows on the NRF52 and so it is the same size as it was before the switch to RTX5.
The stack required for the idle thread is highly dependent on the target because it will call the sleep function which is target specific. While 256 bytes of stack is enough for most targets, others like the NRF52840 might require more. With this change, target maintainers can specify the idle thread stack size in their mbed_rtx.h file.
A stack size of 256 bytes is not enough on the NRF52840, this patch changes it to a size of 512 bytes.
…A/ in TARGET_STM32L475xG/ - Add STM32L475xG extra label in targets.json
…ace drivers. This change allows the u-blox C027 and C030 boards to use both the mbed-os OnboardCellular modem driver and the u-blox cellular interface drivers (which support both PPP and AT data modes).
/morph test-nightly |
/morph mbed2-release |
/morph export-build |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
Result: FAILUREYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 69 Exporter Build failed! |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputTest failed! |
/morph export-build |
/morph test-nightly |
/morph mbed2-release |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 71 All exports and builds passed! |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
|
No description provided.