Support STM Nucleo-G431RB #14259

rotu · 2021-02-09T21:10:02Z

Summary of changes

Support the STM Nucleo-G431RB board

Impact of changes

Migration actions required

Documentation

Support the STM Nucleo-G431RB board

Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[X] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

ciarmcom · 2021-02-09T21:30:25Z

@rotu, thank you for your changes.
@ARMmbed/team-st-mcd @ARMmbed/mbed-os-maintainers please review.

rotu · 2021-02-10T00:01:04Z

I'm not sure that the clock setup is correct. The debugger seems to drop out when calling ThisThread::sleep_for(...) but I have no idea how to troubleshoot/fix this.

LMESTM · 2021-02-10T07:51:50Z

I'm not sure that the clock setup is correct. The debugger seems to drop out when calling ThisThread::sleep_for(...) but I have no idea how to troubleshoot/fix this.

@rotu thanks for your contribution.
You may give a try to calls like below and let us know if that helps maintaining the debugger running.
https://github.com/ARMmbed/mbed-os/blob/master/connectivity/drivers/ble/FEATURE_BLE/TARGET_STM32WB/HCIDriver.cpp#L876

0xc0170 · 2021-02-10T10:08:07Z

@rotu I assume testing fails as well, so no test results available at the moment. Once you fix, please attach the logs to the pull request.

jeromecoutant

It seems correct.
About you debug issue, did you work on top on 6.6.0 release ?
(because there was an issue, go with 6.7.0)

targets/targets.json

rotu · 2021-02-10T19:07:33Z

@LMESTM

I'm not sure that the clock setup is correct. The debugger seems to drop out when calling ThisThread::sleep_for(...) but I have no idea how to troubleshoot/fix this.

@rotu thanks for your contribution.
You may give a try to calls like below and let us know if that helps maintaining the debugger running.
https://github.com/ARMmbed/mbed-os/blob/master/connectivity/drivers/ble/FEATURE_BLE/TARGET_STM32WB/HCIDriver.cpp#L876

I was under the impression that calling ThisThread::sleep_for as in the blinky example should not trigger hardware sleep as per docs. Where do you propose I put that code?

rotu · 2021-02-10T19:55:31Z

@rotu I assume testing fails as well, so no test results available at the moment. Once you fix, please attach the logs to the pull request.

@0xc0170

I don't know how to run tests canonically.

The output of mbed test -m NUCLEO_G431RB contains a lot of failures like below. I don't know which ones are of concern

