* commit 'b8b2869753d488bfd203615637e1de3912589a92': (68 commits)
Updated revisions.txt
Fixed wrong path in successful message
arduino-core: restored debug info in class files
Fixed NPE in case of missing boardData
Added missing translations
Added windows drivers
Added warning for uncertified boards
Update revision.txt
update revisions.txt
SoftwareSerial: match bool API with HardwareSerial
Fix to save as to parent folder is needed by all OSs, not just Mac
Update revision.txt
MacOSX: previous better IDE was missing some pieces. Added
MacOSX: better IDE
Updated revisions.txt
NEW button now behaves as clicking File -> New menu entry. Fixes#2685
Windows: bundled JRE updated to 8u31 build.xml now uses unzip target
Added .getParentFile() to saveas for mac. This prevents saving into the sketch itself
Compound edits weren't part of the undo/redo dance
An undoable action marks the sketh as modified
...
* 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
Before, the interrupt would remain enabled during reception, which would
re-set the PCINT flag because of the level changes inside the received
byte. Because interrupts are globally disabled, this would not
immediately trigger an interrupt, but the flag would be remembered to
trigger another PCINT interrupt immediately after the first one is
processed.
Typically this was not a problem, because the second interrupt would see
the stop bit, or an idle line, and decide that the interrupt triggered
for someone else. However, at high baud rates, this could cause the
next interrupt for the real start bit to be delayed so much that the
byte got corrupted.
By clearing the interrupt mask bit for just the RX pin (as opposed to
the PCINT mask bit for the entire port), any PCINT events on other bits
can still set the PCINT flag and be processed as normal. In this case,
it's likely that there will be corruption, but that's inevitable when
(other) interrupts happen during SoftwareSerial reception.
This precalculates the mask register and value, making setRxIntMask
considerably less complicated. Right now, this is not a big deal, but
simplifying it allows using it inside the ISR next.
Since those functions are only called once now, it makes sense to inline
them. This saves a few bytes of program space, but also saves a few
cycles in the critical RX path.
Previously, up to four separate but identical ISR routines were defined,
for PCINT0, PCINT1, PCINT2 and PCINT3. Each of these would generate
their own function, with a lot of push-popping because another function
was called.
Now, the ISR_ALIASOF macro from avr-libc is used to declare just the
PCINT0 version and make all other ISRs point to that one, saving a lot
of program space, as well as some speed because of improved inlining.
On an Arduino Uno with gcc 4.3, this saves 168 bytes. With gcc 4.8, this
saves 150 bytes.
