Architecture advice please?

[jan.didden]

Some weekend reading for those interested in the practicalities of what I am trying to do.

Have a great weekend,

Jan

[jan.didden]

Hi Leigh, yes I did that exactly. The only deviation was that the instructions tell you to select ' v4.1 (release version)' of the EDF-IDF while version 'v4.1.4 (release version)' was the only 4.1 available. There was also a choice 'release /v4.1 (release branch)' , no idea what that is, I just ignored that.
Install went fine, but I had to run the install.bat in the esp-idf folder to install a bunch of dependencies, which was not detailed in the install guide.
I got back to where I was yesterday:, after compiling to hex:

Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
idf.py build

Executing action: all (aliases: build)
Running cmake in directory c:\users\jandi\desktop\esp32_testbed\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=1 c:\users\jandi\desktop\esp32_testbed"...
ERROR: C:\Users\jandi\.espressif\python_env\idf5.0_py3.7_env\Scripts\python.exe doesn't support asyncio. The issue can be worked around by re-running idf.py with the "--no-hints" argument.

So what does it mean ' go to the project directory and run ' idf.py build' ? Is that a command-prompt command that I need to run when CD'ing to the project directory? Or is it part of the compile script?

Have a great weekend,

Jan

[LeighM]

That message is output from an ESP-IDF script that runs when Flowcode invokes the ESP build process.
(And can be ignored)

It looks as though the build is still using IDF V5.
So looks like V5, or remnants of it, are still installed.
Unfortunately, it looks like you might need to repeat the uninstall and reinstall.
Also after uninstall delete any ESP related directories, including the hidden .espressif directory on your user home directory.
Hope that helps
Leigh

[mnfisher]

One very interesting feature of the esp32 is the RMT (Remote Transceiver) - this allows sending or receiving IR signals (among other things) in hardware...

How goes it installing the tool chain?

Martin

[jandidden]

Sorry guys for the long silence. In my zeal to delete all remnants of ESP-IDF V5 I must have been a bit too enthousiastic and crashed Windows. I had to reset Windows, which means I lost all apps and had to rebuild everything. Lost my login to this fine forum, forgot password was disabled, contact board manager was disabled, so I registered with new identity. Don't tell anyone. Had to promis the missus to take her out on Valentine's eve to make up for the lost weekend ...
But in the end I got the ESP environment installed correct and can run a Build to Hex without errors.
So, I'm getting there. But I get to old for this sh*t.
Thanks everybody for valuable pointers.

Jan

[mnfisher]

Hi Jan,

Welcome back - that sound's a bit like the old del *.* problems of old.

Still - nice 'streamlined' Windows install now And esp-idf successfully installed too...

Martin

[jandidden]

Yes, still haven't everything recovered yet, but all looks OK now.
Ordered some ESP12 type modules from Mouser, looking forward to beating them into shape

Jan

[jandidden]

So far I have been compiling to hex and then load the hex file into the chip with my Phyton programmer.
With this ESP module I assume I compile to chip and connect the PC USB port with the ESP UART port, right?

No! I need a UART to USB bridge like so:
http://www.ftdichip.com/Support/Documen ... LC234X.pdf

Jan

[mnfisher]

Depends on the hardware - but generally yes... Can also use a FTDI board if needed (the board doesn't have a USB port)

Martin

[jandidden]

Ordered a couple of UART to USB bridges with their drivers from Silicon Labs and FTDI.
Very cheap, that stuff. They must sell them in the 100's of thousands.

Jan