Building library mbed-build (NUCLEO_G431RB, ARMC6)
Scan: mbed-motor-control
Building project stress-net-fs (NUCLEO_G431RB, ARMC6)
Scan: ARM
Scan: stress-net-fs
Scan: COMMON
Compile [100.0%]: main.cpp
[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target
Building project net-single (NUCLEO_G431RB, ARMC6)
Scan: ARM
Scan: net-single
Scan: COMMON
Compile [100.0%]: main.cpp
[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target
Building project fs-single (NUCLEO_G431RB, ARMC6)
Scan: ARM
Scan: fs-single
Scan: COMMON
Compile [100.0%]: main.cpp
[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target
Building project sleep_lock (NUCLEO_G431RB, ARMC6)
Scan: ARM
Scan: sleep_lock
Link: sleep_lock
[Warning] @0,0: L3912W: Option 'legacyalign' is deprecated.
[Error] @0,0: L6200E: Symbol __ARM_use_no_argv multiply defined (by BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/main.o and BUILD/tests/NUCLEO_G431RB/ARM/main.o).
[Error] @0,0: L6200E: Symbol main multiply defined (by BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/main.o and BUILD/tests/NUCLEO_G431RB/ARM/main.o).
Warning: L3912W: Option 'legacyalign' is deprecated.
Error: L6200E: Symbol __ARM_use_no_argv multiply defined (by BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/main.o and BUILD/tests/NUCLEO_G431RB/ARM/main.o).
Error: L6200E: Symbol main multiply defined (by BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/main.o and BUILD/tests/NUCLEO_G431RB/ARM/main.o).
Not enough information to list the image map.
Finished: 1 information, 1 warning and 2 error messages.
Building project net-threaded (NUCLEO_G431RB, ARMC6)

mergify · 2021-02-11T08:03:38Z

This PR cannot be merged due to conflicts. Please rebase to resolve them.

ciarmcom · 2021-02-22T08:50:40Z

This pull request has automatically been marked as stale because it has had no recent activity. @rotu, please carry out any necessary work to get the changes merged. Thank you for your contributions.

jeromecoutant

First tests done => all OK

Need to redo CMakeLists files with the new rules.

targets/targets.json

jeromecoutant · 2021-02-24T16:57:15Z

The output of mbed test -m NUCLEO_G431RB contains a lot of failures like below. I don't know which ones are of concern

This is the correct command.
Failures you reported are "normal" as they are [NOT_SUPPORTED] tests

[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target
[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target
[Error] main.cpp@25,2: [NOT_SUPPORTED] integration tests not enabled for this target

This error :

[Error] @0,0: L6200E: Symbol __ARM_use_no_argv multiply defined (by BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/main.o and BUILD/tests/NUCLEO_G431RB/ARM/main.o).

is not normal. This is because you can't have a main.cpp file in your root directory during test...
You have to temporary rename or remove it.

jeromecoutant · 2021-02-24T16:57:59Z

targets/TARGET_STM/TARGET_STM32G4/TARGET_STM32G431xB/TARGET_NUCLEO_G431RB/PinNames.h

+
+    USBTX = STDIO_UART_TX, // used for greentea tests
+    USBRX = STDIO_UART_RX, // used for greentea tests
+


Maybe you could add Arduino pins definitions here ? :-)

adbridge · 2021-03-10T14:37:37Z

@rotu for future reference you should use rebase not merge , thanks.

rotu · 2021-03-10T18:15:40Z

@adbridge rebased

rotu · 2021-03-10T18:34:10Z

~~Here's the test logs. I think the runner is hung. It looks like the sleep/timer stuff is failing.~~
~~Seems to be passing now, not sure why it failed in the first place.~~

mbedgt: greentea test automation tool ver. 1.7.4
mbedgt: test specification file './BUILD/tests/NUCLEO_G431RB/ARM/test_spec.json' (specified with --test-spec option)
mbedgt: using './BUILD/tests/NUCLEO_G431RB/ARM/test_spec.json' from current directory!
mbedgt: detecting connected mbed-enabled devices...
mbedgt: detected 1 device
mbedgt: processing target 'NUCLEO_G431RB' toolchain 'ARMC6' compatible platforms... (note: switch set to --parallel 1)
mbedgt: running 113 tests for platform 'NUCLEO_G431RB' and toolchain 'ARMC6'
mbedgt: mbed-host-test-runner: started
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'NUCLEO_G431RB', '-p', '/dev/ttyACM0:115200', '-f', '"BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/sleep_lock/sleep_lock.bin"', '-e', '"mbed-os/drivers/tests/TESTS/host_tests"', '-d', '/media/dan/NOD_G431RB', '-c', 'default', '-t', '08500221132B68172C6FF17A', '-r', 'default', '-C', '4', '--sync', '5', '-P', '60'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-sleep_lock' ............................. TIMEOUT in 35.96 sec
	test case: 'DeepSleepLock lock test' ......................................................... ERROR in 0.00 sec
	test case: 'timer lock test' ................................................................. SKIPPED in 0.00 sec
mbedgt: mbed-host-test-runner: started
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'NUCLEO_G431RB', '-p', '/dev/ttyACM0:115200', '-f', '"BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/timerevent/timerevent.bin"', '-e', '"mbed-os/drivers/tests/TESTS/host_tests"', '-d', '/media/dan/NOD_G431RB', '-c', 'default', '-t', '08500221132B68172C6FF17A', '-r', 'default', '-C', '4', '--sync', '5', '-P', '60'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-timerevent' ............................. ERROR in 10.75 sec
	test case: 'Test insert' ..................................................................... OK in 0.05 sec
	test case: 'Test insert timestamp from the past' ............................................. SKIPPED in 0.00 sec
	test case: 'Test insert_absolute' ............................................................ OK in 0.05 sec
	test case: 'Test insert_absolute timestamp from the past' .................................... SKIPPED in 0.00 sec
	test case: 'Test insert_absolute zero' ....................................................... SKIPPED in 0.00 sec
	test case: 'Test remove after insert' ........................................................ OK in 0.15 sec
	test case: 'Test remove after insert_absolute' ............................................... ERROR in 0.00 sec
mbedgt: mbed-host-test-runner: started
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-generic_tests' .......................... OK in 9.70 sec
	test case: 'Basic' ........................................................................... OK in 0.00 sec
	test case: 'Blinky' .......................................................................... OK in 0.00 sec
	test case: 'C++ heap' ........................................................................ OK in 0.01 sec
	test case: 'C++ stack' ....................................................................... OK in 0.01 sec
mbedgt: test case summary: 4 passes, 0 failures
mbedgt: mbed-host-test-runner: started
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-buffered_serial' ........................ OK in 9.89 sec
	test case: 'Bytes are correctly received' .................................................... OK in 0.02 sec
	test case: 'Bytes are correctly sent' ........................................................ OK in 0.03 sec
mbedgt: test case summary: 2 passes, 0 failures
mbedgt: mbed-host-test-runner: started
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-race_test' .............................. OK in 10.91 sec
	test case: 'class init race' ................................................................. SKIPPED in 0.00 sec
	test case: 'function init race' .............................................................. ERROR in 0.00 sec
mbedgt: test case summary: 2 passes, 0 failures
mbedgt: utest test case summary mismatch: utest reported passes and failures miscount!
	reported by utest: passes = 2, failures 0)
	test case result count: passes = 0, failures 2)
mbedgt: mbed-host-test-runner: started

rotu · 2021-03-10T19:03:49Z

I have no idea how to interpret these outputs. It seems DeepSleepLock test passes.

mbedgt: test case summary: 7 passes, 0 failures
mbedgt: mbed-host-test-runner: started
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-sleep_lock' ............................. OK in 10.38 sec
        test case: 'DeepSleepLock lock test' ......................................................... OK in 0.06 sec
        test case: 'timer lock test' ................................................................. OK in 0.05 sec
mbedgt: test case summary: 2 passes, 0 failures

but later on in the log it says "mbedgt: :191::FAIL: Deepsleep should be allowed.":

mbedgt: mbed-host-test-runner: started
mbedgt: checking for GCOV data...
mbedgt: test case summary event not found
        no test case report present, assuming test suite to be a single test case!
        test suite: mbed-os-drivers-tests-tests-mbed_drivers-dev_null
        test case: mbed-os-drivers-tests-tests-mbed_drivers-dev_null
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-dev_null' ............................... OK in 11.77 sec
        test case: 'mbed-os-drivers-tests-tests-mbed_drivers-dev_null' ............................... OK in 11.77 sec
mbedgt: test case summary: 1 pass, 0 failures
mbedgt: mbed-host-test-runner: started
mbedgt: :191::FAIL: Deepsleep should be allowed.
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-watchdog_reset' ......................... OK in 20.23 sec
        test case: 'Kicking the Watchdog prevents reset' ............................................. OK in 0.07 sec
        test case: 'Watchdog reset' .................................................................. OK in 0.05 sec
        test case: 'Watchdog reset in deepsleep mode' ................................................ OK in 0.06 sec
        test case: 'Watchdog reset in sleep mode' .................................................... OK in 0.07 sec
        test case: 'Watchdog started again' .......................................................... OK in 0.13 sec
mbedgt: test case summary: 1 pass, 0 failures
mbedgt: utest test case summary mismatch: utest reported passes and failures miscount!
        reported by utest: passes = 1, failures 0)
        test case result count: passes = 5, failures 0)

