Welcome to the MikroE
Thank you for your time for sharing your opinion,
and I sincerely apologize for all unpleasantness.
I understand you, but unfortunately, at this moment, we can only provide hardware
and software support for development boards which are MikroElektronika's products
and which MCUs are supported in MikroElektronika's compilers.
For shields which are made for non MikroElektronika's boards,
we can only provide hardware support.
-- The beaglebone cape has a firmware.
I'm sorry for misunderstanding, Beaglebone cape doesn't come with firmware, it is only a shield,
i.e. pinout for connecting on an easy way click boards. It only has in addition chip for EEPROM.
All our products are tested before sending, but if you doubt if mikroBus Cape is working,
you can open a ticket and we will investigate it:https://helpdesk.mikroe.com/index.php?/Tickets/Submit
-- Oled B click. There is an undocumented 5V pin.
5V pin is used along with AP7331 linear regulator
which is used for VDDB (Supply voltage for internal DC/DC on display).
For the click boards there are examples written in our compilers,
which can be used as reference. Also, all click boards are tested before sending.
And with introduction to mikroSDK
examples can be easy written for MikroElektronika development boards.
-- Speaking of Github: It's great that you upload some of your products there. How about being a bit more active in the community aspect? I bet very few of the library maintainers would mind accepting pull requests from your engineering team.
-- Why not supporting something like platformio.org, and promote the mikrobus standard there by offering really nice library support?
Thnak you for the suggestions, I have forwarded them to our developers.
PS: Is Hexiwear better documented?
You can check Hexiwear documentation here:https://github.com/MikroElektronika/HEXIWEAR
If you have any doubt regarding some feature, feel free to contact us.