Improve HAL Initialize/Uninitialize

[josesimoes]

Description

• Add code to stop and release buses and drivers during nanoHAL_Uninitialize.
• Add code to init control structs of several drivers during nanoHAL_Initialize.
• Change declarations of control structs of several drivers to use typedef instead of plain structs.
• Add HAL options to TI SimpleLink to expose I2C and SPI inclusion to be able to properly manage the code in nanoHAL Init/Uninit.

Motivation and Context

• Stopping and disposing of drivers is executed on call of NativeDispose. This doesn't always happen (specially on CLR reboot on which the RTOS is not restarted, except on devices that don't have soft reboot), which leads to drivers being wrongly left active/locked and their control structs initialized.
• Similar situation with the control structs of some drivers on CLR restart, which where NOT being reset/initialized causing the issues on the code ahead that uses them in a invalid state.
• Resolves Usage of I2C on Netduino 3 Wifi causes execution to stop at I2cDevice.FromId Home#627.
• Resolves Usage of I2C on ST_NUCLEO64_F091RC causes execution fail on startup Home#626.

How Has This Been Tested?

• I2C and SPI samples with STM32F429, STM32F091.

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nfbot]

Hi @josesimoes,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

[nfbot]

@josesimoes there are issues with the code style on the source files.
A PR was submitted with the code style fixes. Please review and merge the changes. See Eclo#15.

Make sure you are using the project code style. Check the details here.

[nfbot]

@josesimoes there are issues with the code style on the source files.
A PR was submitted with the code style fixes. Please review and merge the changes. See Eclo#16.

Make sure you are using the project code style. Check the details here.