jeromecoutant

Note you changed 2 files in targets/TARGET_STM/TARGET_STM32L1/TARGET_STM32L152xC/TARGET_MOTE_L152RC

0xc0170 · 2021-03-11T11:11:54Z

Note you changed 2 files in targets/TARGET_STM/TARGET_STM32L1/TARGET_STM32L152xC/TARGET_MOTE_L152RC

Please revert these two and this should be ready for CI

rotu · 2021-03-29T17:58:50Z

@jeromecoutant, @adbridge I still have some problems with the tests which make me doubt that passing CI would be sufficient. Some tests are showing failure messages after the test cases themselves have passed. I'm way out of my depth here.

#14259 (comment)
#14259 (comment)

rotu · 2021-03-29T18:51:29Z

rebased onto master and fixed breaking changes

rotu · 2021-03-29T19:09:48Z

Still having weird test problems after rebasing on master and fixing build bugs:

Image: BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/timerevent/timerevent.bin


Memory map breakdown for built projects (values in Bytes):
| name       | target        | toolchain | static_ram | total_flash |
|------------|---------------|-----------|------------|-------------|
| timerevent | NUCLEO_G431RB | ARMC6     |      10694 |       47473 |


Build successes:
  * NUCLEO_G431RB::ARMC6::MBED-BUILD
  * NUCLEO_G431RB::ARMC6::MBED-OS-DRIVERS-TESTS-TESTS-MBED_DRIVERS-TIMEREVENT
