Nordic "Thingy" kit

[espruino-discuss]

Posted at 2017-06-22 by @yerpj

Any support planned for the Nordic Thingy dev kit? https://www.nordicsemi.com/eng/Products/Nordic-Thingy-52

It runs on nRF52832.

[espruino-discuss]

Posted at 2017-06-22 by @gfwilliams

Looks like a neat little device!

To be honest the standard nRF52832DK build might well work on it as-is - on other devices Nordic have tended to use the same pins for the UART, so if they've done the same on here you'd be sorted.

---

Posted at 2017-06-22 by tom.gidden

Mmm.. it's like a Puck, but huge and ugly.

They've posted some Node.js code to operate with the default firmware: https://github.com/NordicSemiconductor/Nordic-Thingy52-Nodejs/blob/master/lib/thingy.js

It might be good to try to match the same services and characteristics they're using for their sensor, to get a Puck acting like a Thingy:52 as far as their official App is concerned.

---

Posted at 2017-06-23 by @gfwilliams

That's a good idea - and then you'd get their IFTTT bridge thing I guess?

---

Posted at 2017-06-26 by @yerpj

That would be a nice to have indeed! I will keep this idea in mind for later.

@gfwilliams I know that unofficial boards may not benefit from any support, but I ask the question anyway (it might also be helpful for Puck.js users): Is there a way of flashing the .hexover OTA or do we absolutely need to give it a .zip archive? nightly builds for the NRP52 kit seems to be .hexonly...

---

Posted at 2017-06-26 by @gfwilliams

I just copy the hex onto the JLINK USB drive.

On the nRF52DK builds there is no bootloader, so it won't do OTA at all (even with a zip). It's a complete pain to get working and requires an encryption key and two separate builds (one bootloader, one firmware), so for a devboard I just skip it :)