Design Article
Comment
cedricfau
Thank you Subra and Max for sharing this information. This is a very interesting ...
Max the Magnificent
The growing use of programmable logic in mobile handsets
Subra Chandramouli, Lattice Semiconductor
5/17/2012 12:33 PM EDT
The pace of innovation in the mobile handset industry has never been higher, with users continuing to demand more from these devices. Smart phones, tablets and other battery powered devices have evolved beyond communication devices and now offer personal assistance by unifying “always connected” features such as navigation, email, phone, Internet access and camera. Choosing between the two leading smartphone operating systems, smartphone designers depend on their physical hardware to differentiate their products and position them against competitive products. This is an area where programmable logic devices add direct value by providing mobile handset system architects a way to quickly innovate and add new functionality to their products. Below are some examples of why and how low cost, low power programmable logic devices are successfully adding value to mobile handset design.
Asynchronous product development cycles within the handset industry
Readers of this article may not be surprised to learn that the product design life cycles of mobile handset and chipset vendors are fundamentally different. It is fairly common to see new phone models being introduced every other month, while chipset vendors release newer versions of their chipsets in a much slower product cycle cadence. While there are solid and obvious reasons for this, the challenge faced by handheld system architects is also real; i.e. keeping up with product innovation cycles that are faster than what the chipset vendors are capable of supporting. A good example of this is the recent announcement of the MIPI battery interface (BIF) standard.
The MIPI battery interface (BIF) standard
The use of dual-core and quad-core processors, along with the marketing imperative to create a compelling user experience, increases power consumption that has direct downstream effects on power delivery, battery life and longevity. Striking a balance among optimal power delivery, battery capacity, chemistry, safety, and form factor is a significant design challenge. The communication protocol established by MIPI-BIF provides a method for system designers to read parameters on demand to optimize power consumption during device use and to optimize battery charging. It also provides a method to authenticate batteries for systems that need to ensure user safety. Although the MIPI standard has already been announced, chipset vendors will still need time to adopt this standard in their products. However, handset designers may want to take advantage of MIPI-BIF much sooner. Programmable logic devices are perfectly suited in such situations, because they enable mobile system architects to adopt new standards using existing chipset or application processors. In fact, soon after MIPI released the BIF standard, Lattice Semiconductor announced its support for the standard and that it is engaged with key customers on implementing it.
Figure 1 illustrates the use of a low cost, low power FPGA to create a bridge between an existing application processor and the recently released MIPI-BIF standard. Communication over the BIF battery communication line (BCL) is enabled using the low power FPGA. On the application processor side, I2C, because it is commonly available, is a natural choice to connect the host application processor to the FPGA. A simple protocol is defined on top of the I2C standard to communicate between the host and the FPGA.
If needed, the host interface can be easily customized using the FPGA solution. In addition, further customization of the BIF interface / protocol can also be achieved when using an FPGA. Furthermore, the FPGA offers the flexibility for customers to even integrate other functions within the same low power FPGA device. By using a low power FPGA as a companion chip to the application processor, handset manufacturers can enable cutting edge features / standards into their products on demand to create clear product differentiation.
Loss of flexibility due to unsupported standards by chipset vendors
Although system-on-a-chip and holistic integration are the mantras of most chipset manufacturers, chipsets are often designed to meet broad market needs and therefore may not support certain standards. This denies handset system architects valuable flexibility. Also, as new standards are adopted by chipset manufacturers, they often completely drop older ones from their portfolio. This again takes away valuable flexibility from both the system architect and the component procurement teams of handset manufacturers. Often in such cases, system architects may want to use the latest chipset solutions based on their merits, while the procurement team may wish to continue using certain older standards, even if not supported by the latest chipsets, to provide supply flexibility. Here again FPGAs provide considerable value.
Figure 2 illustrates how a low cost, low power FPGA can be used to regain design flexibility by providing an easy way to bridge between two different standards.
This figure illustrated how a terrestrial TV broadcast tuner chip with a custom interface can be used with an applications processor that does not support that interface. Figure 2 shows the host interface through the SPI bus that is commonly available in application processors. Here again, communication to the application processor can be customized as needed when using a FPGA.
Sensor management
The number of sensors included in smartphones has grown dramatically. High-end smartphones include several sensors like gyroscope, multiple cameras, touch, accelerometers, magnetometers, an ambient light sensor, and GPS, among others. In the future, phones are expected to be even more aware of their surroundings (sensing altitude, temperature, humidity, etc.) while providing more value-added features such as the monitoring of human vital signs.
The proliferation of sensors has a profound impact on the user experience. For example, most smartphone users can confirm that the use of GPS navigation has a direct and noticeable impact on battery life. In addition, some smartphone operating systems mandate the frequency of polling from certain critical sensors, such as touch. Touch sensors may need to be polled at frequencies of several hundred KHz to ensure a compelling user experience. In architectures where the application processors are connected to sensors directly, sensors need to be actively managed by the application processor(s), which has a direct impact on power consumption.
Figure 3 illustrates an implementation of a low power FPGA used as a companion chip to the application processor to manage sensors in a mobile platform. Independent I2C masters may be used to manage different sensors to ensure the right throughput is achieved from each sensor. Sensors, such as touch, that require higher throughput may be interfaced to the FPGA using an independent I2C bus, if required.
The smart sensor hub may be designed with intelligence to aggregate interrupts generated from different sensors and, based on pre-defined conditions, to interrupt the application processor. This design approach would enable the application processor to go into a standby state for longer periods of time and thereby reduce power consumption, or would free the application processor to perform other important tasks.
Conclusion
The mobile handset market is extremely competitive, with many handset models offered by multiple manufacturers. The product development cadence of handset manufacturers is different from those of chipsets or application processors. In some cases, this creates a bottleneck for handset manufacturers to enable cutting edge features in their products on demand.
In addition, product differentiation has become a key challenge that is magnified because handsets using the same operating system appear to deliver a similar user experience to consumers. Therefore, handset manufacturers use hardware features to differentiate their products. Handset system architects are constantly trying to strike a balance among new feature inclusion, reducing power consumption and keeping cost in check.
In such a dynamic environment, low cost, low power FPGAs, such as the iCE40 devices offered by Lattice Semiconductor, are a perfect choice to help handset architects design new features to differentiate their products.
About the author
Subra Chandramouli is a Sr. Marketing Manager in the Consumer/Mobility Business Unit at Lattice Semiconductor. He has been working in the mobile handheld industry for the last 14 years. Prior to joining Lattice, Subra was a successful entrepreneur and has also worked at Cypress semiconductors and Intel Corporation.
Subra has one patent and four patent applications on file, all in the field of Flash memory design. He has an MBA from Duke University and a M.S.EE from Wright State University, Ohio.
If you found this article to be of interest, visit Programmable Logic Designline where you will find the latest and greatest design, technology, product, and news articles with regard to programmable logic devices of every flavor and size (FPGAs, CPLDs, CSSPs, PSoCs...).
Also, you can obtain a highlights update delivered directly to your inbox by signing up for my weekly newsletter – just Click Here to request this newsletter using the Manage Newsletters tab (if you aren't already a member you'll be asked to register, but it's free and painless so don't let that stop you [grin]).
Asynchronous product development cycles within the handset industry
Readers of this article may not be surprised to learn that the product design life cycles of mobile handset and chipset vendors are fundamentally different. It is fairly common to see new phone models being introduced every other month, while chipset vendors release newer versions of their chipsets in a much slower product cycle cadence. While there are solid and obvious reasons for this, the challenge faced by handheld system architects is also real; i.e. keeping up with product innovation cycles that are faster than what the chipset vendors are capable of supporting. A good example of this is the recent announcement of the MIPI battery interface (BIF) standard.
The MIPI battery interface (BIF) standard
The use of dual-core and quad-core processors, along with the marketing imperative to create a compelling user experience, increases power consumption that has direct downstream effects on power delivery, battery life and longevity. Striking a balance among optimal power delivery, battery capacity, chemistry, safety, and form factor is a significant design challenge. The communication protocol established by MIPI-BIF provides a method for system designers to read parameters on demand to optimize power consumption during device use and to optimize battery charging. It also provides a method to authenticate batteries for systems that need to ensure user safety. Although the MIPI standard has already been announced, chipset vendors will still need time to adopt this standard in their products. However, handset designers may want to take advantage of MIPI-BIF much sooner. Programmable logic devices are perfectly suited in such situations, because they enable mobile system architects to adopt new standards using existing chipset or application processors. In fact, soon after MIPI released the BIF standard, Lattice Semiconductor announced its support for the standard and that it is engaged with key customers on implementing it.
Figure 1 illustrates the use of a low cost, low power FPGA to create a bridge between an existing application processor and the recently released MIPI-BIF standard. Communication over the BIF battery communication line (BCL) is enabled using the low power FPGA. On the application processor side, I2C, because it is commonly available, is a natural choice to connect the host application processor to the FPGA. A simple protocol is defined on top of the I2C standard to communicate between the host and the FPGA.
Figure 1. Using a low power FPGA to implement new standards
If needed, the host interface can be easily customized using the FPGA solution. In addition, further customization of the BIF interface / protocol can also be achieved when using an FPGA. Furthermore, the FPGA offers the flexibility for customers to even integrate other functions within the same low power FPGA device. By using a low power FPGA as a companion chip to the application processor, handset manufacturers can enable cutting edge features / standards into their products on demand to create clear product differentiation.
Loss of flexibility due to unsupported standards by chipset vendors
Although system-on-a-chip and holistic integration are the mantras of most chipset manufacturers, chipsets are often designed to meet broad market needs and therefore may not support certain standards. This denies handset system architects valuable flexibility. Also, as new standards are adopted by chipset manufacturers, they often completely drop older ones from their portfolio. This again takes away valuable flexibility from both the system architect and the component procurement teams of handset manufacturers. Often in such cases, system architects may want to use the latest chipset solutions based on their merits, while the procurement team may wish to continue using certain older standards, even if not supported by the latest chipsets, to provide supply flexibility. Here again FPGAs provide considerable value.
Figure 2 illustrates how a low cost, low power FPGA can be used to regain design flexibility by providing an easy way to bridge between two different standards.
Figure 2. Low power FPGA used as an interface bridge.
This figure illustrated how a terrestrial TV broadcast tuner chip with a custom interface can be used with an applications processor that does not support that interface. Figure 2 shows the host interface through the SPI bus that is commonly available in application processors. Here again, communication to the application processor can be customized as needed when using a FPGA.
Sensor management
The number of sensors included in smartphones has grown dramatically. High-end smartphones include several sensors like gyroscope, multiple cameras, touch, accelerometers, magnetometers, an ambient light sensor, and GPS, among others. In the future, phones are expected to be even more aware of their surroundings (sensing altitude, temperature, humidity, etc.) while providing more value-added features such as the monitoring of human vital signs.
The proliferation of sensors has a profound impact on the user experience. For example, most smartphone users can confirm that the use of GPS navigation has a direct and noticeable impact on battery life. In addition, some smartphone operating systems mandate the frequency of polling from certain critical sensors, such as touch. Touch sensors may need to be polled at frequencies of several hundred KHz to ensure a compelling user experience. In architectures where the application processors are connected to sensors directly, sensors need to be actively managed by the application processor(s), which has a direct impact on power consumption.
Figure 3 illustrates an implementation of a low power FPGA used as a companion chip to the application processor to manage sensors in a mobile platform. Independent I2C masters may be used to manage different sensors to ensure the right throughput is achieved from each sensor. Sensors, such as touch, that require higher throughput may be interfaced to the FPGA using an independent I2C bus, if required.
Figure 3. Using an FPGA as a smart sensor hub.
The smart sensor hub may be designed with intelligence to aggregate interrupts generated from different sensors and, based on pre-defined conditions, to interrupt the application processor. This design approach would enable the application processor to go into a standby state for longer periods of time and thereby reduce power consumption, or would free the application processor to perform other important tasks.
Conclusion
The mobile handset market is extremely competitive, with many handset models offered by multiple manufacturers. The product development cadence of handset manufacturers is different from those of chipsets or application processors. In some cases, this creates a bottleneck for handset manufacturers to enable cutting edge features in their products on demand.
In addition, product differentiation has become a key challenge that is magnified because handsets using the same operating system appear to deliver a similar user experience to consumers. Therefore, handset manufacturers use hardware features to differentiate their products. Handset system architects are constantly trying to strike a balance among new feature inclusion, reducing power consumption and keeping cost in check.
In such a dynamic environment, low cost, low power FPGAs, such as the iCE40 devices offered by Lattice Semiconductor, are a perfect choice to help handset architects design new features to differentiate their products.
About the author
Subra Chandramouli is a Sr. Marketing Manager in the Consumer/Mobility Business Unit at Lattice Semiconductor. He has been working in the mobile handheld industry for the last 14 years. Prior to joining Lattice, Subra was a successful entrepreneur and has also worked at Cypress semiconductors and Intel Corporation.
Subra has one patent and four patent applications on file, all in the field of Flash memory design. He has an MBA from Duke University and a M.S.EE from Wright State University, Ohio.
If you found this article to be of interest, visit Programmable Logic Designline where you will find the latest and greatest design, technology, product, and news articles with regard to programmable logic devices of every flavor and size (FPGAs, CPLDs, CSSPs, PSoCs...).
Also, you can obtain a highlights update delivered directly to your inbox by signing up for my weekly newsletter – just Click Here to request this newsletter using the Manage Newsletters tab (if you aren't already a member you'll be asked to register, but it's free and painless so don't let that stop you [grin]).
Navigate to related information


