Oberon microsystems has been working on STM32F4 (cerberus) port for sometime while GHI was also working on the port. At the point we learned of each other ports, Oberon were at a more advanced stage. So instead of doing double work, we decided to work together on the port and to use their work as the base. Waiting for Oberon’s announcement, we couldn’t say more about Cerberus progress lately. Please see today’s announcement http://www.mountaineer.org/news/
We are glad to say that this complete and stable firmware is already running on cerberus/cerbuino/cerb40. Working with Oberon microsystems has been a pleasure to GHI Electronics. A major announcement to come from both companies which involves CSA Engineering as well, so stay tuned.
We see this cooperation as an especially important step as it demonstrates how NETMF partner companies can work hand in hand to achieve higher goals.
Now for the plan: We are currently adding GHI’s OSHW libraries to the firmware and doing some final touches. In addition, Microsoft’s Gadgeteer team is about to release a non-beta core soon. If all goes well, we will have a Release Candidate GHI package in about a week.
Thanks to Oberon microsystems, CSA Engineering and this amazing community.
Incorrect, this will sill be the TinyCLR community place to work on the STM32 port then we can feed any fixes back to Oberon and to Microsoft. AN example is in adding GCC support
I have been busy at work lately, so I have not been updating my software or playing with betas/OSW versions.
So I am confused.
We have the Premium/OSW libraries, we have 4.1/4.2 versions, we have GHI versions, we have community versions(?), released, beta, alpha(?), joint company
It would be nice if there was a chart identifying all of the firmware/sdk alternatives, by board, and their current status.
Based upon some of the questions I have seen lately, others are also confused, and beginners are buying boards that have unexpected “not ready for prime time” support.
Mike, I agree completely. I’ve been wanting to pull the trigger on a Cerberus or Cerbuino, but have been hesitant given that it’s hard to keep track of the status of firmware and SDKs in a central location (the info is all here, it just tends to end up scattered across multiple forum posts).
A chart such as you describe would be VERY helpful, IMO.
There is nothing yet outside beta board, right? But I agree with you this can be confusing. This is why we want to finish it all before this goes on the support page here Support – GHI Electronics
So, for those who can handle all the confusion for the next week or so, they can help us in testing what we have so far but if it is confusing then the support page is what should be used.
This will be better and cleared up in a week or two.
