Skip to content
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

mc4plus v3.43 + mc4plus-trace-rtos v103.43 + ems v3.46 + mc2plus v3.29 #42

Merged
merged 1 commit into from
Nov 23, 2021
Merged

mc4plus v3.43 + mc4plus-trace-rtos v103.43 + ems v3.46 + mc2plus v3.29 #42

merged 1 commit into from
Nov 23, 2021

Conversation

marcoaccame
Copy link
Contributor

@marcoaccame marcoaccame commented Nov 23, 2021

mc4plus v3.43 + mc4plus-trace-rtos v103.43 + ems v3.46 + mc2plus v3.29
also added the related .map files

  • built:
    • mc4plus v3.43, build 23 nov 2021 @ 11:21
    • mc4plus-trace-rtos v103.43, build 23 nov 2021 @ 11:21
    • ems v3.43, build 23 nov 2021 @ 11:32
    • mc2plus v3.43, build 23 nov 2021 @ 11:24
  • main changes from previous release are:
    • fixed priority policy in of interrupts in hal so that now:
      • we always keep NVIC_PriorityGroup_4 (16 priorities, 0 subpriorities)
        and never change it in runtime (as the mc4plus did and now it does not anymore).
      • dont use anymore priorities 14 and 15 because they must be reserved for
        the correct behavior of the RTOS (mc4plus used priority 15, not anymore now).
        i believe / hope that the fixing of priorities can solve the fatal error of the mc4plus due to
        dirty stack usage by the RTOS.

See associated PR robotology/icub-firmware#219 and issue robotology/icub-tech-support#673 (comment)

also added the related .map files

- built:
  - mc4plus v3.43, build 23 nov 2021 @ 11:21
  - mc4plus-trace-rtos v103.43, build 23 nov 2021 @ 11:21
  - ems v3.43, build 23 nov 2021 @ 11:32
  - mc2plus v3.43, build 23 nov 2021 @ 11:24
- main changes from previous release are:
  - fixed priority policy in of interrupts in hal so that now:
    - we always keep NVIC_PriorityGroup_4 (16 priorities, 0 subpriorities)
      and never change it in runtime (as the mc4plus did and now it does not anymore).
    - dont use anymore priorities 14 and 15 because they must be reserved for
      the correct behavior of the RTOS (mc4plus used priority 15, not anymore now).
  i believe / hope that the fixing of priorities can solve the fatal error of the mc4plus due to
  dirty stack usage by the RTOS.
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.

1 participant