We asked – does ARM indemnify licensees against patent suits?

We emailed ARM and asked their legal folks a few questions. Mostly to understand if it makes any sense to license from ARM if patent trolls can just go after companies for selling a product that had ARM IP in it.

Why does this matter for hardware developers? When designing chips, engineers have a choice of what core to base their ASIC off of. (Yes, sometimes its a fully custom core, but that’s not terribly common when a microcontroller core is needed). There’s a few common licensable cores people use that we’ve seen: the classic 8051, Tensilica, RISC V and ARM. As far as we can tell, ARM does not actually fabricate or design any silicon on their own – its a pure IP licensing holding company. According to this SEC filing by ARM (hat tip to ZDnet’s article here, which is a great overview of ARM)

     We take great care to establish and maintain the proprietary integrity of our products. We focus on designing and implementing our products in a “cleanroom” fashion, without the use of intellectual property belonging to other third parties, except under strictly maintained procedures and express license rights. In the event that we discover that a third party has intellectual property protections covering a product that we are interested in developing, we would take steps to either purchase a license to use the technology or work around the technology in developing our own solution so as to avoid infringement of that other company’s intellectual property rights. Notwithstanding such efforts, third parties may yet make claims that we have infringed their proprietary rights, which we would defend.

From the filing declaration, ARM states that upon a 3rd party claiming IP rights over their products, they will either purchase a license, or work around the technology to avoid infringement.

Given the lawsuit filed by Altair Logix is claiming IP rights over a part of the ARM Cortex A9 processor design, we thought this would be a great way to find out if ARM really defends or indemnifies their sub-licensees or if that is not part of the price for licensing ARM core designs. If so, that’s awesome and a great reason to use ARM cores! If not, then designers need to make sure that they have a clause in their licensing contracts that require ARM to indemnify the client and if they’re not willing to do so, find another core to license!

Here is what we sent over to ARM’s legal.

1) Has ARM had a chance to look at the suit that was filed against SparkFun?
https://www.sparkfun.com/news/3917

2) Does ARM think this suit has any merit?

3) Has ARM licensed this IP for use in their cores?

4) When companies license ARM for their microcontroller or microcomputer cores, does ARM indemnify the licensee against patent suits?


The response we received for all four questions was:

“Arm does not comment on pending litigation”


The board in question was made by pcDuino (we emailed pcDuino, no reply). The chip on the board is a Freescale i.MX6 SoC 1.2GHz ARM Cortex A9 Quad Core made by NXP.

The ARM core is licensed to NXP, and there may be some contract that indemnifies NXP since the whole point of licensing from ARM is to license the IP and not worry about patent suits. We’ll never know what agreements ARM and NXP have, and there may or may not be indemnification for NXP and/or chip reseller and pcDuino contracts.

All that said, it seems like ARM should step in and invalidate the patent or assist with this lawsuit. According to the SEC filing by ARM, that is what they say they will do.

” In the event that we (ARM) discover that a third party has intellectual property protections covering a product that we are interested in developing, we would take steps to either purchase a license to use the technology or work around the technology in developing our own solution so as to avoid infringement of that other company’s intellectual property rights. Notwithstanding such efforts, third parties may yet make claims that we have infringed their proprietary rights, which we would defend.”


Adafruit publishes a wide range of writing and video content, including interviews and reporting on the maker market and the wider technology world. Our standards page is intended as a guide to best practices that Adafruit uses, as well as an outline of the ethical standards Adafruit aspires to. While Adafruit is not an independent journalistic institution, Adafruit strives to be a fair, informative, and positive voice within the community – check it out here: adafruit.com/editorialstandards

Happy New Year 2025
Happy New Year from Adafruit!

Stop breadboarding and soldering – start making immediately! Adafruit’s Circuit Playground is jam-packed with LEDs, sensors, buttons, alligator clip pads and more. Build projects with Circuit Playground in a few minutes with the drag-and-drop MakeCode programming site, learn computer science using the CS Discoveries class on code.org, jump into CircuitPython to learn Python and hardware together, TinyGO, or even use the Arduino IDE. Circuit Playground Express is the newest and best Circuit Playground board, with support for CircuitPython, MakeCode, and Arduino. It has a powerful processor, 10 NeoPixels, mini speaker, InfraRed receive and transmit, two buttons, a switch, 14 alligator clip pads, and lots of sensors: capacitive touch, IR proximity, temperature, light, motion and sound. A whole wide world of electronics and coding is waiting for you, and it fits in the palm of your hand.

Have an amazing project to share? The Electronics Show and Tell is every Wednesday at 7:30pm ET! To join, head over to YouTube and check out the show’s live chat and our Discord!

Join us every Wednesday night at 8pm ET for Ask an Engineer!

Join over 38,000+ makers on Adafruit’s Discord channels and be part of the community! http://adafru.it/discord

CircuitPython – The easiest way to program microcontrollers – CircuitPython.org


New Products – Adafruit Industries – Makers, hackers, artists, designers and engineers! — New Products 11/15/2024 Featuring Adafruit bq25185 USB / DC / Solar Charger with 3.3V Buck Board! (Video)

Python for Microcontrollers – Adafruit Daily — Python on Microcontrollers Newsletter: A Fabulous Year for Python on Hardware and Much More! #CircuitPython #Python #micropython @ThePSF @Raspberry_Pi

EYE on NPI – Adafruit Daily — EYE on NPI Maxim’s Himalaya uSLIC Step-Down Power Module #EyeOnNPI @maximintegrated @digikey

Adafruit IoT Monthly — The 2024 Recap Issue!

Maker Business – Adafruit Daily — Same-day delivery, not for convenience, but customer loyalty

Electronics – Adafruit Daily — Level Conversion Hack

Get the only spam-free daily newsletter about wearables, running a "maker business", electronic tips and more! Subscribe at AdafruitDaily.com !


3 Comments

  1. That’s an excellent (and complex) topic!

    I am not a lawyer but I believe you misinterpreted the wording of the ARM SEC filing:

    “In the event that we discover that a third party has intellectual property protections covering a product THAT WE ARE INTERESTED IN DEVELOPING, we would take steps to either purchase a license to use the technology or work around the technology in developing our own solution so as to avoid infringement of that other company’s intellectual property rights.”

    They are saying that PRIOR to developing a new product, they will do a patent landscape analysis, and if they find existing patents they may run into, they will try to either work around them or seek to license them (if they have no good work around). They are also implying that they have done their homework and have reduced the risk of later infringement lawsuit to the best of their ability (this is an SEC filing – which is all about risk).

    This part does not apply to a third-party claiming infringement, which would happen AFTER they develop and sell products. Instead, that case is addressed in the last sentence:

    “Notwithstanding such efforts, third parties may yet make claims that we have infringed their proprietary rights, which we would defend.”.

    They are basically saying that in the (unlikely and unexpected) case where they get sued for infringement, they will defend themselves through whatever means possible. At that point, they can’t really work around it (it is usually committed in silicon – too late for a workaround) and any license fee is likely to be exorbitant (that’s why there is a lawsuit), unlike a license established prior to development, on friendly terms.

    This doesn’t take away from the discussion on liability, which is buried deep into the various contracts along the supply chain and generally impossible for an end-user to figure out.

  2. That was the response I’d expect. Very few companies would step into the middle of a lawsuit unless it is financially or strategically compelling. And even if that is the case they’re not going to talk about it until they’ve got their legal plans set.

  3. The wolrd would be a better place without patent trolls.

Sorry, the comment form is closed at this time.