Stages of Firmware development

Image: stage NEQ

No Equipment. We have an SDK for the platform, but we don't have specific hardware to continue development, you can donate it to our R&D guys (especially old boards that passed EOL and can not longer be bought).

Image: stage R&D

The Research and Development stage, when we already have the platform SDK and maybe even the hardware boards, but we are starting to fiddle with the platform, studying its specifics and features. There is still a lot of work ahead.

Image: stage HLP

Help wanted. We have the hardware, we have the SDK, the basic stuff is learned and done. But we are stuck. This is where we are looking for help from experienced embedded developers to overcome the obstacles and move on to the next stage.

Image: stage WIP

Work in progress. We learned a lot about the platform hardware and code base, prepared the first public binary build, and are waiting for the first adopters to test it on their boards and provide feedback to help us move forward.

Image: stage MVP

A minimal viable product. The basic system is built, the platform can produce video, at least on the main channel, but due to a lack of human resources, development is delayed or halted. A financial infusion could push the development to the final stage.

Image: stage DONE

"Done and done!" Everything works just as it did in the original firmware. We're still waiting for feedback from you guys, though.

Typical development lifecycle

After we acquire an SDK for a new SoC, we add the SoC to the table of supported hardware. We assign either NEQ (No Equipment) status, if we do not have particular hardware modules, or HLP (Help Needed) status, if we have the hardware but are looking for a developer who would lead the development for that SoC. This is considered an official start of development.

There is no reason to have SoC in the table without having its SDK.

As work on the SoC progresses, its status changes, gradually. First to RND, then to WIP, then further to MVP, and, finally, to DONE.