-
-
Notifications
You must be signed in to change notification settings - Fork 12
Feels verry sluggish, fuse settings wrong? #18
Description
UPDATE : Programming standard bootloader and the application using Arduino IDE instead of avrcommands fixed it.
now it turns on in few seconds and verry responsive. No idea why it would not work using the commands below?!
so i built 3pcs of this and they all act the same way, feeling verry sluggish.
First of all it takes 40sec - 1min before it even comes on ( led turns on and it starts reacting to buttons )
and then in games its verry delayed, laggy. Tested on both amiga and c64 and compared with normal old joystick
i suspect that the fuses might not be getting set correctly?
I use the following commands and in this order.
Fuses :
avrdude -C avrdude.conf -v -patmega328p -cusbasp -Pusb -e -Ulock:w:0x3F:m -Uefuse:w:0xFD:m -Uhfuse:w:0xDE:m -Ulfuse:w:0xFF:m
Bootloader:
avrdude -C avrdude.conf -v -patmega328p -cusbasp -Pusb -Uflash:w:optiboot_atmega328.hex:i -Ulock:w:0x0f:m
Application:
avrdude -C avrdude.conf -v -V -patmega328p -cusbasp -Pusb -b115200 -D -Uflash:w:OpenPSX2AmigaPadAdapter.ino.hex:i
everything seems to go as intended except i get a error on one of the fuses, and then as you can see on last row it says fuses are not the same whatsoever. any idea?
avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0xFD:
avrdude: load data efuse data from input file 0xFD:
avrdude: input file 0xFD contains 1 bytes
avrdude: reading on-chip efuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0x05 != 0xfd
avrdude: verification error; content mismatch
avrdude: safemode: lfuse reads as 62
avrdude: safemode: hfuse reads as D9
avrdude: safemode: efuse reads as 5
avrdude: safemode: efuse changed! Was fd, and is now 5
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK (E:FD, H:D9, L:62)