compatible with JC4827W543??

[judasacustico-commits]

I bought an esp32s3 card with display model JC4827W543, great cost-benefit because it is much cheaper than a waveshare. I believe that the code of the model JC3248W is the closest to my board, but I am unable to modify and adapt the code to make it work. If someone can help me and others could enjoy the cost of this cheap board.

[Builty]

Hi. Could you post a link to the board you got please.
I did some searching, but the ones I found have 2 major issues:

• 4 MB flash is not enough. 8MB is usable but with limited skins. Most of the bigger boards have 16 MB
• the resolution of the display seems to be 480 x 272, which is different to all others and would need an entirely new UI design to be done

Some boards also can't do the USB host mode needed.
When you post the link, I can check these details more carefully.

[judasacustico-commits]

I bought it at this link:
https://a.aliexpress.com/_msjzyff

Here are pictures of the sign:

![20260415_160452.jpg] (https://github.com/user-attachments/assets/4be36034-7ff5-46af-bef6-cd23435da521)

![20260415_155655.jpg] (https://github.com/user-attachments/assets/aa53477b-6243-438b-873d-6b43e5658a65)

It uses an ESP32S3 Sparkle XH-S3E that has 8MB of PSRAM.

I think that changing the resolution and pinning would solve it.

[Builty]

8MB of PSRAM is good, but it only has 4 MB of flash memory.
The current release for the JC3248W needs 3.6MB for the application + 5.7MB for the skin images (total 9.3MB.)
The first 65k of flash is used by partition table, bootloader etc, leaving about 3.75MB for application.
If the skins were removed, it might have some chance of just squeezing in, but if I add anything new in the next release then it may not fit anymore.
8MB is really the smallest it can be (a special build with only a few skins.) Most use 16 MB of flash.

The display drivere is ILI6485 which is not well supported and not included in the Espressiv repository. It would need be to ported from some other sources.

The schematic doesnt show any details about the USB-C port. The picture shows a diode near it. It may not be suitable to provide power to the USB port (this can be fixed by using 9v power on the pedal though.)

Changing the resolution is not just changing 2 numbers. It would need every graphical object to be moved/changed in size to fit correctly (its a big job.)

I'm sorry but I don't think this board is suitable to use. Mainly the flash memory issue, its just so small.

[Builty]

The Guerrihila Box is my project that they stole. It will be a "Zero" board inside.
If you don't need the LCD at all, then yes 4 MB would be enough.

[judasacustico-commits]

Is it true? how did they steal? what a pity that. I even modified my guerrilla box and added internal battery, it works very well, if you want I can provide you with the whole process of modification. Regarding the display plate that I have then I will have to throw in the trash, how sad it does not work. Wouldn't it really work with a simplified interface?

[Builty]

Re Guerrihila Box:

As per the open source license terms if they create a commercial version they must state that it is based on this project and link the Github page, which they are not doing. Watch the videos, you can see the web interface is identical.
I commented on some Youtube videos and they just delete the comments.

I could contact Intragram/Youtube and get them shut down but I don't really want that hassle or to be a bad guy.

It might be possible to support a basic interface with no images on the screen. That could perhaps fit but would be a fully custom firmware.

[judasacustico-commits]

They should have given credit to the creator, that was a real vacillation.

I have already created a menu on my board, this is not difficult, to show the name of the presets, nuenro, bpm do delay, what is connected and what is not. But I am having difficulty finding what the communication data is between the plates. What I am doing is opening the IP through the browser and observing what happens in the exchange of data during operation. This is exhausting, if I had this list ready it would help me a lot.

[Builty]

All of the code is here on Github. If you are creating a UI on your board, you should not need to connect via Wifi. You can do the UI and write to the screen directly from the controller code, as the other platforms do.

If you want to just make a remote controller for an existing Tonex controller, then in this case WiFi would be OK. The interface uses the websockets protocol. Refer to wifi_config.c. You can see how the Json messages are created and recieved.
And also check web/script.js, for the Javascript side that talks to the controller.