TPI support for linuxgpio and usbtiny#8
Conversation
Can't export GPIO 0, already exported/busy?: Device or resource busy This error gets triggered since pins PPI_AVR_VCC and PPI_AVR_BUFF appear to default to ~0 so if avrdude.conf does not explicitly define them to some other unique pins, we end up trying to export gpio 0 multiple times, triggering the error.
This makes it possible to program the smaller chips, such as ATtiny9 via TPI.
This makes it possible to program the smaller chips such as ATtiny9 via TPI using the usbtiny interface. Tested with sparkfun AVR Pocket Programmer.
|
You're probably going to want to submit this to the mainline avrdude project here: http://savannah.nongnu.org/projects/avrdude/ This repository contains changes for the linuxspi driver that has not yet been accepted into the mainline. |
|
I did submit patches at Savannah:
Is there anything else I should/could do? |
|
Strange... some of these has already been fixed in svn, while others ignored... |
|
I don't really know. We have since switched to using FTDI cables for TPI programming. See:
Not that these have generated a lot of feedback... ;-/ |
|
Thought I'd follow up - as I've been on a quest to find more information about TPI support for the USBtiny. While David's patch (8924) adding support was added, there hasn't been a new release of AVRDUDE since 2016. So those hoping to use it will need to build from source. As noted in usbtiny.c, using TPI requires connecting MOSI and MISO with a 1k Ohm resistor although others have had success with a 330 Ohm resistor. |
4 participants
These commits make it possible to program ATtiny4, ATtiny5, ATtiny9 or ATTtiny10 through TPI using the linuxgpio driver (e.g., on Raspberry PI) or the usbtiny driver (e.g., with the Sparkfun Pocket AVR Programmer).