Yeah — this is a solid start, and I can read the main intent from the screenshot.
What I see in your schematic image:
ESP32-S3-MINI-1 module in the center
USB-C connector
3.3 V regulator
BOOT / RESET buttons
power LED
buzzer
a servo output section
a fingerprint connector
and a sensor block at bottom-right that looks like an IMU/sensor interface
My quick opinion
Good:
You’ve already separated the design into functional blocks, which makes it much easier to debug and build from a screenshot review perspective
The core support pieces for the ESP32 are there: USB, regulator, boot/reset, LED
The schematic is readable enough to reason about at a high level
Main concerns from the screenshot
I do not think that bottom-right sensor is the BNO055
The label in the image looks like something closer to LSM6DSOXTR, not BNO055.
So if your goal is specifically ESP32 + BNO055, this screenshot may be using a different IMU.
I can’t verify exact pin correctness from the screenshot alone
For image reviews, the right approach is to identify topology and obvious issues, but not pretend unreadable pin text is confirmed
So I can comment on structure, but not guarantee every net is right from this image.
USB-C implementation needs a closer check
I can see 5.1 kΩ CC resistors, which is a good sign for a USB device/power sink style connection.
But the USB D+ / D- routing to the ESP32-S3 needs to be checked carefully, since the S3 supports native USB and those exact nets matter.
ESP32 enable / boot network should be verified
You have buttons and a pull-up shown, which is directionally right.
But the exact EN, GPIO0/BOOT, pull resistor values, and whether reset/boot are wired in the recommended way should be checked against the ESP32-S3-MINI-1 documentation, not guessed.
Sensor power / interface mode needs verification
If this is meant to be BNO055, then the required power pins, I²C/UART mode pins, address/config pins, reset pins, and decoupling need to match the BNO055 datasheet.
From the screenshot alone, I can’t confirm that.
Short answer
As a rough architecture: yes, this looks reasonable.
As a finished “ESP32-S3 + BNO055” schematic:not yet verified, and possibly not actually using a BNO055.
What I’d fix/check first
Confirm the IMU part number
Verify ESP32-S3 USB pins
Verify EN / BOOT wiring
Verify regulator input/output caps
Verify the sensor is powered from 3.3 V
If it is BNO055, verify:
SDA/SCL
pull-ups
reset/boot/config pins
decoupling caps
If you want, I can do the next useful step in a very practical way:
Option A: you send a clearer screenshot just of the ESP32 + USB + IMU area
Option B: I give you a known-good ESP32-S3-MINI-1 ↔ BNO055 connection checklist
Option C: I mark up this screenshot verbally and tell you exactly what looks right vs suspicious block by block
If you want the fastest path, pick C and I’ll go line-by-line through this image.
Wirelessly connects nets on schematic. Used to organize schematics and separate functional blocks. To wirelessly connect net portals, give them same designator. #portal
General Purpose Thick Film Standard Power
and High-Power Chip Resistor
47 kOhms ±5% 0.125W, 1/8W Chip Resistor 0805 (2012 Metric) Automotive AEC-Q200 Thick Film
Features:
- RMCF – standard power ratings
- RMCP – high power ratings
- Nickel barrier terminations standard
- Power derating from 100% at 70ºC to zero at +155ºC
- RoHS compliant, REACH compliant, and halogen free
- AEC-Q200 compliant