[title]USBiziOpen[/title]
You will also notice a new addition to the SDK, USBiziOpen. This is an all open source OSHW release for USBizi chipset and its derivatives, FEZ Panda, FEZ Panda II, FEZ Mini and FEZ Rhino. The sources are located at http://usbiziopen.codeplex.com/ and the wiki for this is here http://wiki.tinyclr.com/index.php?title=USBiziOpen_Developer The port is still early but it is tested to boot and deploy simple application.
Please see release notes for info.
[title]The Plan[/title]
We will be releasing at least one more 4.1 package to cover the latest modules but from there on, it will be all NETMF and gadgeteer 4.2.
As for FEZ Cerberus, which is based on STM32F4, we are sadly seeing too many redundant work by users and by companies. There is at least Cerberus/netduino/Oberon and ST discovery board. We are calling on everyone to join forces and have a one golden STMF4 port on codeplex, that we all contribute to and benefit from. After all, isn’t this is what open source is about? Any ideas and suggestions?
This is NETMF release fro OSHW boards, not gadgeteer.
STM32F1 (original port) and new STM32F4 are very similar yet have enough differences to cause some troubles and week of work. Oberon (the F1 port makers) are working on F4 port but that is not out yet I believe. What is available today is from GHI and netduino, 2 open source projects for the exact same processor! Users also are interested in the ST discoveryboard, this is from ST. You can find the info on the wiki.
Not to forget that a chip can be booted with NETMF in few days but then you spend months tweaking things and adding peripheral drivers. It would be great if we do not all work on the same thing!
As it’s GHI’s port, I think it’s GHI’s place to create a central place that we can work on this port. I’m all for CodePlex, or wherever.
Of the code that’s been released so far, Netduino’s gives me more “warm fuzzy” feelings, for two reasons:
[ol]they’re using the correct include for the STM32F4 instead of a modified STM32F1 header
they’ve got support (supposedly) for compiling with GCC. Given the performance of GCC 4.6, and the amount of flash available on Cerberus/Cerb40/Netduino, I think it’s a more viable option, especially if there is any hope for contributions for the community, who generally won’t have access to RVDS.[/ol]
I’m not experienced enough to evaluate the differences in the startup code, I only know that there ARE some differences.
now I am very puzzled, I have looked at the open uzbizi code at code.google.com for some long time not understanding what it was, now the same code is on codeplex and claimed to be directly from GHI?
really puzzled, asfaik uzbizi support usb host and device? in the open uzbizi is some usb_platform file but there what I see are references to
Gus, I think you, Chris Walker, and the folks at Oberon should get together for dinner and come up with a good solution. I doubt this is a problem that can be solved in this forum.
When will the changes in the Cerberus firmware be updated on the Cerberus firmware / software status page? ( GHI Electronics – Where Hardware Meets Software ) Or is that page still correct?
