Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ESP32C3 does not compile

See original GitHub issue

All default, tasmocompiler 9.0.1

Compiling .pio/build/tasmota32c3/liba9a/mp3_shine_esp32/l3loop.cpp.o
Compiling .pio/build/tasmota32c3/liba9a/mp3_shine_esp32/l3mdct.cpp.o
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp: Assembler messages:
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:101: Error: unrecognized opcode `mulsh a4,a4,s11'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:103: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:104: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:105: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:106: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:107: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:108: Error: unrecognized opcode `mulsh a7,t5,t4'
lib/libesp32_audio/mp3_shine_esp32/src/l3mdct.cpp:109: Error: unrecognized opcode `mulsh a7,t5,t4'
*** [.pio/build/tasmota32c3/liba9a/mp3_shine_esp32/l3mdct.cpp.o] Error 1
lib/libesp32_audio/mp3_shine_esp32/src/l3loop.cpp: Assembler messages:
lib/libesp32_audio/mp3_shine_esp32/src/l3loop.cpp:411: Error: unrecognized opcode `mulsh a4,s11,a4'
lib/libesp32_audio/mp3_shine_esp32/src/l3loop.cpp:419: Error: unrecognized opcode `mulsh a5,s11,a5'
lib/libesp32_audio/mp3_shine_esp32/src/l3loop.cpp:141: Error: unrecognized opcode `mulsh a4,a4,a4'
*** [.pio/build/tasmota32c3/liba9a/mp3_shine_esp32/l3loop.cpp.o] Error 1
========================= [FAILED] Took 136.96 seconds =========================
Environment    Status    Duration
-------------  --------  ------------
tasmota32c3    FAILED    00:02:16.956
==================== 1 failed, 0 succeeded in 00:02:16.956 ====================

Finished. Exit code: 1.

Issue Analytics

State:
Created a year ago
Reactions:1
Comments:8 (2 by maintainers)

Top GitHub Comments

1reaction

benzino77commented, Sep 2, 2022

For now you can choose Tasmota version up to v12.0.2 in the Tasmota Version dropdown field. Probably there is a change in platformio configuration for C3 boards in v12.1.0 and up, which are not handled by TasmoCompiler. I’m currently out of time to look at this, but if there are no importatnt changes for you in Tasmota v12.1.0 or v12.1.1 you can always use v12.0.x.

0reactions

benzino77commented, Sep 3, 2022

Fortunately it was fairly easy to fix. New version v9.0.2 is pushed to dockerhub. Enjoy.