- Oct 14, 2015
-
-
Cristian Maglie authored
-
- Sep 23, 2015
-
-
Paolo Paolucci authored
-
- Sep 04, 2015
-
-
Cristian Maglie authored
-
Cristian Maglie authored
-
Cristian Maglie authored
-
Cristian Maglie authored
-
Cristian Maglie authored
Fixes #30
-
Cristian Maglie authored
-
Cristian Maglie authored
See #30
-
- Aug 25, 2015
-
-
Sandeep Mistry authored
-
- Aug 24, 2015
-
-
Cristian Maglie authored
-
- Aug 19, 2015
-
- Aug 14, 2015
-
-
Martino Facchin authored
calling digitalWrite with any value different from 0 will end in performing digitalWrite(HIGH)
-
- Aug 13, 2015
-
-
Cristian Maglie authored
In the wire library there are several functions where an unnecessarily complex coding has been used: - endTransmission: the availability of data is already checked in while(...), therefore need not be checked again in the loop. - requestFrom: the for-loop has a predefined and fixed number of loops. Therefore a check whether the last element has been reached is unnecessary and does not add any benefit. Fixes #20
-
Cristian Maglie authored
-
Thibaut VIARD authored
-
Thibaut VIARD authored
-
Cristian Maglie authored
Fix for deadlock conditions after i2c bus errors
-
- Aug 11, 2015
-
-
Thibaut VIARD authored
-
Thibaut VIARD authored
-
- Aug 10, 2015
-
-
Thibaut VIARD authored
-
Thibaut VIARD authored
-
Thibaut VIARD authored
-
- Jul 25, 2015
-
-
Erin Tomson authored
The first occurs when starting a read transaction from a slave that doesn't respond. The code would wait until the SB (slave on bus) bit is set in the INTFLAGS register, but when a nack occurs that never happens so we're stuck in an infinite loop. The fix is to also look for the MB flag to be set. If it is, issue a stop condition and return. The second happens when a bus error (ie, an illegal stop condition) occurs while sending data as a master. In that case we are waiting for the MB (master on bus) flag to be set. When a bus error occurs that never happens, so again we end up in an infinite loop. The fix here is to also look for the BUSERR flag to be set. If it is, return an error condition.
-
- Jul 23, 2015
-
-
Martino Facchin authored
the function returned 1 millisecond after the required time
-
- Jul 21, 2015
-
-
Cristian Maglie authored
-
Cristian Maglie authored
-
Cristian Maglie authored
- Jul 18, 2015
-
-
Cristian Maglie authored
Close #5
-
- Jul 17, 2015
-
-
Cristian Maglie authored
-
Cristian Maglie authored
-
Cristian Maglie authored
See https://github.com/arduino/Arduino/pull/2175 Quoting the original commits from Matthijs Kooijman: Enable C++11 support This uses the gnu++11 standard, which is C++11 with GNU extensions. C++11 should be full compatible with the previously used C++98 standards, so all pre-existing sketches should continue to work. Enable C11 support This uses the gnu11 standard, which is C11 with GNU extensions. Previously, gnu89 was being used, which is pretty ancient by now. C99 brings some important improvements, some of which were already available and used even without this option. C11 is more recent and brings more minor improvements. Most notable feature is the static_assert statement, allowing checking invariants at compiletime using the full C expressions.
-
- Jul 06, 2015
-
-
Cristian Maglie authored
-
Cristian Maglie authored
-
PaoloP74 authored
-
PaoloP74 authored
-
- Jul 05, 2015
-
-
Cristian Maglie authored
This fix lock-ups on UART errors (for example when disconnecting and reconnecting RX/TX wires or if the method Serial.begin is called while another device is already transmitting).
-