Fixing BLE priorities and making them configurable

[pwilkowski]

as per #933

i checked it in my local project and it seem to work file for nrf52840

[h2zero]

Thanks @pwilkowski, I will merge this shortly, just need to test a few things first.

[h2zero]

@pwilkowski Looks like there are some issues with this, causes errors on some of my boards. What needs to be done is the timer task needs to be lower priority than the controller task. I have added this to the nimble core 1.6 PR #891 and you can see the implementation here: https://github.com/h2zero/NimBLE-Arduino/blob/nimble-core-1.6/src/nimble/porting/npl/freertos/src/nimble_port_freertos.c

This requires an update to the n-able core timer task priority to work correctly, I set it to 2, which works great.

[pwilkowski]

@h2zero that is weird, because it totally fixed my issues. And my timer still has highest priority. Which board are you talking about?

Generally if possible, please make all priorities configurable. My task stack is pretty complex and i needed to fiddle around to make USB, BLE and internal tasks working fine. Solution was pretty straightforward tho, just assign each task its own unique priority and sort them out.

[h2zero]

The issue was in nimble 1.6 with an nrf52833.

I will be making all of these configurable. For now please update this PR to match the code in the 1.6 PR so I can merge this PR.

[pwilkowski]

@h2zero i think i updated it correctly, please check

[h2zero]

Thanks @pwilkowski, unfortunately the build failed. I have merged the nimble 1.6 update that has the changes in it though so this will no longer apply.

[pwilkowski]

That is weird but I see its configurable now so all good.