4 ms·

The system-on-chip is the MGM210L which needed to be powerful enough to run multiple wireless protocols (Zigbee, Thread, Bluetooth), so the lamp can be controll

• oaiey 5y ago
  complexity .. maybe, 80Mhz ... heck no. However, this is all off-the-shelf ware and as long as the energy consumption is not a problem, I am fine.
  • marcan_42 5y ago
    It's burst processing. You do actually need high processing speeds for short periods of time to implement network protocols like these effectively. Think cryptography, reliability, etc. The CPU isn't doing anything most of the time, but it makes a big difference if it can get the job done in 500μs instead of 5ms when there is something to do (like process a packet). Also, higher clock speed = lower power consumption. It sounds counterintuitive, but getting the job done quickly so you can go back to low power mode sooner actually saves power, even if the instantaneous power draw while processing is higher.
    • baybal2 5y ago
      Nearly all cryptography on MCUs is hardware based. It would have otherwise be completely impossible to do timing sensitive crypto work like WiFi, or BT. The WiFi, or BT protocol stacks themselves are however almost always in software on MCUs simply because nobody would bother making a separate ASIC IP for that which will be outdated by the next standard errata.
      • marcan_42 5y ago
        Symmetric cryptography is often hardware based, but asymmetric crypto rarely is. The latter is commonly used for pairing/key exchanges, and would be painfully slow on a slow MCU.
• Cthulhu_ 5y ago
  I would have thought they'd have specialized chip hardware already to deal with these, but maybe I don't know enough about that kinda thing. Pretty sure it'd have specialized hardware and/or instructions to deal with the cryptographic aspects though.
  • gtsteve 5y ago
    Baking something like that into hardware is probably not a good idea because then you can't update it when vulnerabilities are found.
    • nekopa 5y ago
      Makes me smile to think that one day my bank account will be drained of all its BTC because I forgot to patch my bedside lamp last tuesday...
      • kwdc 5y ago
        That would make me frown. Just saying.
    • dolmen 5y ago
      But do you get software update (and deployment to your device) when vulnerabilities are found? ;) The real reason is it reduces the cost (and duration) of iterating in the development phase.
      • kmadento 5y ago
        Since Ikea update the firmware of the trådlös units quite often and has security updates in the changelog I would guess... yes They also mentions improvement of stability and performance towards different protocols in the changelogs.
      • elondaits 5y ago
        My Hue lamps had their firmware updated through the app a couple of times, and I had them for 4-5 years.
• baybal2 5y ago
  > The Thread spec for example is hundreds of pages. And this also assured it being dead on arrival.
  • mrb 5y ago
    Actually Thread is alive and kicking! It has a lot of momentum at the moment. But if it gets displaced, IMHO it's going to be by WiFi Ha-Low or successors.
    • baybal2 5y ago
      It is not alive. I haven't seen a single device working with it, while I at least seen one Apple Home compatible device in an Apple store. Tuya on other hand is just in every retail outlet, it's just people don't know that Tuya is under the bonnet.
      • notwedtm 5y ago
        Please stop lying to people: https://www.threadgroup.org/thread-group#OurMembers https://www.threadgroup.org/thread-group#OurMembers
        • baybal2 5y ago
          I am not lying, the assortment of Thread based devices ever seeing sale is much smaller than the size of Thread's illustrious board of directors. They literally have more talkshops per months than devices released.
        • kortex 5y ago
          That just means little more than "who bought or used the spec at some point." It has little bearing on contemporary real-world commercialization of the thread protocol.
      • mrb 5y ago
        Maybe not in your country(?) In the US there are quite a few commercial systems built on Thread: Apple HomePod mini, Google Nest security system, etc. Don't get me wrong: we are still very early in real-world deployments. It was just 2 years ago that the consortium/Google released the open source OpenThread which is when momentum really picked up.
• phkahler 5y ago
  >> The software complexity of these protocols is greater than the complexity of a rudimentary 3D game like Doom That's unfortunate. Protocols, particularly those used for security should be a simple as possible. I know it's a hard problem and people tend to use what is available rather than solving the hard problem.