Endpoint roadmap

Hi everyone,
I looked at the documentation on github and would like to know if GHI already has a roadmap on SOM modules available.
Domino is certainly exceptional and I think I’m not the only one who wants to use this technology as soon as possible.
Let’s say that for the moment, in addition to the pinout of the SOMs, which is already there in github, the actual dimensions of the connection pads would be enough…
just to prepare ourselves in advance for the bang…

2 Likes

SoMs are already done and being evaluated. The pinout is 99% compatible with SITCore. More on that in Q1-2025.

1 Like

Hi. When can we order modules?

1 Like

WE WANT THE MODULES!
WE WANT THE MODULES!
:stuck_out_tongue_winking_eye:
or at least the semi-official pinout

2 Likes

How much money do you have? :nerd_face:

Never enough. :sunglasses:

1 Like

let’s agree… one is enough… then we share the information obtained from the mercenary… but let’s not tell him… let’s not make ourselves heard

Any updates on Endpoint?

3 Likes

I guess everyone is on vacation

So, look. I am one of the biggest GHI fans around - have been forever - but I find myself a bit confused as to where Endpoint and Domino fit into the spectrum of full-dotnet-enabled (i.e., Linux) compute modules. Endpoint is a lot more cost-effective at scale than the alternatives (BBB, RPi, RPi CM) but if you are approaching it as a hobbyist, then there’s a richer community behind RPi and you can run all the same GHI tools against the Endpoint runtime on RPi.

Now if you are into doing something at scale, then it’d be a great way to run full dotnet core and all the great tooling while still maintaining a reasonable cost profile, but since there’s no SOM out there yet, there’s no way to commit to it.

I’m not sure that even GHI has figured out where the thing fits in as evidenced by the lack of movement here. That’s not a criticism - I suspect they have other more profitable fish to fry and that’s how companies work. Though in that same sense, if you walk up to Gus with a sufficiently sized sack of money, I’m sure you could snag a bag of Endpoint in exchange.

So, if you want full dotnet on a platform with some longevity and availability, I think we’re stuck with either RPi and Beagle for hobbyist stuff, or the high-priced commercial alternatives (Toradex and friends) for industrial/commercial quality.

2 Likes

I really hope that the modules will appear by the end of the year. And we will all be able to smoothly switch to them. Just like we switched from G120 to SCM20260N.

“The Chain-of-Trust” from site https://www.ghielectronics.com/longevity/
“… timely development of new products while maintaining maximum compatibility”

The SoMs are already made if anyone has a sack of money. Maybe we can cover some of the tariffs! :grin:

You will always have options. We appreciate your trust and we take it seriously.

I have $10 burning a hole in my pocket :rofl:

1 Like

That’s only $6USD! :slight_smile:

1 Like

The Next Generation Star GIF

2 Likes

As a commercial user, I am a bit conflicted with Endpoint. We have invested heavily in TinyCLR, and I would love to see some of the open issues resolved. Every company has limited development resources, and I selfishly would like to see those resources directed towards TinyCLR. But unfortunately, the world does not revolve around me.

On the other hand, I do see potential for Endpoint, especially if it is pin-compatible with existing TinyCLR modules.

However, if I were to go full-bore with a larger embedded Linux product roll-out, I think I would lean towards Toradex since they have a much larger ecosystem and cloud services support for remote deployment and management.

I am confident GHI will release Endpoint when they feel it can be fully supported, and I am anxious to give it a go.

How much backwards compatibility do you need?

Just hardware compatibility. It would be ideal to be able to use the same hardware and swap between the SitCore SCM20260D and the Endpoint module.