Most recent activity
-
- 3 comments
- 767 views
-
-
-
-
I was actually replying to @user134951 :D
With regard to your question on comms with the internet, Gordon answered a similar question: http://forum.espruino.com/conversations/309832/
-
You'd be surprised that even the computer you're using has an opaque, second "brain" that nobody except the manufacturer has any idea of what it's doing (maybe even tracking you?) https://en.wikipedia.org/wiki/Intel_Management_Engine
-
I would liken this to saying operating systems based on Linux are open source, except when you start adding binary blobs like nvidia or printer drivers.
You can recompile Espruino to not use bluetooth (for example the stm32 ones don't have bluetooth) but the watch won't be as functional (e.g. no app store, no wireless comms).
Nordic is the manufacturer of the microprocessor that powers the watch, and they also provide the bluetooth stack. Since they are the manufacturer, the Nordic provided bluetooth stack works best with the chip, similar to how nvidia drivers have better support than the nouveau reverse engineered drivers.
Another tricky thing for opensource products working with wireless comms would be compliance. If you use the Nordic sdk, you can mention that in your product docs and the certification officials would know what to do (since a lot of products with the Nordic chips would usually use the sdk and they would have experience with it). If you don't, you're in for a more grueling (and possibly more expensive) certification process since you'll need to ensure your wireless energy signals don't go beyond what local laws require. Since Espruino can be used in consumer products (the only one that comes to mind right now is https://lab.ruuvi.com/espruino/ ) the product manufacturers benefit from this as well.
-
The neopixels require fast pulses, and the usual way firmware for microcontrollers do it is to ride on I2S (instead of bitbanging gpio).
I2S usually need both SCK and LRCK defined, but the nRF52832 didn't need the LRCK pin defined. However after some testing (and a trip to the nordic forums) it seems it is indeed required.
What I meant by not accidentally using it is that since with nRF52 you can assign devices their pins, if you put LRCK it on an exposed pin, you might accidentally connect it to your circuit and have a really awful time debugging :P
-
In this case, http://forum.espruino.com/comments/15562682/ and building the hex file with this board def works for me
Edit: just saw that fanoush mentioned it's not a good idea. I guess you can just pick any pin that's free (for the dongle, maybe one that's on a pad underneath so you don't accidentally use it?)
Just wanted to mention that Seeed Studio put an NRF52840 in the XIAO form factor:
https://www.seeedstudio.com/Seeed-XIAO-BLE-nRF52840-p-5201.html
Would be a good stopgap until we finally get an official MDBT50Q breakout with Espruino programmed in, if only it's in stock :P