Pygamer usb #104
Pygamer usb #104
Conversation
jacobrosenthal
force-pushed
the
pygamer
branch
from
bb54e23
to
637bd40
Compare
|
Yeah uart_debug is 🔥 🗑️ - couldn't work out a better way to do it :( feel free to revise or maybe even rip it out. Maybe it makes more sense being in the uart code? That way there can be an invariant for each kind of uart rather than the one on the itsybitsy_m4 pins. |
Neopixel or apa102 LED? |
|
I didn't think neopixels were compatible with SPI? I thought they had to be bitbanged? |
|
Neopixels. And yes theyre being bitbanged using the same library as the itsy bitsy |
|
Rather the feather m4 and metro m4 |
|
RE uart_debug, the main issue is I think my stuff is on sercom5 instead of 3, so hardcoded pins need changing. I suppose we can store via traits somehow. What about static dyn like the singleton pattern docs https://docs.rust-embedded.org/embedonomicon/singleton.html |
jacobrosenthal
force-pushed
the
pygamer
branch
from
4511002
to
6227cea
Compare
jacobrosenthal
force-pushed
the
pygamer
branch
from
6227cea
to
643c63d
Compare
jacobrosenthal
force-pushed
the
pygamer
branch
from
643c63d
to
b9540a9
Compare
|
Ive pulled all the smart-leds neopixel code out of here and its already been merged, so now this is just the usb work. I pulled the uart_debug feature because I dont know how to fix it yet either.. Technically this could merge any time. It works as well as the other implementation despite the existing bug #105 |
* blinky * usb_serial for pygamer, not being flushed until serial close * usb_poll for pygamer, not being flushed until serial close
Neopixel example wasn't working for me at all.. I reved the underlying deps and now it works for 1 led but not more. I'll pr that work over there as well.
Then I brought over usb from metro_m4. (likewise its stuck on 1 lets as well)
The only problem there is uart_debug.rs is pretty coupled and needs a better solution than this.