Finally - NetMf on GitHub

Caught via email:

[quote]The .NET Micro Framework development team has heard plenty of feedback about transitioning to GitHub and are now happy to announce that the transition has occured. The v4.3 and earlier code base will remain here on Codeplex, however the v4.4 and future releases will continue from GitHub (e.g. all future development will occur in GitHub but the CodePlex repositories will remain for historical support)

All feedback and bugs/issues on codeplex will be reviewed and when activated will be added to the work items in GitHub by the development team. Bugs filed in GitHub will be validated against v4.4 (or later depending on when the bug is filed)

The new .NET Micro Framework GitHub Page is: http://netmf.github.io[/quote]

Thought y’all might want to know …

13 Likes

Excellent

Nice to see that the solution folder has been cleaned and there are fewer solutions than before.

@ PiWi -

Is the link valid?

I’m getting:
•Make sure the web address http://netmf.github.io%3c is correct.

skip the %3c

or try NETMF · GitHub

or GitHub - NETMF/netmf-interpreter: .NET Micro Framework Interpreter

What’s the significance of this:

Isn’t the PK what we used to call the entire source distribution?

@ godefroi - It means you can just get it from GitHub and don’t need the “executable” that installs PK on your machine.

In fact there is only STM32 and STM32F4 native targets.
I wonder if that is the only targets that will be moved over. :think:

So no PK installer. Since (mostly) all it installed was source code. Makes sense.

They’re the targets that make the most sense. With the Discovery boards, you get a cheap, powerful NETMF target that’s easy to debug since it includes the onboard STLink.

They’re also pretty much the only targets that are in common use for OSS ports (except Hydra, if it’s still in common use).

Maybe ST will sponsor NETMF development :slight_smile:

I agree with that, but I would like to see the solution and native target for Hydra as well.

Hydra is an ARM9E-S, which doesn’t support CMSIS, which means, the new networking stuff won’t run on it. It would have to be custom-built.

Isn’t the STM32F4 faster, anyway? I believe that even at 168MHz it beats Hydra, let alone the F429 at 180MHz?

It is fast enough for what I use it for.

Judging from RLP benchmarks, Cerberus beats Hydra to the ground. However, Hydra uses external RAM, so the competition may not be fair. But I’m pretty sure STMs will still be faster.

But speed aside, my guess is that since they took a dependency on CMSIS for networking, you won’t see any (official) ports that don’t use CMSIS. That means no ARM9.

Interestingly, that may mean GHI will be on their own to implement networking for the G400. Yet another reason, in my mind (and if true), to keep the higher-performance systems out of NETMF and in something like RPi/RPi2, especially if it runs Windows.

Just my opinion and speculation.

Similar thread has popped up on SL.

This snippet starts ringing big alarm bells tho…

Secret Labs will continue contributing features and bugfixes to the NETMF core (above).

I admire what Chris has done in the past (my first NETMF board was an original Netduino) but if SL is working on the core and it’s not all bollocks…well lets just say that scares me… :open_mouth:

You don’t think Chris is qualified to work on NETMF?

@ Bill Gates - It just a standard statement. It means nothing other than “we are still in the game” really. Here is another one:

@ godefroi - not with his project management track record…

@ Architect - indeed

I doubt they’d ask him to do project management…

Yeah, may be offer the task of creating sales collateral… offers the oppurtunity to state anything and everything and does not force to deliver …