Most recent activity
-
can you use
process.env.BOARD? -
check this link NRF51TAG.py
In case the space is tight it should be possible to remove GRAPHICS from there as it may not be that much useful on beacon/tag? Also there are 16 pages reserved for bootloader. If flashing via SWD is possible, removing that from line 55 and 58 could give more space for code or storage.
-
yes, that's normal, they are all like that, also other watches with round shape are designed like that
-
not solution but maybe workaround or thing to check - you can retype the array as Uint8Array in place (they share same memory) and see how that one gets written or check how it compares to 'bad' file you have.
>var d8 = new Uint8Array(d.buffer)or even check
d.buffer- that will be probably the same byte array as d8 would be -
Cool, thanks. Wondering how micropython port is done regarding cmake, did you check how they solved it?
Maybe the SDK is just bunch of sources and headers like nordic SDK, could it work without cmake at all? But that would mean all needed files would need to be listed like e.g. in https://github.com/espruino/Espruino/blob/master/make/common/NRF5X.make + https://github.com/espruino/Espruino/blob/master/make/family/NRF52.make for nrf52 port, which is a pain. Or you mean you can generate that one via cmake (once? at provision.sh step?) so it can be included like NRF5X.make is? -
20 bytes is maximum in BLE unless both devices agree on bigger MTU size or support DLE - data length extension. and yes bigger MTU would need different build of espruino with less memory available. also before DLE or larger MTU was added to bluetooth standard, there were so called long writes, nice summary also here https://github.com/NordicSemiconductor/Android-BLE-Library/issues/3
-
missing 0x2A02 0x2A03 and 0x2A05, their value is not used
the first two are mentioned here https://devzone.nordicsemi.com/f/nordic-q-a/26129/add-peripheral-privacy-flag-and-reconnection-address-characteristics-to-generic-access-service-in-nrf52832 this is something that was removed from bluetooth specs, I still don't know what it actually does - something about secure connections when address is changing?
0x2A05 is service changed, that should allow updating list of services, characteristics without need to disconnect and reconnect when implemented properly, was already discussed here http://forum.espruino.com/conversations/357737/
-
Watched full video, the UI is very nice, full touch with such UI design feels natural. This really looks professional, you would not have guessed there is javascript interpreter behind it :-) Native firmware in some watches feels slower and less polished than this.
say a dsd6 inside the helmet only for receiving alarms from its buzzer
BTW I still have plenty of them, if anyone wants some DS-D6 I can ship them relatively cheap (e.g. two for 15 eur including registered EU shipping, shipping is almost a fixed cost at this weight so more can get cheaper). Got carried away when they were cheap and won't really have a chance to use them all :-) Still new in box. Also have few others (DK08,F07,HX03W). If anyone is interested just PM me. Otherwise sorry for spam.
-
do you have pull ups on the pins? 4.7k seems to be typical value. also can you paste your i2c code that is still not working?
what you mean by native firmware calls (that bypasses the javascript interpreter entirely)? can you provide example of what you think is not possible/available?