Skip to content

[ESP32-C2] setCpuFrequencyMhz(): Bad frequency: 120 MHz! Options are: 240, 160, 80, 26 and 13 MHz #8955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
TD-er opened this issue Dec 4, 2023 · 1 comment · Fixed by #8956
Closed
1 task done
Assignees

Comments

@TD-er
Copy link
Contributor

TD-er commented Dec 4, 2023

Board

ESP32-C2

Device Description

Just any ESP32-C2

Hardware Configuration

Nothing attached to the board

Version

latest master (checkout manually)

IDE Name

PlatformIO

Operating System

Windows 11

Flash frequency

40MHz

PSRAM enabled

no

Upload speed

115200

Description

Cannot set the default CPU frequency, even though it is initially running at this frequency.
Debug error:

[   401][E][esp32-hal-cpu.c:195] setCpuFrequencyMhz(): Bad frequency: 120 MHz! Options are: 240, 160, 80, 26 and 13 MHz

Reported frequencies of this board:

  • ESP Chip ID: 1005908 (0x0F5954)
  • ESP Chip Frequency: 120 MHz
  • ESP Crystal Frequency: 26 MHz
  • ESP APB Frequency: 40 MHz
  • ESP Chip Model: ESP32-C2
  • ESP Chip Revision: 1.0

Sketch

setCpuFrequencyMhz(120);

Debug Message

[   401][E][esp32-hal-cpu.c:195] setCpuFrequencyMhz(): Bad frequency: 120 MHz! Options are: 240, 160, 80, 26 and 13 MHz

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

  • I confirm I have checked existing issues, online documentation and Troubleshooting guide.
@TD-er TD-er added the Status: Awaiting triage Issue is waiting for triage label Dec 4, 2023
@P-R-O-C-H-Y P-R-O-C-H-Y added Status: Needs investigation We need to do some research before taking next steps on this issue and removed Status: Awaiting triage Issue is waiting for triage labels Dec 4, 2023
@P-R-O-C-H-Y P-R-O-C-H-Y self-assigned this Dec 4, 2023
@P-R-O-C-H-Y
Copy link
Member

@TD-er Thank you for reporting. I will take a look fix the issue.

@P-R-O-C-H-Y P-R-O-C-H-Y added Status: Solved and removed Status: Needs investigation We need to do some research before taking next steps on this issue labels Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants