ARDUINO 1.6.12 - 2016.09.21
[ide]
* Refactor Editor code, solving some long standing bugs and cleaning up everything. Thanks @matthijskooijman
* Add initial Cloud API integration. When plugging a new board, if an additional core is needed, the user will be prompted to install it
* Improved examples menu organization. Thanks @PaulStoffregen
* Recompiled arduino-builder with Go 1.7.1 to avoid crash on OSX Sierra
[core]
* avr: Add support for internal 2.56V and 2.56V ext. cap analog references on the ATtiny25/45/85. Thanks @mischnic
* Added String::toDouble(). Thanks @Ivan-Perez
* Update to avrdude 6.3 with patch to ignore unused fuses (burn bootloader works also wih outdated cores)
avrdude 6.3?
Get ready for people with the old USBAsp driver installed to start asking for help. Assuming this wasn't fixed in the patched version, 6.3 is not compatible with the older USBAsp driver.
DrAzzy:
Get ready for people with the old USBAsp driver installed to start asking for help. Assuming this wasn't fixed in the patched version, 6.3 is not compatible with the older USBAsp driver.
No, I still encounter that issue with Arduino IDE 1.6.12/Arduino AVR Boards 1.6.14.
Here's the driver update instructions:
pert:
- Plug in USBasp
- Download Zadig from http://zadig.akeo.ie
- Start zadig
- Options > List all devices
- Select USBasp from the drop down menu
- Select libusbK(v3.0.7.0) driver
- Click Install
Forum thread for the issue: [SOLVED]Problems using USBasp with Arduino IDE 1.6.10/Arduino AVR Boards 1.6.12 - Microcontrollers - Arduino Forum
Issue report: avrdude 6.3.0-arduino2 incompatible with USBasp using libusb-win32 driver · Issue #1 · arduino/avrdude-build-script · GitHub
It's a shame because the stock avrdude build works fine for me with the libusb-win32(the USBasp recommended driver which is included with the firmware) which proves that it could have been fixed. I couldn't get the other people who encountered the issue to verify it for me so I wasn't able to provide further evidence in the issue report that I wasn't the only user affected by the bug.
On the other hand, all the other issues that avrdude 6.3.0-arduino2(included with Arduino AVR Boards 1.6.12/Arduino IDE 1.6.10) had should be fixed.
Something new that may cause unnecessary concern with some users is you now get messages such as:
avrdude: WARNING: invalid value for unused bits in fuse "efuse", should be set to 1 according to datasheet
This behaviour is deprecated and will result in an error in future version
You probably want to use 0xfd instead of 0x05 (double check with your datasheet first).
When avrdude 6.3.0-arduino6's workaround code for the AVRDUDE 6.3 changed unused fuse bit handling behavior is required for verification.
It's annoying that they have apparently replaced the old system they had for handling unused fusebits (where their representation was up to the author of the avrdude.conf entry) with a less flexible one...
That Zadig tool is neat.
I updated the driver on a system that had the old one by just uninstalling driver from device manager, and running the installer for the new driver. In any event, it's unfortunately that the update broke compatibility, when the old driver had been working fine for years.
It used to be that new release announcement threads were pinned at the top of the forum, and older ones were unpinned. Now I suppose 1.6.6 and 1.6.7 are "new" forever, and subsequent announcements go to oblivion.
Works well on a UNO on server 2012 seems faster too ?
Ballscrewbob:
seems faster too ?
I believe that is caused by the arduino-builder include detection caching added by Matthijs Kooijman in Include detection caching by matthijskooijman · Pull Request #175 · arduino/arduino-builder · GitHub.
Tried it with a ch340 UNO and NANO, genuine Mega, all working fine under USB 3.0
MKR1000 will not play with USB 3.0 but works fine on USB 2.0
UPDATE...
It offered a couple of updates which I took then it promptly started to fail with the MKR.
Reversed to 1.6.11
Shame cos it really was quick and works well with lesser boards.