Is manual install of DUE core possible?

IDE: 1.6.4

Due to the firewall at work, when I start the Boards Manager I get en error, and I am unable to download the core for the DUE. Just wondering if anyone knows if I could download the file from home onto a USB stick, then take it to work and manually copy the file. I suspect there is more to it than that. Any thoughts? Thanks -

Offline installation is hopefully going to be added in 1.6.5 or 1.6.6, there have already been multiple issues about this.

If you need to use the DUE core you can use the older 1.5.8 version of the IDE as it is still added with the zip.

http://www.arduino.cc/en/Main/OldSoftwareReleases#1.5.x

There is a way to use IDE 1.6.4 with Due from a USB drive (on Windows... didn't try with U..X).

  • Expand the ZIP installation archive on your USB drive.
  • In the main arduino directory (where you find arduino.exe), create a new folder named portable
  • Use the board manager to download Due related fles Those new files and preferences.txt will be installed in this portable directory. You can now use your IDE directly from your USB drive or copy the entire arduino folder to another machine.

al1_24: There is a way to use IDE 1.6.4 with Due from a USB drive (on Windows... didn't try with U..X).

  • Expand the ZIP installation archive on your USB drive.
  • In the main arduino directory (where you find arduino.exe), create a new folder named portable
  • Use the board manager to download Due related fles Those new files and preferences.txt will be installed in this portable directory. You can now use your IDE directly from your USB drive or copy the entire arduino folder to another machine.

Shame this information is not more prominent in the Arduino IDE installation pages. I have cursed and stayed away from any IDE version > 1.5.x because the IDE was no longer portable. I also suffer the board manager problem some others seem to have where I cannot download new packages (or libraries) through the IDE. The manager problem I finally figured a workaround for but the fact it stored and expected to access the packages from %APPDATA% was still a problem. Even manually moving a core from %APPDATA% to the sketch hardware folder did not work properly for DUE as the tools folder did not pick up properly so sketches could compile.