You have the idea
A product note, an AI draft, or a finished Gerber. If there is no schematic yet, that is a design job — not a reason to stop.
Huiyang Embedded · AI hardware partner
Bring an idea, a spec, or files. Leo owns a complete ESP32 PCB project — schematic, layout, BOM, Gerber — and writes the ESP-IDF firmware that has to run on that board. Then it can be built, powers on, and can be built again.
AI can sketch a circuit. A factory can fab it. We sit in both gaps: a complete schematic and PCB project, firmware written here, then DFM, bring-up, and a path the next batch can repeat.
A product note, an AI draft, or a finished Gerber. If there is no schematic yet, that is a design job — not a reason to stop.
A complete PCB project: schematic, footprint, stack-up, antenna keep-out, layout a fab can make. And ESP-IDF firmware written to run on that board — or a punch list if you already have files.
First power-on, firmware that talks, and a pass/fail path you can run again.
Taken from boards and firmware already built here. Say which of these you need.
Say design, DFM, bring-up, or repeatable when you write.
A complete ESP32 / S2 / S3 / C3 / C6 PCB project from the product note: schematic, layout, BOM and Gerber. Day-to-day work here, not a one-off sketch.
Your schematic or layout, checked against parts you can actually buy, footprints, power, and assembly.
Board back from fab. Power rails, flash path, first UART, first I2C or SPI. Firmware we wrote, or yours, talking on the bench — the faults that usually hide until then.
The same steps the next batch can follow, so bring-up is not a one-off heroics session.
WhatsApp what the board must do. A schematic, Gerber and BOM help. If you have none yet, that is a design job.
Against the ESP32 whitelist. Infinite custom is how this work dies. A no is a useful answer.
A schematic and Gerber, a punch list, a running first article, or a repeatable path — not an open ticket.
Look for a module that fits, then start building the idea.
Engineer questions written as pages. An AI search can point at one URL instead of a whole catalog.
Leo designs schematic and layout, and reviews the same sequence a fab and SMT line will run. We do not run a factory. This is what the board has to live through.
Talk got cheap. A body that any mind can wear — without the firmware guessing — is still scarce. This lab is building that operating system: discover every organ, install a brain, keep the kernel as a post office.
Speech already reaches the brain slot. The round trip is too slow, and the uplink is too fat. 神赐 is a grant the main brain issues so this body can wash a stream or emit menu steps locally — without rewriting Body OS.
中文
蕙杨嵌入式 · AI 硬件伙伴
可以只有想法,也可以已有文件。Leo 做完整的 ESP32 PCB 项目——原理图、布局、BOM、Gerber——并写这块板上要跑的 ESP-IDF 固件。然后这块板能造、能亮、下一批还能同样过。
AI 能画出草稿。工厂能打板。我们做两头:完整的原理图和 PCB 项目、在这里写的固件,以及可制造审查、点亮、下一批能重复的路径。
产品说明、AI 草稿,或已经画完的 Gerber。还没有原理图,就是设计单,不是停下来的理由。
完整 PCB 项目:原理图、封装、叠层、天线净空,以及工厂真能做的布局。板上要跑的 ESP-IDF 固件也在这里写。已有文件就出问题清单。
第一次上电、固件能通信,以及下次还能同样判定合格。
从已经做过的板和固件里列出来。写信时直接说要哪几条。
写信时直接说:设计、审查、点亮,还是可复现。
从产品说明做完整的 ESP32 / S2 / S3 / C3 / C6 PCB 项目:原理图、布局、BOM 和 Gerber。这是日常工作,不是偶尔画一张。
原理图或 PCB,对照能买到的料、封装、电源和装配,改到可以下单。
板从工厂回来。电源轨、烧录、第一次串口、第一次 I2C 或 SPI。我们写的固件,或你的固件,在台架上通上——那些不上台架看不见的故障。
下一批还能按同样步骤走,点亮不再靠某一次运气。
用 WhatsApp 说这块板必须干什么。有原理图、Gerber、BOM 更好。还没有图,就是设计单。
只对照 ESP32 白名单。无限定制会把这事做死。拒绝也是有用的答复。
原理图和 Gerber、问题清单、点亮的样件,或可复现路径——不是一张敞开口的工单。