openrcforums

viewtopic.php?f=95&t=7804#p104279
yes right here under Dont Panic it says not to use -F option
It probably should have been mentioned in a more pronounced way.

Never use the -F option to avrdude. :evil: :evil: :evil: :evil: :evil: :evil: :evil: :evil: :evil: localhost:~ carloskammerlander$ avrdude -c usbasp -P usb -p atmega48 -F -U flash:w:firmware.hex This is how you brick your radio. luckily you are only messing with a programmer. I know it was mentioned...

yes that is the output we need. this particular time the output says the the file firmware.hex is not in the directory you called the command from. this appears to be the 'carloskammerlander' directory. verify that the file firmware.hex is in the directory you are calling the avrdude command from. I...

Yes. Like you did earlier when it mentioned the signature.

You didnt post your output. Dont give up you are almost there.

You did not successfully update the firmware on the usbasp. Your usbasp does not have an m88 mcu. Most assuredly it has an m8. The firmware gruvin posted will not work with an m8. The romulo firmware posted earlier should work but you will need to update the command line syntax. Replace 'atmega88p' ...

[quote="gruvin"] @Koarl -- your USBASP most likely has the ATmega48 chip, like the original. But it might pay to check. Got a magnifying glass? ;-) [/code] I'm pretty sure it comes with an m8 . He can just attempt to read the flash or even and it will print out the actual signature which t...

earlier he posted this which shows 5.11.1 on a mac

viewtopic.php?f=95&t=7804#p104307

maybe until gruvin responds you could post the avrdude output that you get when you try to update the one usbasp with the other one, using the romolo firmware posted in this thread. Maybe this will pinpoint whether you are actually updating the firmware on the usbasp

What i can do tonight is attempt to compile the usbasp firmware that is listed on the gruvin source. as i said before there didnt seem to be a hex file for a m8 mcu. his explanation of why it mismatches at 0x0000 makes sense. What you could do to verify that the size of the firmware written is in fa...

memberlist.php?mode=viewprofile&u=1327
I think this is mr gruvin. Maybe you can pm him and he will check in?

You talking firmware for the gruvin or firmware for the usbasp. 1. I think you got the usbasp properly flashed with romolu because i do not see the 'can not set SCK ' warning in your avrdude log. If you still had the chinese firmware on there you should have that warning ( which under normal situati...

Great. I know that programmer. Pretty sure in the upper left hand of your pic is a compoment with 8 legs, sorta looks like a spider. I think it is marked 101. Please confirm. 101 is good. That is 100 ohm resistor pack. If it said 471 that would be bad for 9x/9xr. Havent seen any bad ones for a coupl...

That link is a hex file but i have no idea what it is. Here is some info from gruvin source https://code.google.com/p/gruvin9x/source/browse/trunk/hardware/gprog/firmware/README he provides his usbasp src but his binaries are not for m8 mcu which more than likely is what your usbasp has in it, We re...

5.11.1 ver of avrdude is good for 9x/9xr. I would think it is good for gruvin also. I'm thinking we look elsewhere for the problem.
will wait to see your usbasp.
I wonder if gruvin posted his usbasp firmware.

I was able to flash a stock 9x with a smartiepartsboard but with a old programmer. That time I used a old version of companion. working with a version downloaded recently. well it could be that the gruvin processor doesnt work with the older version of avrdude, but this information does make you wo...

ok I am home now :-) sorta old thread but may be relevant. http://openrcforums.com/forum/viewtopic.php?f=28&t=3940 and here https://code.google.com/p/companion9x/wiki/MacInstall the talk about avrdude 6.0 being problematic is true but your mismatch then usually starts at 0x0100 not 0x0000 as you...

My confusion. My guess is your problem is related to the version of avrdude with Macintosh. Do some searches on the forum related to this

Linux. Avrdude installed in /usr/local. What distro of linux and version of avrdude. I dont have gruvin but i may have an arduino mega with similar mcu. not sure if gruvin uses a bootloader. What happens if you verify the file you successfully read ? How bout some history. Did it ever work ? When di...

s_mack wrote: PHPBB has always been horrible for spam.

+1

yes follow the instructions on the post you mention. the pics are outdated but you should be able to figure it out. the youtube video on that thread has over 12k hits, so it must be helping out. i dont know about the gruvin board, but at one time with a 9xr if you flashed the wrong firmware to the b...

https://www.sparkfun.com/products/7950

and here it is being driven from the output of an atmel m8 mcu.
https://www.youtube.com/watch?v=zgJUt5ZaeFg

viewtopic.php?f=23&t=449
9xSchematics.pdf
gruvin9x_v2_actual.pdf

yes but your math doesnt consider.
1. the duty cycle of pcm on the output pin. I think it will be 50%
2. the series resistor, if any.
3. the series cap, if any

another schematic does not show the 1k resistor but shows a 10uf cap in series with the buzzer, which is on pin5, pe3

yea I am looking at a 9x schematic now. the one I am looking at appears to have a 1k resistor in series with the stock speaker. not sure what radio you have or how accurate is the schematic I am looking at. then again if you put a cap in series with your new piezo I believe that will affect(lower) t...

I imagine there are many ways to modify the radio regarding the speaker If the question is how much current can an IO pin draw on an atmega 64 taken from page 325 of the below referenced url DC Current per I/O Pin ............................................... 40.0 mA http://www.atmel.com/images/at...

great. glad you got it going.
have fun

avrdude.exe: Device signature = 0x1e9702 avrdude.exe: Expected signature for ATMEGA64 is 1E 96 02 great. you got the driver issue resolved. this issue is because your radio has a m128 processor not a m64 processor. I believe there are 2 places in the software where this needs to be changed. 1. in t...

When trouble shooting ' cant find usbasp device' issues you do not need to have usbasp hooked up to target (the radio). Once the drivers are installed properly or you otherwise resolve ' cant find usbasp device' issues you will get a 'target not found' type error. Then hook up the target (the radio)...

interestingfellow wrote: avrdude.exe: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc

that error is usually a windows driver issue.
http://9xrprogrammer.com/index.php/learn/23-drivers