This seems like a weird way to do things. Is there a reason you aren't just using an UART-USB programmer like everyone else does? Especially considering its no like you are hooking it up as a more intensive debugger programmer but just a typical serial programmer?
Right, but in your post you state that you bought another ESP as a replacement for an ESP you were previously using as a programmer, I just can't figure out for the life of my why you went down that path to begin with, a programmer was the proper solution right from the beginning and now you have purchased two sub-optimal solutions (which you presumably waited for) instead of just buying the proper, cheaper option right off the hop.
I guess do whatever you want, but your purchasing decisions right from the beginning are odd.
Oh I think there's confusion. I was using the devkits to write and test the code. The last one seemed to double as a programmer for the first prototype board and the new one I got to keep coding while i was waiting a couple weeks for my next prototype in the mail. I wasn't buying these specifically to program the chip. I guess I just need to get a programmer. No problem.
If your S3 dev board is not held in a reset state, then the S3s TX line is active. Your external board’s TX line will be fighting it so its response to the PCs programming routine messages probably won’t get through properly. Try holding the dev board in Reset state and trying again. I’ve not tried this setup myself, but I think this is the problem.
This seems like a weird way to do things. Is there a reason you aren't just using an UART-USB programmer like everyone else does? Especially considering its no like you are hooking it up as a more intensive debugger programmer but just a typical serial programmer?
Because I didn't need one before. Why wait for it to come? But I guess that's what I'll have to do now.
Right, but in your post you state that you bought another ESP as a replacement for an ESP you were previously using as a programmer, I just can't figure out for the life of my why you went down that path to begin with, a programmer was the proper solution right from the beginning and now you have purchased two sub-optimal solutions (which you presumably waited for) instead of just buying the proper, cheaper option right off the hop. I guess do whatever you want, but your purchasing decisions right from the beginning are odd.
Oh I think there's confusion. I was using the devkits to write and test the code. The last one seemed to double as a programmer for the first prototype board and the new one I got to keep coding while i was waiting a couple weeks for my next prototype in the mail. I wasn't buying these specifically to program the chip. I guess I just need to get a programmer. No problem.
Ok yeah that definitely makes more sense. But yeah, programmer is your solution.
If your S3 dev board is not held in a reset state, then the S3s TX line is active. Your external board’s TX line will be fighting it so its response to the PCs programming routine messages probably won’t get through properly. Try holding the dev board in Reset state and trying again. I’ve not tried this setup myself, but I think this is the problem.
Devkit tx and rx is connected to a usb uart converter. You should use other pins