-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LiteX-boards support #16
Comments
Good point. Will add to the list of todo's :) |
https://github.com/tinyvision-ai-inc/litex-boards |
Hi @Xenador77 , I have a v3.1 board, with pmod connector, with no modifications. Should I expect these board files to work for me? I tried adding LedChaser (yes even though there's just the single RGB LED), since that is usually the first sign of life of LiteX running on the board. But I don't see any activity. Is there a reset signal I need to toggle or something like that? I know the build is wiring to the LED correctly, since my first attempt I used polarity=0 in the LED chaser, and the LED was just bright white. Then I used polarity=1, and the LED is off. |
The files should work for both 3.0 and 3.1 (I've only tested with the 3.1). However, there is a small modification needed (oops): I initially included the LedChaser in the target file, but removed it due to the brightness (although my RGB LED was pinkish-red) |
@Xenador77 , yeah, I agree the LED is so bright. And you're right it's not pure white. Quickfeather has the same blinding brightness issue. The jumper should be easy, since I'm already using the pin header on that side (for the uart). I just need to solder those pins. I'll let you know how it goes. |
@Xenador77 , no success yet at my end. What was the exact LiteX recipe you used? I had tried:
|
@Xenador77 , I needed to make this fix; now I see (the RGB version of) LedChaser working :) _io = [
# CLK / RST
- ("clk12", 0, Pins("35"), IOStandard("LVCMOS33")),
+ ("clk12", 0, Pins("20"), IOStandard("LVCMOS33")),
|
@Xenador77 I'm not having any luck with the UART/TTY though; did it work for you? |
I'm working on figuring out what is going on with that right now |
Correct, I'm using the Digilent Pmod USBUART, but not in the pmod header, instead directly connected using jumper wires to pins 2, 3, and GND of the Upduino board. I had tried a different usb/uart board beforehand also with no luck, but I switched to the Digilent board because it has tx/rx LEDs. I'm not getting any data coming from the Upduino, but that could be due to anything preventing the CPU from working correctly (SPIflash etc). I guess we can look at the schematics for Fomu and/or Icebreaker, which can read from spiflash. |
No luck yet on my end, tried adding |
The Upduino schematic looks pretty much the same as Fomu's w.r.t. to the spiflash connection. https://github.com/im-tomu/fomu-hardware/blob/master/archive/pvt/releases/pvt1/tomu-fpga-pvt1.pdf |
It would be great to have support (both a platform file and a target file) in litex-boards for v3.1.
I did find these for v1: https://github.com/timvideos/litex-buildenv/blob/master/targets/upduino_v1/base.py (target file), https://github.com/timvideos/litex-buildenv/blob/master/platforms/upduino_v1.py (platform file).
Probably some of the pinout in the platform file would need updating, and it might need some massaging to move it to
litex-boards
.The text was updated successfully, but these errors were encountered: