Tech News: Arduino & Qualcomm

Unless you have been living under a rock, you would have heard this week that Qualcomm announced it will acquire Arduino. I have mixed feelings about it. Probably one of the most celebrated Open source companies gets bought by one of the most closed source hardware chip company ever!

It says Arduino keeps its brand, tools, and open-source mission. But knowing Qualcomm, I don’t have high hopes. They technically have been one of the worst offenders when it comes to putting detailed specs of devices out there. Their documentation is poor, it is always under NDAs, and they have this unspoken rule of not responding to folks who have a non-business ID when you reach out via mails. I desperately hope they prove me wrong this time with Arduino.
Along with this news, they also shipped an Arduino UNO form factor board “UNO Q”. It has a Debian-running Qualcomm Dragonwing QRB2210 application processor with an STM32U585 microcontroller for doing the low level IO. You get 2 GB RAM, 16 GB eMMC, Wi-Fi 5, Bluetooth 5.1(WCBN3536A – Qualcomm Chip), and video output over USB-C. Processor-wise, performance seems to be in the RPi-3 range of things. It’s supposed to be in the “AI for Edge” specific applications. QRB2210 has quad-core 2.0 GHz A53 CPU, Adreno GPU and Dual Camera ISP so can be good for Robotics and Vision IoT stuff. But not sure if it’s a right move when RPi already dominates this range.

It seems to have a new software IDE called Arduino AppLab which is a hybrid for doing Python development for the DragonWing and Arduino sketches for the STM32. Will need to try it out once the board arrives. Anyway, I checked the website documentation, schematic of the board is available (Layout Gerber is available but not the design files). As usual, nothing on the Qualcomm chip used on the board. Hopefully they make this chip atleast available to the public.
 
I just long for a day when I can read up and buy a single unit Qualcomm chip from a reseller without signing an NDA or reaching out to a sales rep. Then I will believe that this acquisition was different!  

If you liked the post, Share it with your friends!

Tech News: EU Cyber Resiliency Act(CRA)

Came across the European Union law which will impact any products you plan to manufacture and sell in EU. I have tried to summarize whatever I have understood below.

CRA is an EU law for products with digital elements. If you ship hardware with firmware into the EU, you’re in scope. It entered into force in Dec 2024. Reporting starts on Sep 2026. Most requirements apply from Dec 2027. Cybersecurity becomes part of CE. It will be mandatory for your product to be “CE” compliant.

If you are building a product, then you are mandated to do a cybersecurity risk assessment and build to it. You would have to keep an update path that can push security patches quickly and, by default, automatically with an opt-out if users wish to. You should provide security updates free of charge during your support period. Support periods are to be around 5yrs for consumer gear (Unless expected usage time is shorter) and longer for industrial. Your technical file must prove all of this for CE.

For hardware teams, the first practical step is to map your device to the CRA lists. Annex III in the bill names important product categories. If you make routers or modems, operating systems on devices, microcontrollers or FPGAs with security functions, or smart home locks and cameras, you likely sit in Class I. Firewalls and tamper-resistant microcontrollers fall into Class II. Class II expects a third-party assessment path such as EU-type examination plus production control. If it’s not in any of these, you can do self assessment. Read the document properly.

There is some leniency for FOSS non-commercial projects or if your product is in alpha/beta prototype stage.

If you liked the post, Share it with your friends!
1 21 22 23 24 25 142