ATmega4809 weird behavior #189
Comments
|
Try pressing the reset button manually after pressing upload. If that
works, the auto reset circuitry is not working. Check whether capacitor is
correct value or the DTR connection is proper.
…On Mon, 25 Dec 2023, 22:44 Dejan Petrović, ***@***.***> wrote:
Hi,
I made a few boards using the ATmega4809 (even 3208), and everything went
fine. I burned the bootloader easily with a jtag2updi programmer. The
onboard bridge was usually the CP2102, on UART0. Zero problems.
Now I have a design with pretty much a barebone setup and I have a problem.
Now I use the CH340C and 4809. I burned the bootloader successfully.
First, I uploaded the Blink sketch. No problems. Second, I uploaded the
same sketch, but with a smaller delay. The sketch couldn't be uploaded. It
spits out:
Arduino: 1.8.19 (Windows 10), Board: "ATmega4809, 48 pin standard, EEPROM
retained, Reset, BOD 2.6V, Internal 16 MHz, Optiboot (UART0 default pins)"
Sketch uses 752 bytes (1%) of program storage space. Maximum is 48640
bytes.
Global variables use 4 bytes (0%) of dynamic memory, leaving 6140 bytes
for local variables. Maximum is 6144 bytes.
avrdude error: programmer is not responding
avrdude warning: attempt 1 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 2 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 3 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 4 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 5 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 6 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 7 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 8 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 9 of 10: not in sync: resp=0x00
avrdude error: programmer is not responding
avrdude warning: attempt 10 of 10: not in sync: resp=0x00
avrdude error: unable to open programmer arduino on port COM13
avrdude error: unable to open programmer arduino on port COM13
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
It turns out I have a problem with a UART bridge. I changed both the
CH340C and the 4809. Nothing. I burned the bootloader again. It works. One
sketch, ok. The second sketch, it doesn't. And so on...
This is the schematic:
sch.png (view on web)
<https://github.com/MCUdude/MegaCoreX/assets/30090189/8f8bc4a7-ea41-404f-b4db-92f137dd54a3>
I soldered only the components around the 4809 and the CH340C. I haven't
soldered any LED or a button. Only an LED on D36.
Any idea what is wrong here?
—
Reply to this email directly, view it on GitHub
<#189>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGI4KT25NSOYW63QM5AQCTYLGGOPAVCNFSM6AAAAABBCNHJB2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TKNZSGYZDGNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
LOL. I somehow soldered the wrong cap value on DTR. It is 0603, damn small. |
|
How'd you even read the value of smd cap? None of mine have any indication on them of their value whatsoever. When you put caps back into the wrong bin (this happened to me - a whole new load of 1uF's into 2-300 0.1's. They looked the same...) there is only one thing to do. Throw the capacitors away, wipe the parts and solder paste off the boards you were assembling, and try again when you order of new caps has arrived. Curious - what was the value of the cap that failed to work? I am under the impression that an exceptionally wide range of values will "work" well enough. |
|
I have no idea. Didn't even bother to measure it. I just noticed that the color of the soldered cap is not the one on the other 100nF and not the same size. And, of course, I throw it away. I have never experienced this failure. But, you learn something new every day. |
|
Aah, see I have in both of my 0805 bins for 0.1 and 1.0 uF both common thicknesses for 0805, so they'd be nigh indistinguishable by visual inspection. I have distinguished mixed capacitors of two makes based on the shape of their terminations (different manufacturers do it subtly differently!) when color didn't suffice (usually if you have references that are known to be either part, you can find some marker to distinguish them either because they're done by different companies with slightly different stylings, or because they're not the same color (though the colors may only be distinguishable side-by-side.) Grey ceramics are almost always very low value C0G caps, while the class II's are yellow to brown. There's a region between pF and .0x uF where you can't have much confidence, but conveniently, that's also the three-order-of-magnitude gap in commonly used capacitor values for most digital electronics. |
Hi,
I made a few boards using the ATmega4809 (even 3208), and everything went fine. I burned the bootloader easily with a jtag2updi programmer. The onboard bridge was usually the CP2102, on UART0. Zero problems.
Now I have a design with pretty much a barebone setup and I have a problem.
Now I use the CH340C and 4809. I burned the bootloader successfully. First, I uploaded the Blink sketch. No problems. Second, I uploaded the same sketch, but with a smaller delay. The sketch couldn't be uploaded. It spits out:
It turns out I have a problem with a UART bridge. I changed both the CH340C and the 4809. Nothing. I burned the bootloader again. It works. One sketch, ok. The second sketch, it doesn't. And so on...
This is the schematic:
I soldered only the components around the 4809 and the CH340C. I haven't soldered any LED or a button. Only an LED on D36.
Any idea what is wrong here?
The text was updated successfully, but these errors were encountered: