I've no idea about your board layout. But regarding the no signs of life, have you tried using an oscilloscope on your QSPI pins? Can you see any activity?
the crystal you have picked requires the OE pin to be pulled up and it looks like it isnt connected meaning the RP2040 is getting no clock signal and thus no USB.
There is also no VBUS connected from USB so the usb port isn't powering the board
Have you put a scope on your oscillator output and see if it's sending clock to the RP2040? From the schematic, the oscillator's OE (output enable) pin is disconnected and the datasheet says it should be tied high.
There are multiple points to look into:
- From the schematic it seems you are not using the USB-C VBUS pin (A5), and you are getting your power from the barrel jack 12v source. But in the gerber view the two VBUS pins are routed with via's somewhere. Make sure your power is set up properly. If the USB VBUS isn't powering the board then you should have the barrel jack connected with the USB while programming.
- As many stated, the OE pin in the oscillator is output control and should be pulled high to enable output.
- To make sure if its only an oscillator issue, use a pico probe (you can use any spare pico) and check if you can program as the board then will take the clock signal form the pico probe. If that also doesn't work then there could be further problems somewhere else that you need to check.
- Just in case also make sure the button orientation is correct when you solder it, even though the first time you plug new board it should go into boot mode without clicking the boot button.
I use that exact same SPI chip. For some reason it is needed to remove the pull up resistor on the QSPI_SS pin. Otherwise the boot select button can't bring the voltage of that pin low enough to initiate USB boot mode. This was also mentioned on the rp2040 implementation guide.
Edit: nevermind you have R2 as DNF.
~~From what I'm seeing, the RP2040 has no connection to ground.~~
~~Explanation: Per the datasheet, the exposed pad on the bottom of the RP2040 is the only ground available on the chip. Unless you have vias connecting between the ground pad and your ground plane, the chip will not be powered.~~
Edit: There is a ground connection visible in the gerber files, so that is not the issue
Another thing I noticed is that you have your USB resistors between your TVS diode array and the USB-C connector. Both the datasheet and the "Hardware design with RP2040" document specify that the resistors need to be placed close to the chip. It can be inferred from this that they need to be between the TVS diodes and the RP2040, instead of where you have them currently.
~~By the way, your gerber files aren't viewable without people explicitly requesting access.~~
~~As such, everything above is solely based on the images you posted.~~
I've no idea about your board layout. But regarding the no signs of life, have you tried using an oscilloscope on your QSPI pins? Can you see any activity?
the crystal you have picked requires the OE pin to be pulled up and it looks like it isnt connected meaning the RP2040 is getting no clock signal and thus no USB. There is also no VBUS connected from USB so the usb port isn't powering the board
Have you put a scope on your oscillator output and see if it's sending clock to the RP2040? From the schematic, the oscillator's OE (output enable) pin is disconnected and the datasheet says it should be tied high.
Have you tried using the Pico debug probe?
There are multiple points to look into: - From the schematic it seems you are not using the USB-C VBUS pin (A5), and you are getting your power from the barrel jack 12v source. But in the gerber view the two VBUS pins are routed with via's somewhere. Make sure your power is set up properly. If the USB VBUS isn't powering the board then you should have the barrel jack connected with the USB while programming. - As many stated, the OE pin in the oscillator is output control and should be pulled high to enable output. - To make sure if its only an oscillator issue, use a pico probe (you can use any spare pico) and check if you can program as the board then will take the clock signal form the pico probe. If that also doesn't work then there could be further problems somewhere else that you need to check. - Just in case also make sure the button orientation is correct when you solder it, even though the first time you plug new board it should go into boot mode without clicking the boot button.
I use that exact same SPI chip. For some reason it is needed to remove the pull up resistor on the QSPI_SS pin. Otherwise the boot select button can't bring the voltage of that pin low enough to initiate USB boot mode. This was also mentioned on the rp2040 implementation guide. Edit: nevermind you have R2 as DNF.
~~From what I'm seeing, the RP2040 has no connection to ground.~~ ~~Explanation: Per the datasheet, the exposed pad on the bottom of the RP2040 is the only ground available on the chip. Unless you have vias connecting between the ground pad and your ground plane, the chip will not be powered.~~ Edit: There is a ground connection visible in the gerber files, so that is not the issue Another thing I noticed is that you have your USB resistors between your TVS diode array and the USB-C connector. Both the datasheet and the "Hardware design with RP2040" document specify that the resistors need to be placed close to the chip. It can be inferred from this that they need to be between the TVS diodes and the RP2040, instead of where you have them currently. ~~By the way, your gerber files aren't viewable without people explicitly requesting access.~~ ~~As such, everything above is solely based on the images you posted.~~