Objective Development Forums

SOLVED POST: wrong fuses

the problem was i was using codevisionAVR to program the fuses but aparently it has wrong info about mega328P so the code was not starting at boot address..

i can use it now at 12MHz or 16MHz perfectly

Thank you all!

SOLVED POST: wrong fuses

the problem was i was using codevisionAVR to program the fuses but aparently it has wrong info about mega328P so the code was not starting at boot address..

i can use it now at 12MHz or 16MHz perfectly

Thank you Christian!

hi there! i made it work, but in order to make it work on a 328p i made some changes on the iom328p.h library file..i dont know why, i didnt checked the hole file but i seemed to be identically to iomx8.h general library file used by atmega48/88/168 (not pico) but, the PRR register is included anywa...

i made it work.. with a 12mhz crystal, both atmega8535 and atmega168V (yes, i know its only 10mhz but it worked fine) but i still cant make it work on atmega328p. i think there is a compatibility issue, because mega168 and mega328 are from the same family.. i know the mega328 is running because i ru...

i thought thats the way it works.. i assumed the osc calibrations were made automatically as the module for 12,8mhz was loaded, if i port D+ to INT0 the osc tune was made at every usb bus reset and if i port D- to INT0 then the osc tune was made at every packet.. so how should i do to have an 12,8m...

sorry christian, i ve made a new post since there is no relation between the topic and my actual problem.. i thought it was correct to do it, and didnt see your reply but.. here i am now: i have been testing my chances.. neither the atmega8535 and atmega328p works at 12,8Mhz code. atmega8535 works a...

i have been testing my chances.. neither the atmega8535 and atmega328p works at 12,8Mhz code . atmega8535 works at 12 and 16Mhz atmega328p no successfull results even with same crystals here is what i did : always running at 3,3v i simply took the mouse-hid project and just like it was, i compiled i...

Welll.. i have tried out with both 16Mhz and 12Mhz with 10pF capacitors and i also added the 68ohms resistors at D+ and D- lines. No results. i have a led at deviceconnect_pin, it blinks many times and then it says again not recognized I saw at metaboard that you were using 27pF capacitors at the cr...

i had tried recently with MOUSE_HID example, with no success..

i will try with a crystal as a last resource.. i have the feeling that my avr is not running at a RC calibrated 12,8Mhz

you were right! my code wasnt at boot loader section.. now it is, i have checked it out with avrdude in terminal mode! BUT.. windows still dont recognized it, i made a "dump cal" and now it seems the firm is running, since it has changed from 0xA3 to 0xC6 is there any special consideration...

mmm i cant get it recognized by windows.. i ve got an atmega328p so i tried what you posted by the winavr says warning and then error: [b]usbdrv/usbdrv.c: In function 'usbDeviceRead': usbdrv/usbdrv.c:504: warning: implicit declaration of function 'pgm_read_byte_far'[/b] main.c: In function 'main': m...

Great! you are right i didnt realize that possibility! Now, a have been able to run the firmware, but i only get an "Could not recognize the device" from windows.. the firmware is running on boot loader section, i know because i have a LED attached at the USB.connectdevice pin an it works ...

sorry if im very very wrong.. but F_CPU isnt defined at khz? you got it at hz



YUP, i was wrong.. F_CPU is at Hz

First of all.. im working on a mega328P @ 3.3v and i will use USB only for bootloading, and that means 1 time a year i guess. Thats why i prefer to overclock the RTC instead of buying a crystal.. and as avr rtc runs on 8mhz i have read there were versions about 12,8 and 16,5mhz that will test the OS...