The problem with the previous board was that I had mosfets to drive motors on the same pins as the pins needed to program the bootloader to the board.
I am creating another one of these boards and am having a similar issue, except my board is basically bare. It has the ATMEGA328P, an ICSP port to program the board, the 16MHz resonator, and a capacitor from pin 20 (AREF) to ground. When loading the bootloader, I get the same message as if the board was not even plugged in. (Device Signature = 0x00000000)
I don't think the nano has a pullup resistor on the reset pin, but I can still give that a try.
Also, I should clarify:
I have two of these PCBs and one of them has the four components listed above, and one of them has other capacitors for 5v regulation and the reset button. Both of these boards have the same problem.
Please see the schematics below:
(Ignore the other nets, they're not soldered on either yet.)
I know it's a weird question, is RESET really connected to the ICSP header?
The second image has a Hierarchical label, in the first image it looks like Local label.
aseidloop:
I don't think the nano has a pullup resistor on the reset pin, but I can still give that a try.
If you don't pullup RESET pin of your target MCU, you cannot guarantee it's state...
In all my 328P standalone designs, i add 10K pullup on RESET pin and 0,1uF capacitor on VCC and AVCC pins
I know it's a weird question, is RESET really connected to the ICSP header?
The second image has a Hierarchical label, in the first image it looks like Local label.
What is not pictured is where RESET comes from another hierarchical label to a local label when connecting to the USB-UART chip. None of that is connected so I did not picture it.
If you don't pullup RESET pin of your target MCU, you cannot guarantee it's state...
In all my 328P standalone designs, i add 10K pullup on RESET pin and 0,1uF capacitor on VCC and AVCC pins
This makes sense to me, I will give it a try when I can get back into our school's lab. Thank you.
In fact, I've tried this with several different master and slave combinations and all of them give me the error as if it's not even connected. Really confused as to why this isn't working.
I remember I spend a day once to find out in the end that one of the wires of my setup had a bad crimp in its connector, and did not make a connection to the pinheader on the board.
You have PB3 (MOSI) connected to something called FR. What are the parts that make up for FR?
Normally that would be connected to a MOSFET and some an LED, but at the moment, none of my boards have any of that on it. So it is essentially only connected to MOSI at the moment.
Also, I was convinced it was bad parts or a bad board or something, but this same things happens on all 5 custom boards with both of my master Nano's. I'm convinced it has to be something with the process, but I don't know what, and can't prove it.
Well, you have to check if the problem is on the nano side (master - programmer) or on the board side (slaves being programmed).
Put a 328P DIP on a breadboard with just 10k pullup on RESET pin and 0,1uF at VCC pins. Burn boatloader @ 8Mhz internal with your master nano. If you can program it, the problem is on the boards. If not, the problem is on your master nano.
I tried exactly what you said and got the same result. I also tried using brand new arduino nanos, and that didn't work. I could get the arduino nanos to burn the bootloaders to eachother, but that was it. No configuration (I tried everything you said plus a bit) was able to burn the bootloader to the replica board. Details to follow about the specifics:
-Old Arduino to DIP 328P
-Old Arduino (with pullup resistor/vcc cap)
-New Arduino to DIP 328P
-New Arduino to DIP 328P (with pullup resistor/vcc vap)
-New Arduino to another new arduino (no pullup resistor or cap): did work, no errors
-New Arduino to replica board
-New Arduino to replica board (with pullup resistor/vcc cap)
The only thing I managed to get working was one arduino to the other arduino
