It looks like an issue in TCPIP_ENC28J60__MakeArpRequest

The arguments are declared as "MX_UINT8 **PFCL_SERVERIP"

but then used as "FCL_SERVERIP[FCL_IDX];"

Does the component need recompiling for v10? or has the way arrays get passed/named changed slightly?

Martin

Just testing this with some SPI code - I have the v5 toolchain installed and compiling from a command line 'works' (or at least attempts to compile) Compiling from FC - I get 'Can't find export.bat' In command line - I do 'idf.py set-target esp32-c3' then 'idf.py build' Then idf.py build - and I get...

Yes - I have export.bat in c:\esp-idf Your setup is at c:\users\45505\.espressif - I'm not sure if there has been discussion of not liking '.' in the path (or maybe it was ' ' (space) ) Full directory list: test.txt Which version did you have installed - have you 'upgraded' to 5? (Which might not be...

Hi Jorgen,

Looks like your esp installation has gone AWOL? Anything else changed - check the esp directory and run install.bat and check that FC still points to the right directory...

Martin

The modified esp_cal_spi.c seems to work AOK. All looks good using hspi and vspi!

Thanks Ben.

Hi Jorgen, - That compiles fine for me... Something awry - you are getting idf.py build Usage: idf.py [OPTIONS] COMMAND1 [ARGS]... [COMMAND2 [ARGS]...]... Try 'idf.py --help' for help. Error: No such option: --no-hints Did you mean --no-warnings? So giving up straight away with a compiler option err...

Thanks Ben,

I'll have a play over the weekend...

Martin

Hi Jan, The FT6206 is a capacitive touch controller. The source for the FT6X06 doesn't seem to occur in the Wiki - but it should work correctly? I've posted a bit about the XPT2046 (more to come :-) ) (https://www.flowcode.co.uk/forums/viewtopic.php?f=10&t=1854)- which isn't very accurate (resis...

This is a result of the slightly strange naming convention in FC. If you use channel 2 UART (note you seem to have it defined as using channel 1) - you need to use RxInt1 (similarly for channel 1 - use RxInt0) Because you haven't used the relevant channel - the interrupt can't be defined. I think it...

Well - finally got the range status to display some meaningful values (okay 91 was meaningful - reading okay!) So - embarrassingly - the sensor was picking up on the wires I'd used - the field of view and path of the jumpers just gave a enough of reflection... It first 'dawned' on me when I noticed ...