Thank you very much for sharing this information. To get a better understanding how things work, I guess it’s best to order some Microbits and start playing around with those.
But however I still have some questions here.
When reading about support for MCUs I thought that this would be a bit like what those guys at Particle.io are doing with their MCUs - They offer similar services (e.g. Firmware Update OTA, etc.) but all their services focus on using their cloud / third party cloud.
All in all they do not offer quite the same freedom you get from an embedded linux device and even if their hardware is available for a very low price - I still prefer using embedded linux SOMs / SBCs powered by resinOS / resin.io a lot!
So what is it like to use the dependent device support? Do those dependent devices (for example a Microbit) appear on the dashboard - just like other devices? And what happens when I push code into the repo / application? Will the code be pushed onto the dependent device / Microbit - or at least its firmware file?
So this means that there has to be a gateway which will program the MCU. But have you thought of different MCUs with WiFi / Ethernet functionality? What about having a “resin-bootloader” for compatible MCUs that will communicate with resin.io over Ethernet / WiFi, etc!?
I know that there once was a boot loader for Arduino which opened up an TFTP-Server when booting so that within the first five seconds one could push Firmware / Sketch onto it.
Well a resin-bootloader for MCUs like Arduinos (but maybe not those 8-bit units), that’ll be awesome
I however let you know when I am working with the dependent device support and will give feedback!