Add jc1060p470ciwy support. ESP32P4 + C6 for wifi.

[josemalm32]

First of all, thank you very much for the project. I love it in general, especially being able to install applications. I'm starting to play around with embedded boards and I'm surprised by what can be done.

Is your feature request related to a problem? Please describe.
It is not a solution to add a new implementation. Would it be possible to implement the jc1060p470ciwy board that uses the new ESP32P4? I actually created a fork and implemented it. It works. I've touched more than I should have, or so I think (base files apart from the device and driver folder). I've also received some help from Copilot, which... may have also touched more than it should have. But I'd like the author to verify it... in case I break more than I should.

Describe the solution you'd like
Use my fork to implement it: https://github.com/josemalm32/Tactility
Working : Display (Flickering when save in internal memory, Flips don't work), SDCard, Wifi and Battery Voltage

Describe alternatives you've considered
I think the fork I created can be improved. I believe that the changes I have made to EspLcdDisplayV2 and CpuAffinity can be improved.

Additional context
I can provide more examples of ESP-IDF if necessary.

THANKS 😃

[KenVanHoeylandt]

Great job! Feel free to open a pull request so we can do a proper code review. I've already looked at most of the code (although not in the greatest of detail) and the structure of it looks fine.
This can become the first officially supported P4 device!

I'm happy to see that the EspLcdDisplayV2 driver is gaining MIPI/DSI support, as it will be useful for some other P4 devices that I intend to support soon (M5Stack Tab 5 and Waveshare ESP32-P4-WIFI6-Touch-LCD-4B). I'm also excited that you got WiFi working!

Here's already some preliminary feedback on the diff:

• (nitpick) The I2C Configuration in Configuration.cpp is generally named to its location or label and not the device(s) attached. In this case the name "Internal" would be more consistent with other implementations.
• SdCard.cpp's locking doesn't seem correct: it should probably not call tt::lvgl::getSyncLock() as it's not on the same bus ... is it? On other devices, the display and SD card often share the SPI bus. That's why the SPI bus in Configuration.cpp is assigned the LVGL lock. In your scenario, you can probably just store a lock instance in the SdCardDeviceImpl class and then return that instance in ::getLock()
• device.properties: brand name should be Guition instead of Elecrow. (with similar devices the name is "CYD", but I'll change them to Guition later)
• We'll have to find a different solution for CONFIG_TT_WIFI_ENABLED: this is now set via the .properties file but the naming of it ("CONFIG_") implies it's a KConfig setting. Can we remove that setting and only use CONFIG_ESP_WIFI_ENABLED and CONFIG_ESP_WIFI_REMOTE_ENABLED instead?
• Some of the code comments are in Spanish and should become English

// Default to core 0 when no explicit WiFi pinning is configured

This is a good idea for the WiFi-related operations.

Thanks a lot!

[KenVanHoeylandt]

FYI: I'm already building the TactilitySDK for P4 in the pipeline, but I haven't published it yet to the CDN. That means it's not available yet when building apps with tactility.py. That said, you can still use the local SDK argument in tactility.py to override it with a locally built/downloaded SDK (--local-sdk).

[KenVanHoeylandt]

I was looking to buy one and I found 2 variants:

• JC1060P470C-I-W-Y with a case, camera and ethernet port
• JC1060P470C-I-W without the case/camera/ethernet

The other components look the same, but I couldn't find any pinouts in the zip files from the seller, so I wonder if they're the same besides the mentioned hardware features above.

Which one do you have? edit: CIWY

[Shadowtrance]

How did you NOT find any pinouts in either zip files? They both have full schematics in them. (as they usually do) 😄
But yeah for simple "read a text source file for pins" i basically couldn't find many pins pointed out at all. Think only backlight and reset and touch.

The first link is the new one. (there's also a 4.3 inch version with camera, no ethernet)
The second link is the old one, one of the very first P4 "cyd" style boards to appear. It also has a full schematic, just not as nice as the other one and not a pdf.

The new one has a very nicely laid out pdf schematic. Look at it! It's purdy! 🤣 (yes i like looking at nice schematics)

So yeah going by the title it's probably the new one.

[KenVanHoeylandt]

I've ordered the board so I can finish up the implementation. I'm keen on having a P4 board soon, so we can implement other P4 boards more easily.