Dr DSP
5/21/2012 10:49 AM EDT
Are there any plans to make the BIF Master design available as IP? Seems like a natural.
Sign in to Reply
brianlk
5/22/2012 4:38 PM EDT
Yes, we do plan on offering BIF master IP under NDA with our customers who meet MIPI’s legal criteria.
Sign in to Reply
cedricfau
5/22/2012 6:44 PM EDT
Do you have examples of current mobile chipset including such kind of FPGA ?
What is the cost of such FPGA in a chipset ?
Sign in to Reply
Subrac
5/25/2012 5:14 PM EDT
Firstly, I’d like to say that programmable chips are being used as companion chips to mobile chipsets in systems. Programmable chips are not a part of the mobile chipset itself.
There are several commercially available mobile devices that use Lattice programmable devices. I can share with you some publicly available teardown reports that have programmable chips from Lattice as examples, below. With regards to your question of price, there are several variables that influence the price of our products. Depending on the functionality required, we have a range of products that are priced anywhere from under $1 to few dollars while meeting the basic low cost, low power requirements of mobile applications.
1. http://www.techrepublic.com/photos/cracking-open-the-2011-barnes-noble-nook-e-book-reader-wi-fi/6243892?seq=36&tag=thumbnail-view-selector;get-photo-roto : Image 36 of 44
2. http://www.techrepublic.com/photos/samsung-focus-windows-phone-7-teardown/492287?seq=50&tag=content;siu-container#photopaging: Image 50 of 67
3. http://www.eetimes.com/General/DisplayPrintViewContent?contentItemId=4207606
-Subra
Sign in to Reply
Max the Magnificent
5/26/2012 11:32 AM EDT
Your URLs seem to be messed up somehow -- try the following instead:
http://www.techrepublic.com/photos/cracking-open-the-2011-barnes-noble-nook-e-book-reader-wi-fi/6243892?seq=36&tag=thumbnail-view-selector;get-photo-roto (Image 36 of 44)
http://www.techrepublic.com/photos/samsung-focus-windows-phone-7-teardown/492287?seq=50&tag=content;siu-container#photopaging (Image 50 of 67)
http://www.eetimes.com/General/DisplayPrintViewContent?contentItemId=4207606
Sign in to Reply
cedricfau
5/30/2012 8:44 AM EDT
Thank you Subra and Max for sharing this information. This is a very interesting topic.
Sign in to Reply