MangOH Red Best Practices?

Hi all,

We’re looking at moving a project from a Particle processor over to a WP7603-1. Picked up a mangOH Red, and have to admit I’m confused as all get out. Hoping you could share your experience with me.

  1. What environment and tools are you programming with?
  2. Is anyone programming in C++, or is it all straight C?
  3. If you are working in C++, what does your program structure look like? Are you setting up the cell connection and such in C, then running separate programs (apps, components?) for the C++ stuff?

Guess I’m just getting a bit overwhelmed by my initial setup experience, which has been a bit… twitchy, I guess.


MangOH is a full Linux environment, so you have a lot of options for application development (C, C++, Python, Go, etc). Generally, with C/C++, you use cmake to build your app.

Go is an excellent app environment for embedded Linux – used it on 3 projects now and it is an amazing experience. It is nearly as efficient as C, but is much easier to write reliable programs. The Go stdlib is very good. I think Go is also a very natural migration for embedded C programmers – much more so than C++ in my experience.

Ah, interesting, thanks @cbrake. So you aren’t using the legato framework with the adefs and cdefs and such?

I’m not very far into my MangoH development yet – more coming from years of experience on other embedded linux platforms. I imagine the legato framework is still required, but you can likely call into the provided API from whatever app env you chose to work in.


You can write components in C++, but the generated IPC bindings are all C based. It would be nice if Legato provided more idiomatic C++ bindings, but it doesn’t today. It would also be nice if Legato supported more languages such as Go and Rust, but it doesn’t.