IDF Version Information

[cbarfield]

This may be a silly question, but here's our scenario:

• Coworker and I both have checked out the latest head of Release/v4.1 of the IDF
• Both of our git logs show the latest commit as c3324a82a3e6beb30d5c24b9828c01ced3864d7f
• One of us gets the following output for idf.py --version v4.1-520-g3c324a82a
• The other of us gets v4.1-520-gc3432a8
• When we build identical firmware, the IDF version is reported as the two different values in our boot logs
• One of us is on Linux
• One of us is on Windows

I realize that everything after the "g" is a unique portion of the commit SHA, but why would this be reported differently? Could it be git versions? A difference between Windows and Linux tools?

[chegewara]

Looks like both of you may have issue with git pull. As you can see here its log from master branch:

Code: Select all

I (731) cpu_start: ESP-IDF:          v4.3-dev-2136-gb0150615d-dirty

and commit:
https://github.com/espressif/esp-idf/co ... b559f480e2

Also remember you need to update submodules:

Code: Select all

git submodule update --init --recursive

[cbarfield]

Well, neither of us are working from master. We're both working from release/4.1. And our git logs show the correct details for that branch:

https://github.com/espressif/esp-idf/tree/release/v4.1

Code: Select all

commit c3324a82a3e6beb30d5c24b9828c01ced3864d7f
Merge: be7b859 50cf0c2
Author: Jiang Jiang Jian <jack@espressif.com>
Date:   Thu Nov 19 16:27:45 2020 +0800

    Merge branch 'bugfix/wpa3_pmkcache_expiry_workaround_v4.1' into 'release/v4.1'

    wpa_supplicant: Increase PMK Lifetime to a very high value

    See merge request espressif/esp-idf!11275

I will look into the submodules, though. Thanks!

[chegewara]

Like i said, both of you have some issues with git clone/pull. Here is release/v4.1 hello-world example:

Code: Select all

I (194) boot: Loaded app from partition at offset 0x10000
I (194) boot: Disabling RNG early entropy source...
I (195) cpu_start: Pro cpu up.
I (199) cpu_start: Application information:
I (204) cpu_start: Project name:     hello-world
I (209) cpu_start: App version:      v4.1-520-gc3324a82a
I (215) cpu_start: Compile time:     Dec 17 2020 12:51:24
I (221) cpu_start: ELF file SHA256:  381a0a5b430fb889...
I (227) cpu_start: ESP-IDF:          v4.1-520-gc3324a82a
I (233) cpu_start: Starting app cpu, entry point is 0x40081048

Code: Select all

commit c3324a82a3e6beb30d5c24b9828c01ced3864d7f (HEAD -> release/v4.1, origin/release/v4.1)
Merge: be7b85919 50cf0c2d2
Author: Jiang Jiang Jian <jack@espressif.com>
Date:   Thu Nov 19 16:27:45 2020 +0800

    Merge branch 'bugfix/wpa3_pmkcache_expiry_workaround_v4.1' into 'release/v4.1'
    
    wpa_supplicant: Increase PMK Lifetime to a very high value
    
    See merge request espressif/esp-idf!11275

App version in bootloader should have included part of SHA commit after g, which stands github:

Code: Select all

App version:      v4.1-520-gc3324a82a

[dastoned]

[*]One of us gets the following output for idf.py --version v4.1-520-g3c324a82a
[*]The other of us gets v4.1-520-gc3432a8

This tag is created by running a command "git describe --always --tags --dirty --long" (or something similar) in the IDF source directory. To my eyes the first one looks correct and the second one is clipped.

Try it manually. If you and your colleague get different outputs, the problem is in your git clients.