forked from ARMmbed/mbed-os
-
-
Notifications
You must be signed in to change notification settings - Fork 20
STM32: allow HS USB endpoints and increase USB OTG_HS endpoints number #3
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
Closed
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
Scancode: Fix false positive reported by scancode output analyser script
- Alignment with other STM32 families - Subfamily level in targets.json
…x_testcase_update Summary of changes Remove WEP security Test Case with NULL as WEP security Key are sequence of Hex Values , the character "NULL" is (0x00) it is a valid value ( for ex: this is key index, followed by length and hex key array). Impact of changes Remove the test case for NULL( "" )key with NSAPI_SECURITY_WEP to test return value with NSAPI_ERROR_PARAMETER The set_credentials(const char *ssid, const char *pass, nsapi_security_t security) API has no key length, the key length is derived by using strlen(pass), which works if the pass ( is a string) , but in case of NSAPI_SECURITY_WEP and NSAPI_SECURITY_WPA2_ENT, the key does not happen to be string but a hex char array. WEP security Key are sequence of Hex Values , the character "NULL" is (0x00) it is a valid value ( for ex: this is key index, followed by length and hex key array). The key index 0 , 1, 2, 3 are keys used for an WiFi Access point.
…che_usage-master Enable Nanostack DNS cache usage
STM32G4 update drivers version to CUBE V1.3.0
SPDX are not yet done in our codebase. We suggest them to be present but 3rd party drivers have not yet been updated. The check as it was causes problems when updating 3rd party drivers (red flags in the PR). Proper fix will be to clean up SPDX id in the codebase.
…ndler BLE: Introduce ChainableEventHandler and subclasses
scancode: fix SPDX check - only warning
STM32L5 update drivers version to CUBE V1.3.1
Do not force red status for PRs due to SPDX missing (license must be there). We will add better SPDX checks later (more work required to enable these for 3rd party code).
…ing with an enum that covers all states
Separate cloud example configurations to another file
STM32WB update drivers version to CUBE V1.8.0
+ STM32Cube_FW_L0_V1.10.0 original files + targets.json update introducing subfamily level
The connection id starts at the value 1. The entry accessed in the array should be connId - 1
The connection starts at 1, not 0. The entry in the array should be connId - 1
STM32L0 update drivers version to CUBE V1.11.3
- startup files pdated from Cube - all SetSysClock aligned and checked - license header updated
Added the board so it can be used for testing the bare-metal profile on a Mbed 2 board
$<TARGET_FILE:${target}> is the output from CMake. As it can contain suffix for some toolchains, we can use ${target} instead (output from hex/bin generation).
Co-authored-by: Rajkumar Kanagaraj <[email protected]>
Issue https://gitlab.kitware.com/cmake/cmake/-/issues/21093 Until this is fixed, we should disable response files for ARMClang + ninja on Windows. Other toolchains and host systems should benefit from response files thus not disabling them completely. This fixes the issue with not finding includes. It's not trivial to find the root cause, it took me a while to figure out why ARMClang can't find the paths. I moved the check to Mbed OS main cmake. It should not be in the toolchain file as it is not related to the toolchain but to generator. We need toolchain properly set up first. Note, I had to protect setting CMAKE_NINJA_FORCE_RESPONSE_FILE. If I set it to 0, ninja would still use rsp files so I rather protected it and define that variable only when required, not always. Co-authored-by: Hugues Kamba <[email protected]>
Rename the CMake variable expected from applications from MBED_ROOT to MBED_PATH to be consistent with the naming used for the configuration file (MBED_CONFIG_PATH) also expected from applications.
As the assembler does not seem to recognise the request to the linker to use microlib, remove that instruction. Microlib is still used as the linker selects microlib as a result of being explicitly asked to do so.
…me depth and format as old mbed-CLI
The new function (mbed_set_cpu_core_definitions()) should always be called as it has defintions needed by Mbed OS to work with that particular MCU core. mbed_set_cpu_core_options() should only be called if a third-party toolchain file has not been used as it has compile options that can cause conflicts.
…put source file The compile defintions should always be added depending on the selected toolchain. mbed_set_toolchain_options() should only be called if a third-party toolchain file has not been used as it has compile options that can cause conflicts.
Compile defintions are always included. However, functions that set compile options are only called if a third party toolchain file is not used
Check if the selected application profile is supported by the selected Mbed Target
CMake: Add initial support
TEST: update cmake example on ble examples
38e7d11
to
f1ea281
Compare
Closing because ARMmbed#13816 has been merged |
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.
Summary of changes
This two commits can be squashed into one. The PR is independent from PORTENTA_H7 board so it can be mainlined before adding the new target
Impact of changes
Changes are enabled if :
MBED_CONF_TARGET_USB_SPEED == USE_USB_OTG_HS
Migration actions required
Documentation
Pull request type
Test results
Reviewers