mjb/altos/src/drivers/ao_rn4678.c, branch 1.9AltOS - the operating system for Altus Metrum products
https://git.ethernal.org/mjb/altos/atom?h=1.92018-10-13T15:23:25+00:00altos: Eliminate 'pin' field from GPIO functions2018-10-13T15:23:25+00:00Keith Packardkeithp@keithp.com2018-09-11T17:40:24+00:00urn:sha1:cdaa0d7b272505c49017f409b7c0b8e3240608f0
This was used with the 8051 bit-addressing mode to provide
single-instruction access to GPIO pins.
Signed-off-by: Keith Packard <keithp@keithp.com>
altos/rn4678: Add BLE support2017-06-20T18:19:40+00:00Keith Packardkeithp@keithp.com2017-06-20T18:19:40+00:00urn:sha1:ea7e236e75452e27f3af6730a0542850851eb23d
This just means ignoring the BLE connect status message.
Signed-off-by: Keith Packard <keithp@keithp.com>
altos: Add timeout to RN4678 status message code2017-06-13T17:34:03+00:00Keith Packardkeithp@keithp.com2017-06-13T17:34:03+00:00urn:sha1:cd8b22bef0a88ed6881036b4c6718a4e33c55d41
If we see the start of an RN4678 status message, but then output
pauses, assume that this isn't the start of a status message and flush
the pending data.
Signed-off-by: Keith Packard <keithp@keithp.com>
altos/ao_rn4678: Send '$$$' for new devices. Fix name setting code.2017-05-15T15:59:52+00:00Keith Packardkeithp@keithp.com2017-05-15T15:59:52+00:00urn:sha1:ab50a1467bac0234062bc8c0a17783f1730aa981
New devices won't respond to the cmd pin we have configured, so get
them to command mode by sending the $$$ string. Somehow I'd botched
the name setting code and hadn't caught it as I hadn't tried a new
device...
Signed-off-by: Keith Packard <keithp@keithp.com>
altos: Add RN4678 Bluetooth module driver2017-05-13T22:29:13+00:00Keith Packardkeithp@keithp.com2017-05-13T22:17:41+00:00urn:sha1:6442e2ad6af4b337348aa2ce25abc91c05765826
This works much like the old BTM module, but supports both bluetooth
and bluetooth LE. I've poked at it briefly over BTLE to see that it
appears to have the right name, but haven't attempted to communicate
over BTLE yet.
Signed-off-by: Keith Packard <keithp@keithp.com>