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 ...
Today i found one of my old projects, actually experimenting stuffs. This is thing is a stepper motor controller. I think many people out there knows whats Stepper Motors are and how it works. Usually this type of motors are in printers and photocopy machines..etc. Actually the circuit i made was to interface a stepper motor to an micro controller IC so i can write a code to turn the motor to different degree and so.. usually this type of applications are used in Robots.
Before i wrote the operating code from assembly language and now i have changed it to C language and its simple and easily understandable for anyone. Hopefully some one will built a robot soon. ;)
Before i wrote the operating code from assembly language and now i have changed it to C language and its simple and easily understandable for anyone. Hopefully some one will built a robot soon. ;)
Comments