Feather RP2350: MAX3421E instead of PIO USB host, or a second build?

未关闭
  • 哪里不对？
#11,697 4 条评论 0 个 reaction 已指派 2 人 在 GitHub 查看

维护者通常 1 天内回复

@mikeysklar 已经在做这个了。

开始于 2026年10月31日。

评估

这个 Issue 还没有评估数据。

描述

rp2 usb

Since #11695, the MAX3421E USB Host FeatherWing (5858) works on a Feather RP2350 that shares board.SPI() with a TFT and an SD card. I've been using it as the USB host in a standalone flasher for a USB-MIDI synth. Stock builds for the Feather RP2350 have CIRCUITPY_USB_HOST = 1 and CIRCUITPY_MAX3421E = 0, so the wing needs a custom build.

The two can't both be on: with both set, the link fails on duplicate hcd_* symbols (hcd_pio_usb.c and hcd_max3421.c). So enabling the wing means turning off usb_host.Port for this board, as adafruit_feather_rp2040_dvi does.

Would you take either of these as a PR?

  1. Switch the Feather RP2350 to CIRCUITPY_MAX3421E = 1, CIRCUITPY_USB_HOST = 0.
  2. Leave it as is. Wing users would keep a custom build, unless there's a better route (a separate board variant, or TinyUSB supporting two HCDs).

Separately: CFG_TUH_ENUMERATION_BUFSIZE defaults to 288 bytes, and some USB audio+MIDI devices have larger configuration descriptors (the M-VAVE FM-1's is 293 bytes, so it fails to enumerate). Fruit Jam raises it to 4096 on its board. Would raising the default, say to 512, be acceptable as a PR, or should it stay per board?

🤖 Generated with Claude Code

主要语言
C
星标
4.6k
派生
1.4k
平均合并
1 天 13 小时
30 天内合并 PR
171

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

adafruit/circuitpython 的其他 Issue

查看 adafruit/circuitpython 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。