* commit '71c39489180723b13cabe3c07e3994a239f8a03e':
Updated translations
Updated offline docs
Corrected some email contacts.
MacOS tests fix: new way of discovering work dir conflicts with tests execution. Fixed.
Updated build_pull_request.bash
Renamed mac build from "macosxnew" to "macosx-java-latest"
Updated revision log. Version set to 1.6.0rc3
build.xml and mac. Change in platform names: macosx now macosxnew, oldmacosx now macosx
Fixed bug with paths with spaces
build_pull_requests now builds oldmacosx as well
Macosx: new appbundler, new macosx builds. Use platform=macosx and platform=oldmacosx
build_pull_requests now moves the artifacts to the parent folder: this allows calling "clean" target before each build
build.xml linux-clean target was not deleting old linux builds
Fix typos in BlinkWithoutDelay.ino
Conflicts:
build/build.xml
Previously, the TX pin would be set to output first and then written
high (assuming non-inverted logic). When the pin was previously
configured for input without pullup (which is normal reset state), this
results in driving the pin low for a short when initializing. This could
accidenttally be seen as a stop bit by the receiving side.
By first writing HIGH and then setting the mode to OUTPUT, the pin will
have its pullup enabled for a short while, which is harmless.
Instead of using a lookup table with (wrong) timings, this calculates
the timings in SoftwareSerial::begin. This is probably a bit slower, but
since it typically happens once, this shouldn't be a problem.
Additionally, since the lookup tables can be removed, this is also a lot
smaller, as well as supporting arbitrary CPU speeds and baudrates,
instead of the limited set that was defined before.
Furthermore, this switches to use the _delay_loop_2 function from
avr-libc instead of a handcoded delay function. The avr-libc function
only takes two instructions, as opposed to four instructions for the old
one. The compiler also inlines the avr-libc function, which makes the
timings more reliable.
The calculated timings directly rely on the instructions generated by
the compiler, since a significant amount of time is spent processing
(compared to the delays, especially at higher speeds). This means that
if the code is changed, or a different compiler is used, the
calculations might need changing (though a few cycles more or less
shouldn't cause immediate breakage).
The timings in the code have been calculated from the assembly generated
by gcc 4.8.2 and gcc 4.3.2.
The RX baudrates supported by SoftwareSerial are still not unlimited. At
16Mhz, using gcc 4.8.2, everything up to 115200 works. At 8Mhz, it works
up to 57600. Using gcc 4.3.2, it also works up to 57600 at 16Mhz and up
to 38400 at 8Mhz. Note that at these highest speeds, communication
works, but is still quite sensitive to other interrupts (like the
millis() interrupts) when bytes are sent back-to-back, so there still
are corrupted bytes in RX.
TX works up to 115200 for all combinations of compiler and clock rates.
This fixes#2019
