Skip to content

[Nucleo_F446RE] adding target #1110

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

Merged
merged 5 commits into from
Jun 1, 2015
Merged

Conversation

ohagendorf
Copy link
Contributor

Adding target incl. RTOS support and exporters to gcc_arm and coide

singletest.py run is OK:
+--------+---------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result | Target | Toolchain | Test ID | Test Description | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+---------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| OK | NUCLEO_F446RE | GCC_ARM | DTCT_1 | Simple detect test | 0.52 | 10 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | EXAMPLE_1 | /dev/null | 3.45 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_10 | Hello World | 0.36 | 5 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_11 | Ticker Int | 11.36 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_12 | C++ | 1.38 | 10 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_16 | RTC | 4.73 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_2 | stdio | 0.8 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_23 | Ticker Int us | 11.37 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_24 | Timeout Int us | 11.37 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_25 | Time us | 11.35 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_26 | Integer constant division | 1.4 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_34 | Ticker Two callbacks | 11.38 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A1 | Basic | 1.37 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A21 | Call function before main (mbed_main) | 1.41 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A5 | DigitalIn DigitalOut | 1.37 | 10 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A6 | DigitalInOut | 1.37 | 10 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A7 | InterruptIn | 9.37 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_A9 | Serial Echo at 115200 | 6.52 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | MBED_BUSOUT | BusOut | 2.27 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_1 | Basic thread | 11.36 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_2 | Mutex resource lock | 11.35 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_3 | Semaphore resource lock | 8.36 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_4 | Signals messaging | 6.37 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_5 | Queue messaging | 2.38 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_6 | Mail messaging | 2.37 | 20 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_7 | Timer | 11.36 | 15 | 1/1 |
| OK | NUCLEO_F446RE | GCC_ARM | RTOS_8 | ISR (Queue) | 6.38 | 20 | 1/1 |
+--------+---------------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+

@0xc0170
Copy link
Contributor

0xc0170 commented May 21, 2015

Can you rebase on the top of master please?

Create the new target - mbed_blinky is runnning
Update system_stm32f4xx to new version, generated by STM32CubeMX
Add target name to digital_loop test
Update coide export template
RTOS_1 .. RTOS_8 tests are OK
- resolving a rebase conflict
- adding pin config for MBED_A7 test (interruptin)
@ohagendorf
Copy link
Contributor Author

It's rebased. And singletest.py is still OK.

What can be done against the ci/circleci test failures?

@0xc0170
Copy link
Contributor

0xc0170 commented May 26, 2015

To be honest, I personally don't know who enabled that circleci, as there seems to be no tests defined.

@PrzemekWirkus
Copy link
Contributor

Yes, please ignore Circle CI :)
This is only useful if you run tests without hardware instrumentation.

In the future I will add Python UT tests for workspace_tools so we can call python setup.py test or pyTest for workspace_tools but for now it is useless for mbed SDK ports.

0xc0170 added a commit that referenced this pull request Jun 1, 2015
@0xc0170 0xc0170 merged commit 7ab478c into ARMmbed:master Jun 1, 2015
@ohagendorf ohagendorf deleted the nucleo_f446 branch June 2, 2015 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants