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.

Sign up for GitHub

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

Jump to bottom

esp-idf build error #9

Closed
EFudd opened this issue Sep 11, 2016 · 3 comments
Closed

esp-idf build error #9

EFudd opened this issue Sep 11, 2016 · 3 comments
Labels
Status: Opened Issue is new

Comments

@EFudd
Copy link

EFudd commented Sep 11, 2016

Performed the build serval times using crosstool-NG and several other toolchains (on latest Debian). Always receive error on xtensa_context.S line 458 -> 224 is not a valid register for rsr.
CPENABLE is def'ed as 224.
@igrr
Copy link
Member

igrr commented Sep 11, 2016 •
edited
Loading

I suspect there may be a problem with the toolchain.

Have you followed these instructions to build the toolchain?
https://github.com/espressif/esp-idf/blob/master/docs/linux-setup.rst#alternative-step-1-compile-the-toolchain-from-source-using-crosstool-ng

What are the "several other toolchains" are you referring to?

If you have built the toolchain using crosstool-NG, please run the following diagnostic command and copy its output here:

echo -ne "#include \"xtensa/config/core-isa.h\"\n#pragma message XCHAL_CORE_ID" | xtensa-esp32-elf-gcc -c -o /dev/null -xc -

(make sure xtensa-esp32-elf-gcc is in your PATH before running this).

@EFudd
Copy link
Author

EFudd commented Sep 13, 2016

Thank you for that rapid respons:

toolchains used in this order:

  1. built: github.com/jcmvbkbc/crosstool-NG - esp32 builed failed at
    xtensa_context.S
  2. prebuilt toolchain: github.com/jmattsson/nodemcu-prebuilt-toolchains
  • esp32 builed failed at xtensa_context.S
    3) built: github.com/espressif/crosstool-NG - esp32 build failed at
    xtensa_context.S

I tried to isolate the various builds but there must have been some leak
between them.

Rebuilt github.com/espressif/crosstool-NG on a fresh install of Debian
Jessie.
The esp32-idf builds were succesful.

Unfortunately, mix & match with tool chains doesn't work very well.

Regards, E.F.

On 9/11/2016 3:46 PM, Ivan Grokhotkov wrote:

I suspect there may be a problem with the toolchain.

Have you followed these instructions to build the toolchain?
https://github.com/espressif/esp-idf/blob/master/docs/linux-setup.rst#alternative-step-1-compile-the-toolchain-from-source-using-crosstool-ng

What are the "several other toolchains" are you referring to?

If you have built the toolchain using crosstool-NG, please run the
following diagnostic command and copy its output here:

|echo -ne "#include "xtensa/config/core-isa.h"\n#pragma message
XCHAL_CORE_ID" | xtensa-esp32-elf-gcc -c -o /tmp/1.o -xc - |

(make sure xtensa-esp32-elf-gcc is in your PATH before running this).

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#9 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADjanbV_es9tIzM-p-LnrETzfM0ul3hMks5qpBQ0gaJpZM4J58UC.

@igrr
Copy link
Member

igrr commented Sep 13, 2016

Great to know that building from https://github.com/espressif/crosstool-NG worked for you!

Just a note to other people who may be reading this: Espressif provides prebuilt toolchains for all platforms, links may be found in docs/linux-setup.rst, docs/macos-setup.rst, docs/windows-setup.rst.

Toolchain in https://github.com/jmattsson/nodemcu-prebuilt-toolchains is not guaranteed to work.

@igrr igrr closed this as completed Sep 13, 2016
@nathanjel nathanjel mentioned this issue Jan 15, 2017
Closed
@lollizze lollizze mentioned this issue Jan 25, 2017
Closed
@andriyadi andriyadi mentioned this issue Apr 26, 2017
Closed
@abhimanyuv1 abhimanyuv1 mentioned this issue Feb 12, 2018
Closed
@kluverp kluverp mentioned this issue Sep 18, 2018
Closed
@my-abousamra my-abousamra mentioned this issue Oct 11, 2018
Closed
@ammaree ammaree mentioned this issue Nov 22, 2018
Closed
@markingle markingle mentioned this issue Dec 4, 2018
Closed
tim-nordell-nimbelink added a commit to tim-nordell-nimbelink/esp-idf that referenced this issue Feb 28, 2019
@tim-nordell-nimbelink
pm: Fix atomicity of rtos idle lock acquiring
9983c41 
It's possible for esp_pm_impl_isr_hook(...) to be nested due to the fact
that interrupts are nested on the ESP32.  To fix this we need to place the
acquiring of the lock into a critical section to ensure it does not get
nested on the system, otherwise the system will never release the idle
lock when this occurs and will not go into lower power states.

A sample backtrace encountering this (the code was instrumented to go into
a while(1) loop when the condition was hit to get this backtrace) from
commit d7a7a68:

    #0  leave_idle () at esp-idf/components/esp32/pm_esp32.c:444
    espressif#1  0x4008143a in esp_pm_impl_isr_hook () at esp-idf/components/esp32/pm_esp32.c:473
    espressif#2  0x40082750 in _xt_medint2 () at esp-idf/components/freertos/xtensa_vectors.S:1243
    espressif#3  0x4000bff0 in ?? ()
    espressif#4  0x40090bb0 in vTaskExitCritical (mux=0x3ffbd230) at esp-idf/components/freertos/tasks.c:4304
    espressif#5  0x40081758 in esp_pm_lock_acquire (handle=0x3ffbd218) at esp-idf/components/esp32/pm_locks.c:126
    espressif#6  0x40081399 in leave_idle () at esp-idf/components/esp32/pm_esp32.c:440
    espressif#7  0x4008143a in esp_pm_impl_isr_hook () at esp-idf/components/esp32/pm_esp32.c:473
    espressif#8  0x400826b8 in _xt_lowint1 () at esp-idf/components/freertos/xtensa_vectors.S:1154
    espressif#9  0x400d14b0 in esp_pm_impl_waiti () at esp-idf/components/esp32/pm_esp32.c:483
    espressif#10 0x400d2c77 in esp_vApplicationIdleHook () at esp-idf/components/esp32/freertos_hooks.c:63
    espressif#11 0x40091008 in prvIdleTask (pvParameters=0x0) at esp-idf/components/freertos/tasks.c:3412
    espressif#12 0x40090344 in vPortTaskWrapper (pxCode=0x40090ffc <prvIdleTask>, pvParameters=0x0) at esp-idf/components/freertos/port.c:143

Signed-off-by: Tim Nordell <tim.nordell@nimbelink.com>
@Sermus Sermus mentioned this issue May 11, 2019
Closed
@ghost ghost mentioned this issue Jul 8, 2019
Closed
@iltis42 iltis42 mentioned this issue Apr 12, 2020
Closed
@joehui joehui mentioned this issue Jun 4, 2020
Open
@kannannair084 kannannair084 mentioned this issue Oct 23, 2020
Closed
@norventa norventa mentioned this issue Apr 12, 2021
Closed
4 tasks
@7erduk 7erduk mentioned this issue Nov 8, 2021
Closed
@achao1104 achao1104 mentioned this issue Nov 19, 2021
Closed
@wreyford wreyford mentioned this issue Jan 8, 2022
Open
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jul 12, 2022
tannewt pushed a commit to tannewt/esp-idf that referenced this issue Dec 16, 2022
@dhalbert
Merge pull request espressif#9 from tannewt/fix_esp_mdns_conflict
20c6d4a 
Make mdns hostname mangling check stricter
Open
3 tasks
@sxsx2yzyz sxsx2yzyz mentioned this issue May 10, 2023
Closed
3 tasks
@dimonysos dimonysos mentioned this issue Jan 18, 2024
Closed
3 tasks
@pragulka pragulka mentioned this issue Sep 9, 2024
Closed
3 tasks
@vortex314 vortex314 mentioned this issue Jan 12, 2025
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Opened Issue is new
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@EFudd @igrr @espressif-bot