Issues Uploading to Elegoo Nano on IDE 2.3.2

Used prior references across a couple different posts. At this point I'm at a loss. Been trying to just make this board run to no avail. I have tried disconnecting all circuits, trying example code to test the board, different cables, and fully checked the CH340 drivers and com ports...

Outline of issue is essentially any time an upload starts the code begins then proceeds to lockup. I've attempted waiting it out but I know damn well the example blink code does not take over 6 hours to complete uploading (yes I waited 6 hours to see if it was really that slow) I've checked the board over and nothing appears faulty with the board. I'm not fully fluent in software, but I can confidently say this doesn't appear to be a hardware issue.

Sketch uses 924 bytes (3%) of program storage space. Maximum is 30720 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.
"C:\Users\user\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/bin/avrdude" "-CC:\Users\user\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/etc/avrdude.conf" -v -V -patmega328p -carduino "-PCOM5" -b57600 -D "-Uflash:w:C:\Users\user\AppData\Local\Temp\arduino\sketches\46B501AA1BFB737D2268A3B9E97E908E/Blink.ino.hex:i"

avrdude: Version 6.3-20190619
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "C:\Users\user\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino17/etc/avrdude.conf"

         Using Port                    : COM5
         Using Programmer              : arduino
         Overriding Baud Rate          : 57600

The above code is what the compiler spits out. After it states baud rate nothing else comes out and it continues to "upload" indefinitely. Any help would be appreciated.

Ok Kinda dumb but ended up messing with the loader and swapping off the ATmega328P (Old Bootloader) to the standard ATmega328P and the problem auto resolved.... :confused: I did try this loader before and had the same issue and assumed the old loader was needed. Unsure what changed atp but I guess problem solved for now

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.