-
Notifications
You must be signed in to change notification settings - Fork 3k
Add support for target MTB_ADV_WISE_1530. #6423
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
Can you please share tests (all compilers) ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one nit
GPIO2 = PB_1, | ||
GPIO7 = PB_14, | ||
|
||
I2S_CK = PB_12, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
misligned lines until 190?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest to remove USI MTB define from this PR as there are 2 separate targets and the USI needs separate pin defines.
Could you please address other comments. Thanks.
targets/targets.json
Outdated
"device_name": "STM32F412RG" | ||
}, | ||
"MTB_USI_WM_BN_BM_22": { | ||
"inherits": ["MTB_ADV_WISE_1530"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Derivative target must not inherit from another target. It should inherit from parent MCU..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will remove usi from here. There will be a lot of duplicate definitions, since the wise-1530 and USI targets are basicly the same targets. According the hw specification the wise-1530 includes usi chip. Only the tx&rx pins are diffrent with these 2 targets
D13 = PA_5, | ||
D14 = PB_9, | ||
D15 = PB_8, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove all Arduino pin defines. There are no Arduino connectors on the module.
LED_RED = GPIO0, | ||
LED1 = LED_RED, | ||
LED2 = LED_RED, | ||
USER_BUTTON = GPIO2, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use standard button names.
LED2 = LED_RED, | ||
USER_BUTTON = GPIO2, | ||
// Not connected | ||
NC = (int)0xFFFFFFFF |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All pins from the module must be defined. Even the non-connected ones. You may want to move the NC to the top for this.
@@ -100,7 +100,8 @@ | |||
defined(TARGET_STM32F439ZI)) | |||
#define INITIAL_SP (0x20030000UL) | |||
|
|||
#elif defined(TARGET_STM32F412ZG) | |||
#elif (defined(TARGET_STM32F412ZG) ||\ | |||
defined(TARGET_STM32F412RG)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ARMmbed/team-st-mcd Thoughts on the above question?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, The SRAM memory is the same between F412ZG and F412RG. This is the reason why the stack pointer must be initialized at the same address for both Targets.
Please leave this line.
Kind regards
Any update? |
Sw has been build with Jenkins job: Test's are running at the moment. Will link the results, once the test are done. |
@0xc0170 What test results are required? |
test case results: 4 FAIL / 14 SKIPPED / 461 OK / 2 ERROR Failing ones: | MTB_ADV_WISE_1530-GCC_ARM | MTB_ADV_WISE_1530 | mbed-os-tests-mbed_hal-lp_ticker | TIMEOUT | 47.5 | default | Test results log-file also attached |
"inherits": ["FAMILY_STM32"], | ||
"core": "Cortex-M4F", | ||
"extra_labels_add": ["STM32F4", "STM32F412xG", "STM32F412RG", "CORDIO"], | ||
"device_has_add": ["CAN", "LOWPOWERTIMER", "SERIAL_ASYNCH", "SERIAL_FC", "TRNG", "FLASH"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
line 1141 and 1153 are overwritten each other both with label device_has_add
@ashok-rao Has this been reported? |
Please rebase to resolve the conflict. If we can report those issues that HAL implementation for a parent has? |
Description
Add support for MTB_ADV_WISE_1530 and MTB_USI_WM_BN_BM_22 targets
Pull request type