Bad connections between ftdi and pro mini re-soldered. Now each connection between ftdi andPro mini is continuous,
The first listed problem ("programmer is not responding") no longer occures, BUT
2nd error respo still occurs, but with alternating error code: 020 alternating with 030
Continuity checked after the test; EAch connection still is good.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt [x] of 10 not in sync: resp=0x03
Pro Mini connecting to COM12 through Sparkfun FTDI Basic
Windows Device Manager shows Connection to COM12 but not labelled as Arduino.
Attempt to upload to Pro Mini consistently fails when I use Sparkfun FDT1 and consistently fails when I use Sparkfun FDTI232.
HOWEVER upload DOES work when using the tutorial which recommends using a UNO that is uploaded with the "Arduino ISP" method (https://docs.arduino.cc/built-in-examples/arduino-isp/ArduinoISP). Of course, this means keeping the UNO/ISP connected when running the sketch. One sketch sets up one HC-05 as "master" and another with the HC-05 as slave.
The simpler upload which works with the Arduino/ISP also fails when I use either FTDI module.
The consistent error message is
"avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x20
Failed uploading: uploading error: exit status 1"
The sketch code follows:
int the_count;
void setup() {
// put your setup code here, to run once:
pinMode(8, OUTPUT);
Serial.begin(9600);
Serial.print("Well, we're loaded.");
digitalWrite(8, HIGH);
delay(5000);
digitalWrite(8, LOW);
delay(5000);
digitalWrite(8, HIGH);
delay(5000);
digitalWrite(8, LOW);
delay(5000);
the_count = 0;
}
void loop() {
the_count++;
if ((the_count > 1000) && (the_count < 2000)) {
digitalWrite(8, HIGH);
}
if (the_count == 2000) {
digitalWrite(8, LOW);
Serial.println("\t\t LED should be off.");
delay(5000);
the_count = 0;
}
}
Note that when you do an "Upload Using Programmer", it erases the bootloader on the Pro Mini board. After that, it is expected that all attempts to upload via the FTDI module will fail with this "not in sync" error because the bootloader is required for that type of upload. For this reason, you must use the Arduino IDE's Tools > Burn Bootloader feature with your "Arduino as ISP" connected to the board in order to replace the bootloader before uploading to the board with the FTDI module.
I understand the issue (RX/TX) you raise, but, the same problem occurs with the simpler code (the blinky one) I included in my posting. I did this because I realised that the RX/TX problem comlicated the discussion.
Thank you for the bootloader information. I have to report, though, that the FDTI problems emerged long before I used the "Arduino as ISP" method. My attempts "back then" to "burn loaders (w/o the UNO) encountrered (repeatedly) lack of (cannot find) Programmer.
I will test out your proposal, today (March 4). thank you, ptillisch.
This is odd. If you are able to do an "Upload Using Programmer" operation you should definitely be able to do a "Burn Bootloader" operation with the same wiring and IDE configuration.
True, that, but the whole issue of uploading to a Pro Mini has bothered me for a few months.
By the way, I simply do a simple Upload, not the "Upload using programmer" selection from the IDE (okay, use the upload icon on the IDE).
Two Sparkfun FDTI devices consistently fail to do the job. I also tried to "Burn Bootloader" through these decives; that also failed. I remain totally confused. I assume (probably I am wrong) that I must keep the Arduino/ISP connected to the Pro Mini to use the uploaded sketch. I know; I have to test that issue (meaning disconnect the Arduino/ISP) to prove or disprove that last question ("needing the Arduino/ISP connected"). I need something to run the sketch on the Pro Mini without having to upload to start the sketch. Maybe upload then disconnect the Arduino/ISP. My reason for keeping the things connected is the supply of pwoer to the Pro Mini. Maybe the FDTI devices can do that, at least.
Yes; why do I keep on trying to use the Pro Minis? Stubborn, I admit. I took a liking to the Pro Mini a bit of time back (like, about a year).
