Why Did Ambiq Micro Select HiFi-5 DSP IP for Next Generation MCU?
Ambiq Micro has built a family of voice processing MCU dedicated to battery powered, energy sensitive systems, supporting mobile application like wearable. The company is facing two strong challenges: support computationally intensive processing (NN-based far field) and speech recognition algorithms, while offering “ultra-low power” devices. When Ambiq claim to build ultra-low-power devices, it’s really the case: the company has developed a unique and proprietary technology, the Subthreshold Power Optimized Technology (SPOT™) platform (SPOT architecture uses transistors biased in the subthreshold region of operation).
These two challenges are clearly in contradiction: intensive processing built in energy-sensitive devices, this sounds like the perfect definition of energy-efficiency! According with Aaron Grassian, VP of marketing, Ambiq Micro, “Porting the HiFi 5 DSP to Ambiq Micro’s SPOT platform enables product designers, ODMs and OEMs to take the most advantage of technology from audio software leaders like DSP Concepts and Sensory by adding voice assistant integration, command and control, and conversational UIs to portable, mobile products without sacrificing quality or battery life.”
To read the full article, click here
Related Semiconductor IP
- Tensilica HiFi 4 DSP
- Spatial Audio & Head Tracking Solution
- Tensilica HiFi 3z DSP
- Versatile, Ultra-Low-Power DSP for Audio, Voice, Vision, and AI
- Tensilica HiFi 5s DSP
Related Blogs
- Adding DSP hardware shrinks energy for MCU core
- Is Altera Looking At Programmable DSP?
- Jeff Bier's Impulse Response - The Rise of Licensable Cores
- Oxford Digital Offers Small Audio DSP Core With Graphical Programming
Latest Blogs
- Beyond Trusted: What the NSA’s New Guidance Means for Hardware Security
- A scalable, shader-programmable vector graphics GPU core for low-power MCUs
- Navigating ISO 26262 Part 11: A Guide for Semiconductor Architects
- Embedded Security explained: Digital signatures
- Hardware security verification must go beyond functional testing