-
Notifications
You must be signed in to change notification settings - Fork 293
SpDir Continues To Flash Error
Alden Hart edited this page Mar 18, 2017
·
6 revisions
In 2015 a batch of TinyG v8's shipped from the factory with incorrect LOCKBITS
set. To fix this issue you may contact Synthetos and we will fix your board and ship it back to you free of cost. However, if you want to fix this error yourself then proceed below.
To fix this you will need:
- A windows machine (vm or bare metal)
- An AVRISP MKII or compatible programmer that support Atmel Studio and PDI programming mode.
- You can get the xboot.hex file here. [xboot.hex (https://raw.github.com/synthetos/TinyG/master/xboot/xboot/xboot.hex) NOTE: You need to right click and save as on the xboot.hex link to download the hex file correctly.
- Launch Atmel Studio and press CTRL-SHIFT-P (or click on the chip with a lightning bolt on it from the menu).
You should see a screen like this:
- Select your programmer (assuming its plugged in correctly to your tinyg and your tinyg is powered up, the raised part on one side of the connector matches up with the gap in the white outline around the target on the tinyg), select the Atxmega192A3 as the chip and then click apply and then read. If all went well you should see your device signature populate.
- Next click on the
Lock Bits
menu on the left (only visible after a successful step 3). It will look like this:Notice how they do not all say
NOLOCK
. They need to ALL sayNOLOCK
. - Change all LOCKS to say
NOLOCK
from the dropdown menus. - Then click the program button below once they all are set to
NOLOCK
. NOTE Sometimes this works sometimes it does not. I have not figured out why it works only sometimes. Not to worry move on to the section below if it fails. If it works then you should be good to go and ready to update your tinyg firmware like normal.
If the above method failed its time to just erase the chip.
- Click on the
Memories
tab on the left. Then click on the erase chip like this: - Now go back to the
LOCKBITS
tab and verify that they are all set toNOLOCK
. Like this:
If you were able to reset the lockbit without erasing the board you are pretty much done. However if you had to erase the board we now have no bootloader so follow the steps below to reflash the bootloader AND the new TinyG firmware.
- Follow the steps here to load your bootloader onto your TinyGv7-8. But come back here to finalize loading the TinyG firmware
- Now we need to load a tinyg firmware onto your board via the newly flashed bootloader you loaded in step 1. Remove the AVRISP programmer as you not need it to flash your board. Follow the instructions here.
Getting Started Pages
- Home
- What is TinyG?
- Getting Started
- Connecting TinyG
- Configuring TinyG
- Sending Gcode Files
- Flashing TinyG
- Chilipeppr
Reference Pages
- TinyG Help Page
- TinyG Tuning
- TinyG Command Line
- TinyG JSON
- Gcode Support
- Homing and Limits
- Inch and MM Units
- Alarms and Exceptions
- Coordinate Systems
- Status Codes
- Status Reports
- Power Management
- Feedhold and Resume
- Licensing
- TinyG v8 Data Sheet
Discussion Topics
- Test-Drive-TinyG
- Jerk Controlled Motion
- Gcode Parsing
- Shapeoko Setup
- OX CNC TinyG Guide
- Creating Gcode Files
- Milling With Noisy Spindles
- Stepper Motors and Power Supplies
- Text Wrappers and Transaction IDs
- Using External Drivers
- TinyG Projects
Chilipeppr
- Chilipeppr
- Chilipeppr Advanced Usage
- Chilipeppr Archive and Restore Parameters
- ChiliPeppr PCB Auto Level
- Automatic Z Homing When Milling PCBs
Troubleshooting
Developer Pages