-
Notifications
You must be signed in to change notification settings - Fork 277
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
Fomu: usb.out_ev_pending.status: 'CSR' object has no attribute 'status' #135
Comments
Hi @tcal-x, the integration of ValentyUSB is a bit hacky for now. Changes have been done to ValentyUSB to fix this and we are using a different repository. You can just do |
Thank you @enjoy-digital , Is the goal of removing the valentyusb directory to disable UART, or to refresh the clone of valentyusb? In any case, I see the same issue -- after removing valentyusb/ and rerunning, the ./fomu.py script performs the clone again, and the same error results. If time allows, I will try to debug the issue further.
|
@tcal-x: the goal was to do a clean clone of ValentyUSB, but I think the issue is that LiteX is not up to date on your setup so ValentyUSB is not building correctly. |
Thank you @enjoy-digital ; I had been trying to update my LiteX using When I did a completely new install of everything, starting with an empty directory, wgetting Well, the LiteX side of it worked. I encountered the following. I ran using tools from fomu-toolchain v1.5.6, from March; maybe I need newer versions of Yosys and nextpnr-ice40.
|
In case anyone finds this, my problem above is because I was not specifying the correct VexRiscv variant. From @enjoy-digital 's tweet in October, these are the known good recipes:
You should then see this from dmesg:
...and now you can connect via litex_term, picocom, etc. |
litex-boards: 36b7fb1
valentyusb: (hw_cdc_eptri) 371526e432a858b768ddc561cee0d7a0c8f40f42
Hello,
I encountered the following error. Apologies if I made a mistake with setup:
The text was updated successfully, but these errors were encountered: