Main Site Documentation

TinyCLR vs .NETMF for today's embedded app


#1

This is a tricky question I am sure.

We want to start developing an product, however, with TinyCLR in its infancy it appears that .NETMF is still the mature (and tested?) option.

My question is, with the old GHI site about to die. Will support for the GHI Implementation of .NETMF die along with it? The last thing we want to do is build something on a framework that won’t be supported.

Things that I think make the .NETMF the best choice (which TinyCLR currently lacks)

  1. RLP - Almost a must
  2. IFU
  3. Register Access
  4. USB Client
  5. SQLite Database

Look forward to opinions.

Side question, how does one acquire a G400 Dev Board? (400DB-SM-547)Mouser is out


#2

yes, NETMF 4.3 QFE2 released 3 years ago is still the preferred and recommended for production
TinyCLR OS is still alpha and missing features you seems to require

regarding support, if you find a bug in NETMF you have bad cards to have it solved, if its related to GHI’s code it looks like it depends


#3

One quick note is that both RLP and register access are possible in TinyCLR today. Take a look at http://docs.ghielectronics.com/software/tinyclr/porting/native_interops.html for how RLP is done now and System.Runtime.InteropServices.Marshal for register access.

The above linked post is correct, TinyCLR is the replacement for NETMF going forward. We’re working hard to get feature parity.


#4

The answer really depends on your timeline. NETMF is what is complete and mature so it is the way forward fi you are releasing a product in the next few months. If you are in designing a product to be released in a few months, TinyCLR is thee right path for you. Either way, I suggest you get in touch with our team about your commercial design. They may have additional info that is not out in the open yet :slight_smile:

For the dev board, the new UCM DEV board replaces the old one. There will be several announcements about what is new in the coming week. But like I said, you can always get in touch with our team to get further details.


#5

is Valon Hoti your lapdog ?
looks like he has fun to like your postings


#6

no, I think he, like many, appreciate Gus’s openness to answer a hard question.


#7

He has been an extremely helpful community member and a great contributor. People like him are the reason we love what we do.


#8

I give one like to you too.

and for lapdog word (that you offended me)

I like people who keep promises ,give hope for better things, and by helping others share their experience from what we learn too.

in this forums i’m not going to check who did like or not,since i am one of the of regular readers (maybe with not good English because is not my primary language) and i click button like for every appreciated answer,because i do not hesitate and i’m not here to offend anyone.

and excuse me if this hamper you :slight_smile:


#9

I like reading anyone’s contribution to someone question, yours too Kevin which i have seen often!
We are all here to try and learn, and give input when we can…
I think everyone appreciates everyone that contributes, including you.
Lets keep it going!
Without this forum/community, we would all just be reading PDF’s!


#10

I would like to expand on the USB Client needs for the G400 family. We would like to see both a bulk and interrupt end point available at the same time. Also a way of enabling USB High Speed mode.

This would make for better USB solution, in our product anyways.

Phil


#11

Hi,

Is there a timeline for TinyCLR to reach feature parity with NETMF? Ideally with the individual features listed out. I am very interested in jumping from NETMF as the support transfers, but we need CAN, IFU etc fully working before we do that.

Thanks

Nick


#12

The obstacle was building the core to then start on working on the individual features. We are making an announcement this week specifically about this.


#13

Thanks Gus,

I shall keep an eye out :slight_smile:

Nick