Skip to content

[NUCLEO_L073RZ] Add device in RTOS files #1577

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 1 commit into from
Mar 2, 2016
Merged

[NUCLEO_L073RZ] Add device in RTOS files #1577

merged 1 commit into from
Mar 2, 2016

Conversation

bcostm
Copy link
Contributor

@bcostm bcostm commented Feb 29, 2016

No description provided.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 1, 2016

Please run RTOS tests, and share the output with us

The files look fine to me.

@mcusupstm
Copy link

The tests reports are here:
REPORTS.zip

Some tests are failed. I have also run the same tests on the Nucleo_L053R8 to compare. For sure we'll have to understand why these tests are fail. This will be done later when we'll update the ST HAL driver and recheck everything.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 1, 2016

The tests reports are here:
REPORTS.zip

If you could share the output here for the next time, it is much easier to view than download+unzip+open. There's one build failure for this board with uARM, RTOS_4 , can you elaborate? Is uARM the default toolchain for this target?

+1 for sharing L053 for comparison

@bcostm
Copy link
Contributor Author

bcostm commented Mar 2, 2016

There was an instability of the test. I have re-launched the RTOS_4 several times and it is ok.
image

0xc0170 added a commit that referenced this pull request Mar 2, 2016
[NUCLEO_L073RZ] Add device in RTOS files
@0xc0170 0xc0170 merged commit c0da36d into ARMmbed:master Mar 2, 2016
@bcostm bcostm deleted the rtos_nucleo-l073rz branch March 2, 2016 13:18
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