328p Nano, CH340 fuse questions

So I have some random $3 chinese 328p nano, and I'm trying to confirm the actual clock on it. Blink is spot on, but the avrdude -v kinda scares me.

C:\Users\ZZT>avrdude -v -c arduino -p atmega328p -P COM12 -b 57600

avrdude: Version 5.10, compiled on Jan 19 2010 at 10:45:23
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\WinAVR-20100110\bin\avrdude.
conf"

         Using Port                    : COM12
         Using Programmer              : arduino
         Overriding Baud Rate          : 57600
         AVR Part                      : ATMEGA328P
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PC2
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page
      Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  Max
W   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ---
-- ---------
           eeprom        65     5     4    0 no       1024    4      0  3600  36
00 0xff 0xff
           flash         65     6   128    0 yes     32768  128    256  4500  45
00 0xff 0xff
           lfuse          0     0     0    0 no          1    0      0  4500  45
00 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  4500  45
00 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  4500  45
00 0x00 0x00
           lock           0     0     0    0 no          1    0      0  4500  45
00 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0
 0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0
 0 0x00 0x00

         Programmer Type : Arduino
         Description     : Arduino
         Hardware Version: 2
         Firmware Version: 1.16
         Vtarget         : 0.0 V
         Varef           : 0.0 V
         Oscillator      : Off
         SCK period      : 0.1 us

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f
avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0

avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0
avrdude: safemode: Fuses OK

avrdude done.  Thank you.

Any suggestions?

Interesting that this appears to work in the avrdude parameter list:

-p atmega328p

I use this for the part number when it is an atmega328p:

-p m328p

maybe you have a modified avrdude.conf file ?

You usually can’t read actual fuse info via the bootloader.

If you can upload a sketch to it over serial, and blink blinks at the right speed, that proves that the clock speed is what you selected when you compiled the sketch.

The serial bootloaders are really stripped down in order to fit - they generally only do the bare minimum (read and write flash) - all the other stuff that avrdude shows you is non-relevant.

6v6gt: Interesting that this appears to work in the avrdude parameter list:

-p atmega328p

I use this for the part number when it is an atmega328p:

-p m328p

maybe you have a modified avrdude.conf file ?

I seems either the 'id' or the 'desc' value from avrdude.conf is accepted, case-insensitive.

My concern was the Oscillator being off, I've seen some other logs like mine but they showed a different oscillator frequency. As far as the blink test, its hard to say. all the configs I've looked at show ~16mhz, which honestly I thought I needed an external oscillator circuit to pull off.

My main issue is I'm trying to do some IR stuff, and it feels like the CPU isn't fast enough, So I'm looking for more of a way to confirm that is or isn't the case.

As @westfw wrote, also DrAzzy. The bootloader has limited functionality. It cannot read the fuses, that is why they are 0. You have to use ISP programmer to read the fuses correctly.
In adition, this bootloader, which is usually on chinese Nanos, takes 1kB of flash memory and has uploading speed 57600baud. I’m recommending to burn the optiboot bootloader (same as for the UNO) which takes only 512B of flash and with speed for 115200baud.

LordZZT: My main issue is I'm trying to do some IR stuff, and it feels like the CPU isn't fast enough, So I'm looking for more of a way to confirm that is or isn't the case.

I can personally confirm that 8MHz is fast enough to do 'some IR stuff', let alone 16MHz.

Budvar10: which is usually on chinese Nanos, takes 1kB of flash memory and has uploading speed 57600baud. I'm recommending to burn the optiboot bootloader (same as for the UNO) which takes only 512B of flash and with speed for 115200baud.

I don't recall if I ever burned a different bootloader, this thing is from a year or so ago, but i did program an esp80-something hundred using another nano, So I'll look into that.

After playing around with the IR stuff some more, the signals it records are all sorts of off, but I'm just going to chalk it up to using a $0.10 photoresistive ir led.