Request PIDs f540 and f542 for One ROM

[piersfinlayson]

Project page: https://onerom.org

Pre-requisites:

Publicly available source code repository:

• https://github.com/piersfinlayson/one-rom

Containing modifiable PCB design files:

• kicad files (and other fab files) for all variants
• example: https://github.com/piersfinlayson/one-rom/tree/main/hardware/pcb/verified/fire-24-e/kicad

Source code for a device with a USB interface:

• Main firmware: https://github.com/piersfinlayson/one-rom/tree/main/sdrr
• USB stack: https://github.com/piersfinlayson/one-rom/tree/main/plugins/system/usb

Licensed under a recognized open source or open source hardware license:

• MIT & CC BY-SA 4.0
• License file: https://github.com/piersfinlayson/one-rom/blob/main/LICENSE.md

Edited: 30 Mar 26, PCB files in repo have moved - updated link.

[tannewt]

C firmware source and kicad hardware sources look good. One question first.

[tannewt]

Why do you need a bootloader PID? The RP2350 has a built in bootloader.

[piersfinlayson]

Thanks for reviewing.

What I would like to do is write a custom bootloader VID/PID into the RP2350's OTP memory on first firmware programming. This will help both the user and the One ROM tooling to definitively identify the device as a One ROM when in RP2350 bootloader mode - which is most commonly used for "unbricking" the device.

[cnlohr]

From what I understand the maintainers don't want to have pid's doubled up for this sort of thing.

I would let @tannewt make the final call on this one. I don't know if I would accept this one.

The reason I feel a little weird is, I can sympathize with @piersfinlayson on this one, as there are lots of situations I would prefer to be able to do this. The compromise I could envision is you would use one bootloader VID/PID for all products you make? (Would really like more feedback on this one)

❓

[piersfinlayson]

Thanks for the comment @cnlohr

I went with this approach as there appeared to be other RP2040/2350-based projects that have gone with the dual PID approach, one for the bootloader, one for the application.

However, I'm happy to modify the PR for a single (non-bootloader) VID/PID if that's the requirement.

I would be also happy with a more generic VID/PID for all of my open source products' bootloaders using an RP2040/2350. Again - just let me know if that's what you'd like me to do and I'll modify the PR.