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

Installation step 2: not a valid identifierline 89: export: `sha1 #11

Closed
krzychb opened this issue Sep 15, 2016 · 5 comments
Closed

Installation step 2: not a valid identifierline 89: export: `sha1 #11

krzychb opened this issue Sep 15, 2016 · 5 comments

Comments

@krzychb
Copy link
Collaborator

krzychb commented Sep 15, 2016

Hi Team,

Following Step 2: Getting the esp-idf repository from github of the installation process on Windows 7 x64, I got the following two messages regarding sha1 (at the end of the full log below):

$ git clone --recursive https://github.com/espressif/esp-idf.git
Cloning into 'esp-idf'...
remote: Counting objects: 3162, done.
remote: Total 3162 (delta 0), reused 0 (delta 0), pack-reused 3162
Receiving objects: 100% (3162/3162), 5.05 MiB | 1.03 MiB/s, done.
Resolving deltas: 100% (1695/1695), done.
Checking connectivity... done.
Submodule 'components/esp32/lib' (https://github.com/espressif/esp32-wifi-lib.git) registered for path 'components/esp32/lib'
Submodule 'components/esptool_py/esptool' (https://github.com/themadinventor/esptool.git) registered for path 'components/esptool_py/esptool'
Cloning into '/esp-idf/components/esp32/lib'...
Cloning into '/esp-idf/components/esptool_py/esptool'...
': not a valid identifierline 89: export: `sha1
': not a valid identifierline 89: export: `displaypath
Submodule path '': checked out '1303c92c1056b7f59b95360b58e70a21cb4a93e1'
': not a valid identifierline 89: export: `sha1
': not a valid identifierline 89: export: `displaypath
Submodule path '': checked out '7c84dd433512bac80e4c01c569e42b4fe76646a7'

I have tried this step twice with the same result.

The /esp-idf/components/esptool_py/esptool directory contains some files and sub directories.
I did not find any leads to this error on https://github.com/themadinventor/esptool repository.

Should I be concerned?

@hardikharpal
Copy link

Hi @krzychb,
Until u got solution from esp32 team,try cloning git by desktop git app.I had some issue too but with desktop git app it worked.

@igrr
Copy link
Member

igrr commented Sep 15, 2016

Seen this message on colleague's windows computer as well. It looked like everything was actually checked out correctly.
Here's a similar error mentioned in msys2 tracker: msys2/MSYS2-packages#30. My guess that that's something with msys2 git, we'll check it...

@projectgus
Copy link
Contributor

(Deleted previous comment because I can reproduce this without any special directories, etc.)

I can confirm @igrr's comment that despite this error everything seems to work fine and the git submodule checkout is 100% valid. So it's nothing you have to worry about for now, provided esp-idf works as expected.

I did notice this path is directly in the msys "root":

Cloning into '/esp-idf/components/esp32/lib'...

Did you mean to run the git checkout from the directory /? (this corresponds to c:\msys32 in Windows). It's OK if you did, just wanted to be sure this isn't unexpected behaviour.

@krzychb
Copy link
Collaborator Author

krzychb commented Sep 16, 2016

@hardikharpal, @igrr, @projectgus - thank you guys for really quick replies and support.

@projectgus - indeed I did git checkout intentionally from '/'.

From deciding to set up the esp-idf to getting esp-idf-template compiled, took me maybe 45 minutes. To get to this point with ESP8266 1.5 years ago has not been so easy for me and I was not sure what to expect now from ESP32 framework. ESP32 Team made it it really accessible and easy to follow.

Congratulations 😄 👍

@krzychb krzychb closed this as completed Sep 16, 2016
@projectgus
Copy link
Contributor

Thanks for the kind words, that's exactly the kind of result we are all aiming for!

I've added a note in our Windows documentation about the weird submodule messages, with a link to this issue. There may eventually be a solution, but at least it's not breaking any functionality.

igrr pushed a commit that referenced this issue Sep 19, 2016
tim-nordell-nimbelink added a commit to tim-nordell-nimbelink/esp-idf that referenced this issue Feb 28, 2019
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 <[email protected]>
tannewt added a commit to tannewt/esp-idf that referenced this issue Sep 20, 2023
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

4 participants