This is a custom ESP32S3 prototyping board i built to troubleshoot the issues. It Started With a Simple Problem I was testing the EvilCrow Cable Wind — a USB HID device built around the ESP32-S3 that executes keystroke injection payloads over WiFi. Everything seemed fine: the keyboard HID was typing correctly, the web interface loaded, basic commands like RunWin worked. But ServerConnect and ShellWin did absolutely nothing. No error. No feedback. Just silence. Digging Into the Code The first thing I found was this pattern — repeated across four commands: ORIGINAL — DANGEROUS if (!clientServer.connect(serverIP, serverPort)) { while(1); // hangs forever if TCP fails } ⚠ Critical Bug If TCP connection failed for any reason, the device entered an infinite loop with no timeout, no error output, and no recovery path. Ever. But there was more. The bugs were stacking: critical TCP failures were environmental: listener ...
These days i am trying some experiments with infrared lights. Its not visible to naked eyes and normally uses a camera to see the light. If you want to try that, get an infrared LED and power it up and use a web cam or any type of camera to see it. This is interesting thing.
I use infrared to make a remote control. RX and TX side will have a micro controller. TX will send date to RX and RX will do the rest. Now the TX part is totally completed by experimenting, still RX side experiments are going on. cause i need to make the code looks nice and short. Once this is finished you guys can have a try... ;)
I use infrared to make a remote control. RX and TX side will have a micro controller. TX will send date to RX and RX will do the rest. Now the TX part is totally completed by experimenting, still RX side experiments are going on. cause i need to make the code looks nice and short. Once this is finished you guys can have a try... ;)
Comments