my ti gameboy, I have no idea if it's

can you get an mspm0 with builtin usb the buttons are probably going to be hard to press but that might be ok/we can figure it out when they arrive do you have a screen selected? if not, maybe try to select a screen that could work, you might want a flex connector, check out buydisplay.com and maybe coordinate w/ Abse the boot/reset buttons are usually hidden or close the the mcu to avoid extra presses can't read the schematic

the mspm0 with builtin usb is no available on jlcpcb, would the current one work?

ok yea that's fine

i just don't know if it's programmable over usb yet

https://tscircuit.com/ShiboSoftwareDev/mspm0g3507-gameboy-handheld build fails but passes when you manually run it <@398467566588264449> please check

I think build on the site has 10 min limit

<@809856037376491570>

your build took 662 second (I have the same issue on the gameboy)

hmmm why ur guys boards take so long to route haha

The autorouter is timing out the worker, which has a limit of 10min by default. You can increase that from the tscircuit config

<@757706909351411845> <@398467566588264449> it's built now please review: https://tscircuit.com/ShiboSoftwareDev/mspm0g3507-gameboy-handheld#files

Where do you plug battery?

Also, the schematics are a bit cluttered

added a battery connection, and improved the schematic

<@398467566588264449>

That produces a real power-on reset and is the safest entry method. If you want “hold BOOT, tap RESET” to be guaranteed, it must first be tested on a physical MSPM0G3507 or replaced with circuitry that controls the 3.3 V rail/reset sequence appropriately. Other electrical observations The charger connections look valid: VBUS feeds IN, battery positive reaches both BAT pins, NTC reaches TS, /CE is grounded, SYSOFF is grounded, and the input/charge-current programming resistors are present. USB-only operation should work with the power switch ON because the BQ24075 system output supplies the 3.3 V regulator. Connecting CH340 VCC and V3 to 3.3 V is correct. The USB ESD device is connected with D+/D− passing through the corresponding channel pairs. MCU VDD, VSS and VCORE decoupling are connected correctly. The PCB viewer reports zero routing errors. Remaining concerns These are risks, but not definite connection blockers: The USB pair is not declared as an explicitly impedance-controlled, length-matched differential pair in the TSX. The multiple star-connected ground domains could disturb the USB return path if D+/D− cross a ground split. The CH340 is powered only when the system switch is ON. This should be clearly documented on the enclosure. Ensure the BOOT button and power switch remain accessible after assembly. The release build status does not prove that the custom fabrication and Gerber audit scripts passed. Final verdict: I do not see a wrong TSX connection that would prevent USB-UART programming. The hardware should program through USB-C, but use BOOT held during power-on, not rely exclusively on BOOT + RESET. Keep the SWD pads because they provide recovery if the BSL configuration is accidentally disabled.

this is codex/My review looks good just make sure no shorts correct via size and double check the usb and the buttons are not shorted

<@757706909351411845> <@809856037376491570>

hi taking a look

label all test points

use our new 5 pin programming standard here: https://tscircuit.com/tscircuit/standard-jst-programmer#3d

you can add a 5 pin. The reason i bring this up is it makes it a lot easier to program and probe

there's also no power switch

i'm confused about the audio, it seems like it's pretty far from the audio driver

"use the programming standard" basically just add the 5 pin JST from the package for programming. This allows us to bypass the usb uart chip which is sometimes needed if the firmware becomes botched etc.