Hey please help.
I have built my pov kit as specified but when I tried to run "make program-minipov" I got this:
I think it may be because in the device manager my serial port comes up as 'com10' so when I change it in 'Makefile' the 0 disappears. I really don't know, I've never worked on such low level code before.
Any suggestions??
minipov3
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 1645
- Joined: Sat Nov 10, 2007 12:59 am
Re: minipov3
damn, how much stuff you got plugged into the poor old box? i found the following in the fuzebox pages...
the port setting "-P \\.\COM" is the important bit. ignore the chip and programmer type settings.If you have a lot of FTDI-chip devices that have been plugged in to your computer, like adapters, Arduino, cables, etc. the COM port numbering under windows might be as high as COM10! In this case you have to use the command notation avrdude -p m644 -c stk500v1 -P \\.\COM10 to address the COM port. I have no real idea why this is and its annoying as heck but soon this will be all in a Makefile so bear with me.
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Thanks man,
haha not much, just a mouse and an internet dongle, which I had to reinstall about a million times. Might explain it.
I tried it out a couple of times but it just comes up with the same error.
Do you think it could be because i've edited the text file rather than the unknown file type that comes in the firmware?
My only other guess is that I didn't install the extra driver for the USB/serial converter.
I couldn't manage to make the file run so i figured it only applied for Macs.
Should I be able to find the device in my computer??
haha not much, just a mouse and an internet dongle, which I had to reinstall about a million times. Might explain it.
I tried it out a couple of times but it just comes up with the same error.
Do you think it could be because i've edited the text file rather than the unknown file type that comes in the firmware?
My only other guess is that I didn't install the extra driver for the USB/serial converter.
I couldn't manage to make the file run so i figured it only applied for Macs.
Should I be able to find the device in my computer??
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Hmm, I tried again,
This time my device changed to COM9, so I changed the Makefile accordingly.
But still it comes up with the same error.
I'm really stuck here, any ideas??
This time my device changed to COM9, so I changed the Makefile accordingly.
But still it comes up with the same error.
I'm really stuck here, any ideas??
-
- Posts: 12151
- Joined: Thu Apr 06, 2006 4:21 pm
Re: minipov3
do you have a new screenshot w/COM9?
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Yep
Do you want to see the makefile?
Do you want to see the makefile?
-
- Posts: 1645
- Joined: Sat Nov 10, 2007 12:59 am
Re: minipov3
yeah, the makefile would be good to see, since according to the screenshot it's still trying to use com1.
-
- Posts: 1645
- Joined: Sat Nov 10, 2007 12:59 am
Re: minipov3
the makefile itself would have been more useful than a picture of the beginning of it. try searching the file for an instance of the string com1.
try thisfrom the command line. doesn't fix the makefile, but makes for a nice sanity check.
try this
Code: Select all
avrdude -p attiny2313 -c dasa -P com9 -U flash:w:minipov.hex
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Brilliant, looks like I'm getting somewhere.
Everything went fine until the last bit and this happened
Something about a fuse changing.
I didn't know what it meant so I just clicked yes and it's been blinking away for a good few minutes.
Would it have anything to do with one the LEDs which stopped working before just I tried this?
And if so, should I just restart it and enter no next time?
Everything went fine until the last bit and this happened
Something about a fuse changing.
I didn't know what it meant so I just clicked yes and it's been blinking away for a good few minutes.
Would it have anything to do with one the LEDs which stopped working before just I tried this?
And if so, should I just restart it and enter no next time?
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Hmm, I ignored the lfuse change, restarted the process and got this:
But when I went to add in the new programming I got this:
So it looks like I'll have to fix the lfuse.
Does anyone know how to do it?
Or what that even means??
But when I went to add in the new programming I got this:
So it looks like I'll have to fix the lfuse.
Does anyone know how to do it?
Or what that even means??
-
- Posts: 1645
- Joined: Sat Nov 10, 2007 12:59 am
Re: minipov3
time to post some pictures of the board. top and bottom. this kind of flakiness usually means a build problem.
best to take pictures from a distance with the zoom and the camera in macro mode if you can. maybe a piece of paper over the flash to diffuse it.
best to take pictures from a distance with the zoom and the camera in macro mode if you can. maybe a piece of paper over the flash to diffuse it.
-
- Posts: 1645
- Joined: Sat Nov 10, 2007 12:59 am
Re: minipov3
if your makefile were working i'd say to trySo it looks like I'll have to fix the lfuse.
Does anyone know how to do it?
Or what that even means??
Code: Select all
make burn-fuse
Code: Select all
avrdude -p attiny2313 -c dasa -P com9 -u -U lfuse:w:0xe4:m
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
It's in a new thread but I'll put it here as well
-
- Posts: 20
- Joined: Sun Sep 13, 2009 7:53 am
Re: minipov3
Doesn't look like I'll be able to get any pictures until I get some new batteries.
Please be positive and constructive with your questions and comments.