Assuming you install WinAVR, how would you pass the part information using the external programmer from BASCOM to this command line?? The filename would use the {file}.
Or am I making this harder than it really is? Smile
I am currently using the STK500 interface and a com port to program with BASCOM.
Does anyone know if this device is compatible with BASCOM-AVR?
Yes it is. It’s a programmer that will put a file of bytes into the chip. It doesn’t care what generated the bytes.
BASCOM-AVR can produce a *.hex or *.bin. This programmer when used with avrdude will take that file and program the chip.
I don’t use BASCOM-AVR but I imagine they try to integrate the programmer with the IDE. If that mechanism doesn’t like avrdude, then just ignore it and run avrdude on the command line specifying the *.hex file directly.
deadsy:
BTW- Pocket AVR Programmer sku: PGM-09231 has quite a few people saying it doesn’t work with their USB ports. That’s because the design needs fixing. Specifically adding zener diodes on the USB data lines makes a world of difference.
Hmmm, I have one of those and it worked fine until I set the fuses on an ATmega328P, and now AVRDUDE only reports “init failed” when trying any operation and won’t even read the uC’s device signature when given “-F -v” flags to force it past the init check.
Apparently there’s more amiss than I was thinking…
OddOne:
Hmmm, I have one of those and it worked fine until I set the fuses on an ATmega328P, and now AVRDUDE only reports “init failed” when trying any operation and won’t even read the uC’s device signature when given “-F -v” flags to force it past the init check.
Apparently there’s more amiss than I was thinking…
From what you are saying it sounds like the 328 broke on your dev board. It’s possible, I suppose, but it seems unlikely. Given my experience I’d be more likely to mistrust the programmer.
I saw similar things before I clamped the USB data lines with the zeners. ie- some sort of failure followed by an inability to read the device signature. I could generally restore some modicum of functionality by doing a power cycle.
With the mod in place the programmer is reliable (for me). The only weirdness is a need to unplug/replug the programmer after Linux has booted to get the programmer recognized by the USB sub-system.
OddOne:
Hmmm, I have one of those and it worked fine until I set the fuses on an ATmega328P, and now AVRDUDE only reports “init failed” when trying any operation and won’t even read the uC’s device signature when given “-F -v” flags to force it past the init check.
Apparently there’s more amiss than I was thinking…
From what you are saying it sounds like the 328 broke on your dev board. It’s possible, I suppose, but it seems unlikely. Given my experience I’d be more likely to mistrust the programmer.
I saw similar things before I clamped the USB data lines with the zeners. ie- some sort of failure followed by an inability to read the device signature. I could generally restore some modicum of functionality by doing a power cycle.
With the mod in place the programmer is reliable (for me). The only weirdness is a need to unplug/replug the programmer after Linux has booted to get the programmer recognized by the USB sub-system.
I thought maybe I misconifgged the fuses and nuked the chip (pending a round with a parallel programmer) but it failed on three 328s, one of them literally removed from tray and reflowed onto a board an hour earlier. All efforts with -F -v report an all-zeroes device signature, which implies to me it’s not communicating any more.
I’ve put in a support request to inquire about the situation.
In the meantime, have a link to your mod anywhere?
In the meantime, have a link to your mod anywhere?
I added zener diodes to clamp the USB data lines. These were present on the USBTinyISP design but had been left out on the AVR programmer. Hacking the board was too fiddly, so I cut the cable and added them there instead.
Before: Board not seen by USB host controller when plugged directly into PC.