mbedgt: greentea test automation tool ver. 1.7.4
mbedgt: test specification file './BUILD/tests/NUCLEO_G431RB/ARM/test_spec.json' (specified with --test-spec option)
mbedgt: using './BUILD/tests/NUCLEO_G431RB/ARM/test_spec.json' from current directory!
mbedgt: detecting connected mbed-enabled devices...
mbedgt: detected 1 device
mbedgt: processing target 'NUCLEO_G431RB' toolchain 'ARMC6' compatible platforms... (note: switch set to --parallel 1)
mbedgt: test case filter (specified with -n option)
        mbed-os-drivers-tests-tests-mbed_drivers-timerevent
        test filtered in 'mbed-os-drivers-tests-tests-mbed_drivers-timerevent'
mbedgt: running 1 test for platform 'NUCLEO_G431RB' and toolchain 'ARMC6'
mbedgt: mbed-host-test-runner: started
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'NUCLEO_G431RB', '-p', '/dev/ttyACM0:9600', '-f', '"BUILD/tests/NUCLEO_G431RB/ARM/mbed-os/drivers/tests/TESTS/mbed_drivers/timerevent/timerevent.bin"', '-e', '"mbed-os/drivers/tests/TESTS/host_tests"', '-d', '/media/dan/NOD_G431RB', '-c', 'default', '-t', '08500221132B68172C6FF17A', '-r', 'default', '-C', '4', '--sync', '5', '-P', '60'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: test on hardware with target id: 08500221132B68172C6FF17A
mbedgt: test suite 'mbed-os-drivers-tests-tests-mbed_drivers-timerevent' ............................. TIMEOUT in 15.87 sec
        test case: 'Test insert' ..................................................................... OK in 0.09 sec
        test case: 'Test insert timestamp from the past' ............................................. SKIPPED in 0.00 sec
        test case: 'Test insert_absolute' ............................................................ SKIPPED in 0.00 sec
        test case: 'Test insert_absolute timestamp from the past' .................................... SKIPPED in 0.00 sec
        test case: 'Test insert_absolute zero' ....................................................... SKIPPED in 0.00 sec
        test case: 'Test remove after insert' ........................................................ SKIPPED in 0.00 sec
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.9190187701
mbedgt: test suite report:
| target              | platform_name | test suite                                          | result  | elapsed_time (sec) | copy_method |
|---------------------|---------------|-----------------------------------------------------|---------|--------------------|-------------|
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | TIMEOUT | 15.87              | default     |
mbedgt: test suite results: 1 TIMEOUT
mbedgt: test case report:
| target              | platform_name | test suite                                          | test case                                    | passed | failed | result  | elapsed_time (sec) |
|---------------------|---------------|-----------------------------------------------------|----------------------------------------------|--------|--------|---------|--------------------|
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test insert                                  | 1      | 0      | OK      | 0.09               |
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test insert timestamp from the past          | 0      | 0      | SKIPPED | 0.0                |
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test insert_absolute                         | 0      | 0      | SKIPPED | 0.0                |
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test insert_absolute timestamp from the past | 0      | 0      | SKIPPED | 0.0                |
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test insert_absolute zero                    | 0      | 0      | SKIPPED | 0.0                |
| NUCLEO_G431RB-ARMC6 | NUCLEO_G431RB | mbed-os-drivers-tests-tests-mbed_drivers-timerevent | Test remove after insert                     | 0      | 0      | SKIPPED | 0.0                |
mbedgt: test case results: 1 OK / 5 SKIPPED
mbedgt: completed in 15.98 sec
mbedgt: exited with code 1
[mbed] ERROR: "mbedgt" returned error.
       Code: 1
       Path: "/home/dan/Mbed Programs/shared"
       Command: "mbedgt --test-spec ./BUILD/tests/NUCLEO_G431RB/ARM/test_spec.json -n mbed-os-drivers-tests-tests-mbed_drivers-timerevent"
       Tip: You could retry the last command with "-v" flag for verbose output
