Ok.. I had a play with AVRDude. I kind of get it now!
I managed to get this running with the R3 as an ISP using:
"avrdude -c arduino -P com3 -p m328p -b 19200 -U lfuse:w:0xFF:m"
"avrdude -c arduino -P com3 -p m328p -b 19200 -U hfuse:w:0xDE:m"
"avrdude -c arduino -P com3 -p m328p -b 19200 -U efuse:w:0x05:m"
This confirms when I verify:
"avrdude -c arduino -P com3 -p m328p -b 19200 -U lfuse:v:0xFF:m"
"avrdude -c arduino -P com3 -p m328p -b 19200 -U hfuse:v:0xDE:m"
"avrdude -c arduino -P com3 -p m328p -b 19200 -U efuse:v:0x05:m"
I get back all confirmed as correct.
I used this sketch again:
"#include <avr/boot.h>
void setup() {
Serial.begin(300);
int lf = boot_lock_fuse_bits_get(GET_LOW_FUSE_BITS);
int hf = boot_lock_fuse_bits_get(GET_HIGH_FUSE_BITS);
int ef = boot_lock_fuse_bits_get(GET_EXTENDED_FUSE_BITS);
Serial.println("Low Fuse Bits: ");
Serial.println(lf, HEX);
Serial.println("High Fuse Bits: ");
Serial.println(hf, HEX);
Serial.println("Extended Fuse Bits: ");
Serial.println(ef, HEX);
}
void loop() {
}"
Which only works at baud 2400 (again 8x what its meant to be!) and returns:
"Low Fuse Bits:
FF
High Fuse Bits:
DE
Extended Fuse Bits:
FD"
I am also getting back a device signature of "0x1e950f" which is (apparently) correct.
Yet still no go on the being able to upload, even though I have a form of TX/RX sending back through the 8u2 I'm trying to link up with.. (Due to the CKDIV8 not working, or something to do with the 8u2).
Why AVRDude see's the fuses as being set correctly and the Arduino IDE can not, I am at a complete loss.
In the meantime I am going to knock up another couple of boards and see if I get the same response..
If anyone has any other info on this please let me know!
Thanks in advance.