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: listene...
This afternoon i was hard cording some ADC codes. Actual thing i want to do is micro controller's ADC will analyze the given voltage . Actually i am continuing my voltmeter project. I did analog part from LM358. actually an differential amplifier, it handles the high voltage and gives an out put range from 0 - 5 volt. After some calculations i finally solve the puzzle. Now my micro controlled voltmeter is able to display variable voltage from GLCD (Graphical LCD). Next step is to fine tune the analog circuit and add a new feature or function to display load current. Many experiments are hold for few days, thing is me too busy some times... ;)