Supported Hardware
Get a camera running OpenIPC
Four ways, easiest first. The first two need no tools at all, and none of them needs a soldering iron.
Way 1
Buy one with OpenIPC already installed
These manufacturers and integrators ship cameras with OpenIPC on them. Plug one in and open its web interface.
Manufacturers
Integrators
Way 2
Switch a camera over the air
Many cameras built on Xiongmai boards switch from their factory firmware to OpenIPC through their own Upgrade button, with a Coupler image. Buy one of them, or check the one you have.
The device ID is the 4th part of the System version in the camera’s app or web interface: V5.00.R02.00001532.10010…
Way 3
Open up the camera you have
Unplug it and take the front off. Match the board against more than a thousand photographed boards, or read the chip itself.
The chip is the largest square one, often under a metal plate. Its top line reads like SSC335, T31X or Hi3516EV300.
Way 4
Not found? Ask the community
People answer every day. Post these three and someone will usually know the board:
- The label on the camera
- A photo of each side of the board
- The System version from its app
Reverse engineering a new camera? Get a shell on it and run ipctool, or have an AI coding agent dig through the vendor firmware, then send us the report. That is how new boards reach this list.
Already know the chip?
77 of the 126 chips we know of can take OpenIPC today. Find yours to see how.
- Recommended
- Find by board or camera
- Allwinner 0
- Ambarella 0
- Anyka 0
- Fullhan 2
- Goke 12
- GrainMedia 2
- HiSilicon 22
- Ingenic 17
- MStar 0
- Novatek 2
- Rockchip 2
- SigmaStar 15
- TI 0
- Xiongmai 3
- Full list
The number beside a chip maker counts its chips you can install today.
Recommended chips
The chips OpenIPC supports best. Chips at an earlier stage are on the full list.
| Chip (SoC) | Can I install it? |
|---|---|
| Goke GK7205V200 # | Guided install Generate an installation guide |
| Goke GK7205V210 # | Guided install Generate an installation guide |
| Goke GK7205V300 # | Guided install Generate an installation guide |
| Goke GK7605V100 # | Guided install Generate an installation guide |
| HiSilicon HI3516EV200 # | Guided install Generate an installation guide |
| HiSilicon HI3516EV300 # | Guided install Generate an installation guide |
| Ingenic T21 # | Guided install Generate an installation guide |
| Ingenic T23N # | Guided install Generate an installation guide |
| Ingenic T31AL # | Guided install Generate an installation guide |
| Ingenic T31L # | Guided install Generate an installation guide |
| Ingenic T31N # | Guided install Generate an installation guide |
| Ingenic T31X # | Guided install Generate an installation guide |
| Ingenic T31ZL # | Guided install Generate an installation guide |
| Ingenic T31ZX # | Guided install Generate an installation guide |
| Ingenic T40N # | Guided install Generate an installation guide |
| Ingenic T40XP # | Guided install Generate an installation guide |
| SigmaStar SSC30KD # | Guided install Generate an installation guide |
| SigmaStar SSC30KQ # | Guided install Generate an installation guide |
| SigmaStar SSC333 # | Guided install Generate an installation guide |
| SigmaStar SSC335 # | Guided install Generate an installation guide |
| SigmaStar SSC335DE # | Guided install Generate an installation guide |
| SigmaStar SSC337 # | Guided install Generate an installation guide |
| SigmaStar SSC337DE # | Guided install Generate an installation guide |
| SigmaStar SSC338Q # | Guided install Generate an installation guide |
| SigmaStar SSC377 # | Guided install Generate an installation guide |
| SigmaStar SSC377D # | Guided install Generate an installation guide |
| SigmaStar SSC377DE # | Guided install Generate an installation guide |
| SigmaStar SSC377QE # | Guided install Generate an installation guide |
| SigmaStar SSC378DE # | Guided install Generate an installation guide |
| SigmaStar SSC378QE # | Guided install Generate an installation guide |
What do the development stages mean?
-
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).
-
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.
-
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.
-
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.
-
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.
-
DONE - Done and done! Bootloader boots, Linux loads, streamer can stream video and produce snaphots. You can have yourself a working platform open for tinkering and further improvements. We still expect feedback and patches 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.