-
Notifications
You must be signed in to change notification settings - Fork 295
Flashing g2core with Windows
This page is for uploading an already compiled G2 binary to a target board without a debugger from Windows. Please see Getting Started with g2core Development for information about other options.
Option 1 - Compile your own using the instruction in Compiling the Code
Option 2 - Get the g2core.bin binary firmware files from https://github.com/synthetos/g2/releases
- Click the "Assets" drop down for any of the releases. The various g2core.bin files will be displayed, with names appropriate for specific boards we have configuration files for.
In either case you'll need to note the path to the resulting binary file. For example, if it's called g2core.bin
and it's in the Downloads directory of your home page, you would use %HOMEPATH%\Downloads\g2core.bin
. We'll call this PATH_TO_BINARY
in the commands below.
The arduino-flash-tools repo contains the bossac
utility. You can download the zip file here.
Expand the zip file in a location where you know the path, and note that path.
Hold down the Windows Key and press r then type cmd.exe and hit enter:
-
cd
path to expanded zip file contents
-
cd tools_windows\bossac\bin
Run the mode
command by itself and it should return a COM
x. Note your port number for x to use as COMx
in the following commands. Remember from above that PATH_TO_BINARY
is to be replaced with the path to the downloaded or compiled .bin
file.
After that go ahead and run these commands, replacing COMx
with your port, like this: COM4
.
mode COMx BAUD=1200
bossac.exe --port=COMx -U false -e -w -v -b PATH_TO_BINARY -R
Getting Started Pages
- Home
- What is g2core?
- Who uses g2core?
- Jerk-Controlled Motion
- Getting Started with g2core
- Connecting to g2core
- Configuring g2core
- Flashing g2core
- Troubleshooting
Reference Pages
- Gcodes
- Mcodes
- Text Mode
- JSON Communications
- GPIO Digital IO
- Alarms & Exceptions
- Power Management
- Coordinate Systems
- Status Reports
- Status Codes
- G2 Communications
- Tool Offsets and Selection
- Probing
- Feedhold, Resume, Job Kill
- Marlin Compatibility
- 9 Axis UVW Operation
- gQuintic Specs
Discussion Topics
- Roadmap
- GPIO for 1.X Releases
- Toolheads
- Raster Streaming Prototol
- g2core REST Interface
- Gcode Parsing
- G2 3DP Dialect
- Consensus Gcode
- Digital DRO
- Overview of Motion Processing
Developer Pages
- Development & Contribution
- Branching and Release - DRAFT
- Getting Started with g2core Development
- Project Structure & Motate
- Compiling G2
- OSX w/Xcode
- OSX/Linux Command Line
- Windows10 w/AtmelStudio7
- Debugging G2 on OSX
- Board and Machine Profiles
- Arduino Due Pinout
- Arduino DUE External Interfaces
- Diagnostics
- Debugging w/Motate Pins
- Development Troubleshooting
- g2core Communications
- Git Procedures
- Windows 10 / VMware 8 Issues
- Dual Endpoint USB Internals
- G2core License
- VSCode Setup
- Compatibility Axioms
- Wiki History