[FEATURE] Missing board shield support

[techdragon]

*Is your feature request related to a problem? Please describe. There are several click board shields that do not have proper support, which makes starting new projects more difficult than it needs to be.

Describe the solution you'd like Add support for the missing click shield boards, like the support that has been added for the Arduino Uno click board/shield combination:

• https://github.com/MikroElektronika/mikrosdk_v2/blob/master/bsp/board/include/boards/board_arduino_uno_rev3/board.h
• https://github.com/MikroElektronika/mikrosdk_v2/blob/master/bsp/board/include/shields/shield_arduino_uno_rev3/shield.h Which is as far as I can tell, for this particular product:
• https://www.mikroe.com/click-shield-for-arduino-uno ( MIKROE-5739 )

There is missing support for these items related to widely available dev boards (as well as others, but I'd argue these ones I'm listing would be most beneficial due to their wide availability in the hands of potential developers) on sale in the store:

• https://www.mikroe.com/arduino-uno-click-shield ( MIKROE-1581 )
  • The already released Uno Rev 3 board/shield code may already work (or only require minor changes) for this board as well since the Arduino Uno hardware has not changed significantly based on general Arduino shield compatibility over the years.
• https://www.mikroe.com/pi-2-click-shield ( MIKROE-1879 )
• https://www.mikroe.com/arduino-mega-click-shield ( MIKROE-1900 )
• https://www.mikroe.com/pi-3-click-shield ( MIKROE-2756 )
• https://www.mikroe.com/microbit-click-adapter ( MIKROE-2994 )
• https://www.mikroe.com/feather-click-shield ( MIKROE-3725 )
• https://www.mikroe.com/arduino-nano-click-shield ( MIKROE-4443 )
• https://www.mikroe.com/arduino-mkr-click-shield ( MIKROE-4444 )
• https://www.mikroe.com/pi-4-click-shield ( MIKROE-4122 )
• https://www.mikroe.com/click-shield-for-pi-400 ( MIKROE-4970 )
• https://www.mikroe.com/click-shield-for-pi-pico ( MIKROE-4985 )
• https://www.mikroe.com/click-shield-for-arduino-mega ( MIKROE-5831 )

More specifically I'd consider the MicroBit, Arduino Uno, Arduino Mega, Raspberry Pi 3, Raspberry Pi 4, Raspberry Pi 400 and Raspberry Pi Pico shields are the most useful as far as making the rest of the Click Boards ecosystem available to the widest pool of developers.

Describe alternatives you've considered While mapping these common boards by hand is doable... the need for each individual developer to make make their own mappings repeating the work that others have already done many times before... sort of defeats the purpose of having a library like this to save developer time.

Additional context Add any other context or screenshots about the feature request here.

[MarkoZiv]

Hi @techdragon thank you for reaching out.

Before supporting click shield, we have to support the actual board, and to do so there needs to be support for that specific MCU in the mikroSDK itself.

So, going through the list you mentioned:

• Arduino Mega has ATMega2560, currently supported in mikroSDK (will be implemented with shield in next release)
• micro:bit has nRF51822, currently not supported in mikroSDK
• Adafruit has a lot of feather boards, this will be investigated further what can be supported for next release
• Arduino Nano has ATmega328P, currently supported in mikroSDK (will be implemented with shield in next release)
• Arduino MKR relies on SAM MCUs, currently not supported in mikroSDK
• All the Raspberries are either Broadcom or RP, currently not supported in mikroSDK

One of the major focuses of Mikroe in 2024 is gonna be ramping up MCU support in the toolchains and mikroSDK