I'm on vacation, not bored I want an AVR ISP programmer that uses the systems power on vcc and the gpio. It should use proper levelshifters (4 of them - SN74LVC1T45) giving a range of 1,65 <=> 5,5 on system side and whatever brain I choose for my progger. Can be especially interesting for boards with "exotic" chips and power levels.
a "true" in system programmer | so this didn't work out so well
2022-11-21 17:15:11
Image of PCB shows shortcuts on PCB connector that have been later fixed. Small board of 2cm x 4cm
twitter back log from 2020-10-24
"Time flies when you're trying to have fun with a two year old project. This is my take on an ISP for AVR and Attiny chips, than can power the target with 3V, 5V or translate to the target's voltage. I always wondered why the old version was sometimes shorting out and now I know.
The version before had POGO pins soldered directly to the pads (yes, they were mirrored for that). They were replaced with a "standard" 6 pin socket and this works fine. I was able to program plenty of targets with the new programmer. They just would not start.
With the POGO pins I never noticed that, because as soon as I was done programming with it, the target was powered on it's own and started fine. But now the reset line was held LOW because the reset pin turned into an INPUT.
The level-shifter I'm using is not bidirectional, but the direction of communication can be selected. So I lifted the pins and rewrote the USBASP firmware to change the direction whenever the red LED turns on and off (basically). Now nothing works anymore and I'm asking myself:
Should I change the schematics and find a bi-directional tri-state level-shifter? Or should I scope it and see if it's fixable with some delays?"
It seems to just work with the 5V circuitry and boots normally. Maybe it's behaving weird when it's 3.3V on the receiving side. Hm nope, also works with 3.3V. Maybe it was the target then, need to remember what I wanted to program back then.
a "true" in system programmer | so this didn't work out so well
2022-11-21 17:15:11
Image of PCB shows shortcuts on PCB connector that have been later fixed. Small board of 2cm x 4cm
twitter back log from 2020-10-24
"Time flies when you're trying to have fun with a two year old project. This is my take on an ISP for AVR and Attiny chips, than can power the target with 3V, 5V or translate to the target's voltage. I always wondered why the old version was sometimes shorting out and now I know.
The version before had POGO pins soldered directly to the pads (yes, they were mirrored for that). They were replaced with a "standard" 6 pin socket and this works fine. I was able to program plenty of targets with the new programmer. They just would not start.
With the POGO pins I never noticed that, because as soon as I was done programming with it, the target was powered on it's own and started fine. But now the reset line was held LOW because the reset pin turned into an INPUT.
The level-shifter I'm using is not bidirectional, but the direction of communication can be selected. So I lifted the pins and rewrote the USBASP firmware to change the direction whenever the red LED turns on and off (basically). Now nothing works anymore and I'm asking myself:
Should I change the schematics and find a bi-directional tri-state level-shifter? Or should I scope it and see if it's fixable with some delays?"
It seems to just work with the 5V circuitry and boots normally. Maybe it's behaving weird when it's 3.3V on the receiving side. Hm nope, also works with 3.3V. Maybe it was the target then, need to remember what I wanted to program back then.
a "true" in system programmer | the pcb bug bit me - must be that part of the year
2018-10-17 00:42:19
I wanted to take a look at the firmware of my #BINCL - binary coded decimal 10mm LED clock to get rid of the pcbs I still have from the first batch. I quickly ran into the problem of having only 5V usbasp modules or my version one board with pogo pins, able to talk to 3v3 devices, but not power them. In this revision I've added a AP2112K and a second switch, changed the usb plug and made it a single side pcb. The edge connector is inverted from before and will now hold an ISP6 port instead of the pogo pins!
Boards aren't routed yet, price in a size like this on OSHpark for 3 boards is
a "true" in system programmer | the pcb bug bit me - must be that part of the year
2018-10-17 00:42:19
I wanted to take a look at the firmware of my #BINCL - binary coded decimal 10mm LED clock to get rid of the pcbs I still have from the first batch. I quickly ran into the problem of having only 5V usbasp modules or my version one board with pogo pins, able to talk to 3v3 devices, but not power them. In this revision I've added a AP2112K and a second switch, changed the usb plug and made it a single side pcb. The edge connector is inverted from before and will now hold an ISP6 port instead of the pogo pins!
Boards aren't routed yet, price in a size like this on OSHpark for 3 boards is
a "true" in system programmer | thoughts after half a year
2018-02-14 11:37:00
Overall I'm pretty happy with it, but I'm a bit sad that I can't use this with boards where pinheaders are already present. Would have been nice to have a standard 2x3 ISP socket on it and change between cables, pogopins and avr clamps. When it comes to power, a little regulator for 3V3 would be nice too. Basically switch between 5V, 3V3 and selfpowered.
a "true" in system programmer | thoughts after half a year
2018-02-14 11:37:00
Overall I'm pretty happy with it, but I'm a bit sad that I can't use this with boards where pinheaders are already present. Would have been nice to have a standard 2x3 ISP socket on it and change between cables, pogopins and avr clamps. When it comes to power, a little regulator for 3V3 would be nice too. Basically switch between 5V, 3V3 and selfpowered.
