[protomyth]

"At least for now, the configuration tooling will be a part of the Qt for Device Creation product, and not open source."

I do wonder how a lot of companies's dual license model is going to interact with the IoT / embedded world.

[joezydeco]

I'm thinking about avoiding it for my IoT device node work.

I'm prototyping a node project right now for a large customer (>50K deployments) and while Qt helped me get code running quickly there won't be a way to comply with the dynamic linking model on my final hardware. Can't afford the Qt license in my BOM (probably would be 25% of my bill) so out it goes.

[protomyth]

Any idea what you are going to replace it with?

[joezydeco]

A lot of my smaller devices uses FreeRTOS, it's got a nice simple scheduler and it's easy to work with.

I've also used the uEZ application later from FDI on top of FreeRTOS when I need a more robust application.

Although I'm looking at the Kinetis M3 line for upcoming work, so I might use mbed.