Skip to content
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

Build led_light error for ESP32C2 (MEGH-5195) #296

Open
3 tasks done
rillhu opened this issue Jan 13, 2024 · 1 comment
Open
3 tasks done

Build led_light error for ESP32C2 (MEGH-5195) #296

rillhu opened this issue Jan 13, 2024 · 1 comment

Comments

@rillhu
Copy link

rillhu commented Jan 13, 2024

Answers checklist.

  • I have read the Rainmaker documentation and the issue is not addressed there.
  • I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
  • I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

IDF / ESP32-Arduino version.

idf-v5.1.2

Operating System used.

Windows

How did you build your project?

Command line with Make

Development Kit.

ESPC2-12

What is the expected behavior?

Build led_light successfully

What is the actual behavior?

Build the example with below error message:

C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c: In function 'read_hmac_key':
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c:303:47: error: 'ESP_EFUSE_OPTIONAL_UNIQUE_ID' undeclared (first use in this function)
  303 |     esp_err_t err = esp_efuse_read_field_blob(ESP_EFUSE_OPTIONAL_UNIQUE_ID, out_hmac_key, hmac_key_size * 8);
      |                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c:303:47: note: each undeclared identifier is reported only once for each function it appears in
[1023/1033] Building C object esp-idf/esp_rainmaker/CMakeFiles/__idf_esp_rainmaker.dir/src/ota/esp_rmaker_ota.c.obj
[1024/1033] Building C object esp-idf/esp_rainmaker/CMakeFiles/__idf_esp_rainmaker.dir/src/core/esp_rmaker_local_ctrl.c.obj
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the C:\Z\esp-rainmaker\examples\led_light\build\log\idf_py_stderr_output_17084 and C:\Z\esp-rainmaker\examples\led_light\build\log\idf_py_stdout_output_17084

Steps to reproduce.

Step 1:
PS C:\Z\esp-idf-v5.1.2> .\export.ps1

Step 2:
PS C:\Z\esp-idf-v5.1.2> cd C:\Z\esp-rainmaker\examples\led_light
PS C:\Z\esp-rainmaker\examples\led_light> idf.py fullclean

Step 3:
PS C:\Z\esp-rainmaker\examples\led_light> idf.py flash monitor

Build Logs.

Step 1:
PS C:\Z\esp-idf-v5.1.2> .\export.ps1

Detected installed tools that are not currently used by active ESP-IDF version.
For removing old versions of ccache, cmake, dfu-util, openocd-esp32, riscv32-esp-elf, xtensa-esp32-elf, xtensa-esp32s2-elf, xtensa-esp32s3-elf use command 'python.exe C:\Z\esp-idf-v5.1.2\tools\idf_tools.py uninstall'
For free up even more space, remove installation packages of those tools. Use option 'python.exe C:\Z\esp-idf-v5.1.2\tools\idf_tools.py uninstall --remove-archives'.


Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
    idf.py build

Step 2:
PS C:\Z\esp-idf-v5.1.2> cd C:\Z\esp-rainmaker\examples\led_light
PS C:\Z\esp-rainmaker\examples\led_light> idf.py fullclean

Executing action: fullclean
Executing action: remove_managed_components
Done

PS C:\Z\esp-rainmaker\examples\led_light> idf.py set-target esp32c2

...
ts/spiffs C:/Z/esp-idf-v5.1.2/components/tcp_transport C:/Z/esp-idf-v5.1.2/components/ulp C:/Z/esp-idf-v5.1.2/components/unity C:/Z/esp-idf-v5.1.2/components/usb C:/Z/esp-idf-v5.1.2/components/vfs C:/Z/esp-idf-v5.1.2/components/wear_levelling C:/Z/esp-idf-v5.1.2/components/wifi_provisioning C:/Z/esp-idf-v5.1.2/components/wpa_supplicant C:/Z/esp-rainmaker/examples/common/ws2812_led
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Z/esp-rainmaker/examples/led_light/build

Step 3:
PS C:\Z\esp-rainmaker\examples\led_light> idf.py flash monitor

Executing action: flash
Serial port COM3
Connecting....
Detecting chip type... ESP32-C2
Running ninja in directory C:\Z\esp-rainmaker\examples\led_light\build
...
FAILED: esp-idf/esp_rainmaker/CMakeFiles/__idf_esp_rainmaker.dir/src/core/esp_rmaker_claim.c.obj
...
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c: In function 'read_hmac_key':
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c:303:47: error: 'ESP_EFUSE_OPTIONAL_UNIQUE_ID' undeclared (first use in this function)
  303 |     esp_err_t err = esp_efuse_read_field_blob(ESP_EFUSE_OPTIONAL_UNIQUE_ID, out_hmac_key, hmac_key_size * 8);
      |                                               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Z/esp-rainmaker/components/esp_rainmaker/src/core/esp_rmaker_claim.c:303:47: note: each undeclared identifier is reported only once for each function it appears in
[1023/1033] Building C object esp-idf/esp_rainmaker/CMakeFiles/__idf_esp_rainmaker.dir/src/ota/esp_rmaker_ota.c.obj
[1024/1033] Building C object esp-idf/esp_rainmaker/CMakeFiles/__idf_esp_rainmaker.dir/src/core/esp_rmaker_local_ctrl.c.obj
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the C:\Z\esp-rainmaker\examples\led_light\build\log\idf_py_stderr_output_17084 and C:\Z\esp-rainmaker\examples\led_light\build\log\idf_py_stdout_output_17084

More Information.

No response

@github-actions github-actions bot changed the title Build led_light error for ESP32C2 Build led_light error for ESP32C2 (MEGH-5195) Jan 13, 2024
@shahpiyushv
Copy link
Collaborator

@rillhu esp32c2 is not yet an officially supported platform for RainMaker. We will add it soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants