Splash out interventions for COM module

“Bringing up an Android or Linux BSP is non trivial,” says Ravi Kodavarti, Senior Director of Business Development and Strategy at Inforce Computing, Inc. in Fremont, CA (www.inforcecomputing.com). “Say our application has a 6440 carrier board, and on top of it we put a Qseven COM (Figure 2). However, Wi-Fi is really on the COM and the GPS chip is on the COM as well. These are fanless embedded computer well-tested interfaces not just from a hardware standpoint but also from a software standpoint, and writing these drivers and bringing these up is a pain. Every time you want to do that on a custom board, it is reinventing the work.” Removing legacy I/O and tracking advances in mobile technology have positioned Qseven to provide the long lifecycle support that telehealth systems demand. In an SFF market full of options, this will be critical to the platform’s success.

“Qseven does make fanless embedded computer  easier to design with because bringing up an Android system is not easy, contrary to popular opinion. Everybody has an Android system but those also drive a significant amount of volume in mobile and they put a lot of investment and people to make that happen. You cannot really do that in other spaces. Bringing up a stable platform is very important, and just having that modular architecture makes it so you do not really have to go and change things around too much.”

refer to: http://smallformfactors.com/articles/qseven-coms-healthcare-mobile/

This entry was posted in Embedded SBC, SBC and tagged , , . Bookmark the permalink.