vroland / epdiy

EPDiy is a driver board for affordable e-Paper (or E-ink) displays.
https://vroland.github.io/epdiy-hardware/
GNU Lesser General Public License v3.0
1.25k stars 178 forks source link

About use IDF Project #261

Closed dengfengdz closed 5 months ago

dengfengdz commented 8 months ago

Hi! I want to use the ESP-IDF bulid it but have some problem, the error messages is : HINT: The component epdiy could not be found. This could be because: component name was misspelled, the component was not added to the build, the component has been moved to the IDF component manager or has been removed and refactored into some other component. Please look out for component in 'https://components.espressif.com' and add using 'idf.py add-dependency' command. Refer to the migration guide for more details about moved components. Refer to the build-system guide for more details about how components are found and included in the build.

Can you help me analyze it?Thank you!

martinberlin commented 7 months ago

Hello @dengfengdz Please write in detail what are the steps to reproduce what you are experiencing. As far as I know just downloading latest master and building one of the examples I don't get this. It should be explained in detail so another person can reproduce it. Otherwise is very hard to help you.

dengfengdz commented 7 months ago

Hi ! I downloaded the master and Direct use ESP-IDF 5.1 PowerShell open it.As I enter \epdiy-master\examples\dragon to bulid it ,the Warning message is :The component epdiy could not be found. This could be because: component name was misspelled, the component was not added to the build, the component has been moved to the IDF component manager or has been removed and refactored into some other component. 1 2

martinberlin commented 7 months ago

Sorry but I cannot reproduce in Linux. Will try later using a Windows PC but at the moment I don't have access to it. My steps:

git clone https://github.com/vroland/epdiy.git
cd epdiy/examples/dragon
$ prep_idf 
Detecting the Python interpreter
Checking "python3" ...
Python 3.10.12
"python3" has been detected
Checking Python compatibility
Checking other ESP-IDF version.
Adding ESP-IDF tools to PATH...

idf.py build
Successful build.
dengfengdz commented 7 months ago

Thank you,I'm also trying to figure out what's wrong,I used an older version that was compilable.The old version step have to use idf.py menuconfig

martinberlin commented 7 months ago

Update @dengfengdz I will still have a week more to wait until I can grab a Windows PC and test it since I do not really own any laptop with that OS. First thing I do on a laptop is to install Linux and remove Windows.

I still do not understand why you are getting this but will get my hands on a windows PC soon and try to reproduce it.

HINT: Please use the latest main branch (NOT master) and please inform what board are you using to try this so we can reproduce it.

martinberlin commented 7 months ago

I tried reproducing this steps and it works correctly. I really do not know what you are doing wrong but please send me your email (martin@luckycloud.de) and I will add you to join SLACK.

5 2

LOG:

Using Python in D:\Espressif\python_env\idf5.1_py3.11_env\Scripts\
Python 3.11.2
Using Git in D:\Espressif\tools\idf-git\2.39.2\cmd\
git version 2.39.2.windows.1
Checking Python compatibility
Setting IDF_PATH: D:\Espressif\frameworks\esp-idf-v5.1.2

Adding ESP-IDF tools to PATH...
    D:\Espressif\tools\xtensa-esp-elf-gdb\12.1_20221002\xtensa-esp-elf-gdb\bin
    D:\Espressif\tools\riscv32-esp-elf-gdb\12.1_20221002\riscv32-esp-elf-gdb\bin
    D:\Espressif\tools\xtensa-esp32-elf\esp-12.2.0_20230208\xtensa-esp32-elf\bin
    D:\Espressif\tools\xtensa-esp32s3-elf\esp-12.2.0_20230208\xtensa-esp32s3-elf\bin
    D:\Espressif\tools\riscv32-esp-elf\esp-12.2.0_20230208\riscv32-esp-elf\bin
    D:\Espressif\tools\esp32ulp-elf\2.35_20220830\esp32ulp-elf\bin
    D:\Espressif\tools\cmake\3.24.0\bin
    D:\Espressif\tools\openocd-esp32\v0.12.0-esp32-20230921\openocd-esp32\bin
    D:\Espressif\tools\ninja\1.10.2\
    D:\Espressif\tools\idf-exe\1.0.3\
    D:\Espressif\tools\ccache\4.8\ccache-4.8-windows-x86_64
    D:\Espressif\tools\dfu-util\0.11\dfu-util-0.11-win64
    D:\Espressif\frameworks\esp-idf-v5.1.2\tools

Checking if Python packages are up to date...
Requirement files:
 - D:\Espressif\frameworks\esp-idf-v5.1.2\tools\requirements\requirements.core.txt
Python being checked: D:\Espressif\python_env\idf5.1_py3.11_env\Scripts\python.exe
Python requirements are satisfied.

build-log.txt

martinberlin commented 7 months ago

Reopening here since @dengfengdz is not the only getting this

mataide commented 6 months ago

Hey guys, I found a few issues to solve this problem:

  1. Check if you have installed:

image

  1. If you renamed the folder from epdiy to xxxx-epdiy then you will need to replace:

@martinberlin The first one we can add this info into the docs, the second one, I dont know if its possible to avoid this problem and add a tag that wont change even if the folder is renamed.

martinberlin commented 6 months ago

Thanks Marcus, @dengfengdz can please check if this works also for you?

dengfengdz commented 6 months ago

Hi,@martinberlin I'm sorry this solution doesn't apply to me.I have confirmed that I have installed all of the above. My operation differs from yours in that I use the downloaded ZIP file.I don't know what's wrong with that.My current workaround is to use the git command line"git colne ..."This will make my program work.

martinberlin commented 6 months ago

Hello @vroland do you have any idea on how to solve this issue? I really don't since as you can see in the comments I grabbed my Partner Windows laptop and could not reproduce it. It seems, reading between lines, the issue arises when you rename the epdiy folder into something else. And that makes sense, since now epdiy in this version, is ready to be used "as a component". If this is correct then we can safely close here.

"git clone ..."This will make my program work.

Yes @dengfengdz that is the correct way to do it. You just clone it and by default will come with the epdiy name as the component name is.

vroland commented 5 months ago

If that's the root of the issue, I think we can indeed close it. Looks like an issue specific to the build environment.