---

jeromecoutant · 2021-03-30T07:28:02Z

I don't know, everything is working well on my side:

$ mbed test -m NUCLEO_G431RB -t ARM -v -n drivers*event

target	platform_name	test suite	test case	passed	result	elapsed_time (sec)
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test insert	1	OK	0.07
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test insert timestamp from the past	1	OK	0.07
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test insert_absolute	1	OK	0.1
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test insert_absolute timestamp from the past	1	OK	0.08
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test insert_absolute zero	1	OK	0.05
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test remove after insert	1	OK	0.21
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-timerevent	Test remove after insert_absolute	1	OK	0.21

Using ARM Compiler 6.15 and

$ pip list | grep mbed
mbed-cli           1.10.5
mbed-greentea      1.8.3
mbed-host-tests    1.8.3
mbed-ls            0.0.0

jeromecoutant · 2021-03-30T08:00:34Z

Travis CI is failing due to the new pin standard feature.
I corrected it in 2cd113d
I also added Arduino-uno pins.
Fell free to add it in your PR :-)

rotu · 2021-03-30T19:29:46Z

I don't know, everything is working well on my side

Great! If you can't see it then it's probably Murphy's Law on my end.

Travis CI is failing due to the new pin standard feature.
I corrected it in 2cd113d
I also added Arduino-uno pins.
Fell free to add it in your PR :-)

Pulled it in! Thank you so much!

0xc0170 · 2021-04-07T09:59:05Z

CI started

mbed-ci · 2021-04-07T13:38:36Z

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️

ciarmcom added the release-type: patch Indentifies a PR as containing just a patch label Feb 9, 2021

ciarmcom requested review from a team February 9, 2021 21:30

ciarmcom added the needs: review label Feb 9, 2021

0xc0170 added the scope: new-target label Feb 10, 2021

jeromecoutant reviewed Feb 10, 2021

View reviewed changes

targets/targets.json Outdated Show resolved Hide resolved

mergify bot added needs: work and removed needs: review labels Feb 11, 2021

ciarmcom added the stale Stale Pull Request label Feb 22, 2021

jeromecoutant suggested changes Feb 24, 2021

View reviewed changes

targets/targets.json Outdated Show resolved Hide resolved

jeromecoutant reviewed Feb 24, 2021

View reviewed changes

ciarmcom removed the stale Stale Pull Request label Mar 3, 2021

jeromecoutant approved these changes Mar 9, 2021

View reviewed changes

rotu force-pushed the G431RB branch from b80eb1f to 4abec88 Compare March 10, 2021 18:50

jeromecoutant approved these changes Mar 11, 2021

View reviewed changes

rotu force-pushed the G431RB branch from 4abec88 to c643bc4 Compare March 12, 2021 20:38

rotu added 4 commits March 29, 2021 13:50

Support Nucleo G431RB

3292d05

remove clock_source override

b00add5

switch to new target naming conventions

f7e628d

rename USBRX -> CONSOLE_RX

1c2986a

rotu force-pushed the G431RB branch from fe10f81 to 1c2986a Compare March 29, 2021 18:51

mergify bot added needs: work and removed needs: review labels Mar 29, 2021

jeromecoutant added a commit to jeromecoutant/mbed that referenced this pull request Mar 30, 2021

ARMmbed#14259 Support STM Nucleo-G431RB

269bcbf

NUCLEO_G431RB: pin standard

80fed0b

jeromecoutant approved these changes Mar 31, 2021

View reviewed changes

0xc0170 approved these changes Apr 7, 2021

View reviewed changes

0xc0170 added needs: CI and removed needs: work labels Apr 7, 2021

mergify bot added ready for merge and removed needs: CI labels Apr 7, 2021

0xc0170 merged commit 160b32a into ARMmbed:master Apr 8, 2021

mergify bot removed the ready for merge label Apr 8, 2021

rotu deleted the G431RB branch April 9, 2021 10:43

mbedmain added release-version: 6.10.0 Release-pending labels Apr 16, 2021

mbedmain removed release-type: patch Indentifies a PR as containing just a patch Release-pending labels Apr 26, 2021


		USBTX = STDIO_UART_TX, // used for greentea tests
		USBRX = STDIO_UART_RX, // used for greentea tests

Support STM Nucleo-G431RB #14259

Support STM Nucleo-G431RB #14259

Uh oh!

Conversation

rotu commented Feb 9, 2021

Summary of changes

Impact of changes

Migration actions required

Documentation

Pull request type

Test results

Reviewers

Uh oh!

ciarmcom commented Feb 9, 2021

Uh oh!

rotu commented Feb 10, 2021

Uh oh!

LMESTM commented Feb 10, 2021

Uh oh!

0xc0170 commented Feb 10, 2021

Uh oh!

jeromecoutant left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rotu commented Feb 10, 2021

Uh oh!

rotu commented Feb 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mergify bot commented Feb 11, 2021

Uh oh!

ciarmcom commented Feb 22, 2021

Uh oh!

jeromecoutant left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jeromecoutant commented Feb 24, 2021

Uh oh!

jeromecoutant Feb 24, 2021

Choose a reason for hiding this comment

Uh oh!

adbridge commented Mar 10, 2021

Uh oh!

rotu commented Mar 10, 2021

Uh oh!

rotu commented Mar 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rotu commented Mar 10, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jeromecoutant left a comment

Choose a reason for hiding this comment

Uh oh!

0xc0170 commented Mar 11, 2021

Uh oh!

rotu commented Mar 29, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rotu commented Mar 29, 2021 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rotu commented Mar 29, 2021

Uh oh!

jeromecoutant commented Mar 30, 2021

Uh oh!

jeromecoutant commented Mar 30, 2021

Uh oh!

rotu commented Mar 30, 2021

Uh oh!

0xc0170 commented Apr 7, 2021

Uh oh!

mbed-ci commented Apr 7, 2021

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

Uh oh!

Uh oh!

rotu commented Feb 10, 2021 •

edited

Loading

rotu commented Mar 10, 2021 •

edited

Loading

rotu commented Mar 10, 2021 •

edited

Loading

rotu commented Mar 29, 2021 •

edited

Loading

rotu commented Mar 29, 2021 •

edited

Loading