-
Notifications
You must be signed in to change notification settings - Fork 730
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
No USB signals for the hello_usbdev #4167
Comments
Hi @berkguldiker , Best regards, have a good weekend, |
Hi @vogelpi, |
You will need to provide the VBUS sense (resistive divider needed because the FPGA isn't 5V tolerant) before the USB is started (or change the code to override that check; it isn't strictly needed but Linux has an ultimate reset of removing VBUS when it believes a port is in a very messed up state). You will also need the 1.5k from the pullup output to D+ or the host will not detect a device. (The USB device won't start producing any traffic until the host starts sending the USB frame sequence and addresses it.) |
Hi, I got the PMOD card. Connected it to the port JB of my board and my PC (tried both J1 and J2). Then run the program
There also is no voltage on the sense pin. What might be causing this? Thanks a lot in advance. |
that's strange..did you build an fpga from the head of tree?
…On Fri, Feb 19, 2021 at 6:33 AM berkguldiker ***@***.***> wrote:
Hi, I got the PMOD card. Connected it to the port JB of my board and my PC
(tried both J1 and J2). Then run the program hello_usbdev. However, I got
the following message on UART:
I00038 boot_rom.c:61] Boot ROM initialisation has completed, jump into flash!
I00000 hello_usbdev.c:145] Hello, USB!
I00001 hello_usbdev.c:146] Built at: Nov 19 2020, 12:15:05
I00002 demos.c:18] Watch the LEDs!
I00003 hello_usbdev.c:157] PHY settings: pinflip=0 differential=0
I00004 handler.c:25] Load/Store fault, mtval shows the fault address
I00005 handler.c:26] MTVAL value is 0x4015006c
There also is no voltage on the sense pin. What might be causing this?
Thanks a lot in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4167 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH2RSSFVM3CBFY2YGYJ2T3S7ZZCRANCNFSM4TTEKSNA>
.
|
JB is correct. The sense voltage is just VBUS divided down, so should follow what the host computer is doing. The error address is the phy config register and that is indeed the first one written in the init sequence. Is it possible you have an old build of the FPGA? That register was added last summer. I see the software build date is Nov which would be after the register was added but we don't currently show the FPGA build date (it just got added by #5279 but I don't think is sw accessible) Note that by this point the pullup will not have been asserted (last thing done in init) so the host isn't going to see a device. |
I rebuilt the FPGA with a newer bitstream. It should be from the same time with ROM code. For which I get:
After that I didn't get the error message
The LEDs worked and
Why might the program bu cut at this point? |
That is looking good, all the initial USB handshake and discovery must have worked. If you connect with a terminal program (microcom, minicom, screen etc) on the Linux side (microcom -p /dev/ttyUSB0 is what I use, but of course the device is what ever ttyUSBx the dmsg shows) then you should be able to type characters on one side and see them on the other. Typing / on the FPGA console will print the interrupt and status registers so you can see more about what usbdev is doing. |
Thanks a lot. It is working. |
Hi @berkguldiker , how did you get the PMOD card? |
hi @jackieke724, |
Thank you @berkguldiker for the link. I saw it in the spec mentioned above, but I am not sure if it means we have to make the PCB, buy the parts, and then solder them ourselves? |
Hello, I tried the hello_usbdev program on my FPGA. I was expecting signals on the pins Jb1 and Jb2 (V9 and V8) because according to the xdc-file, the USB signals are connected to those pins. However, I didn't get any signals. Was I analyzing on the wrong pins or is there another issue?
The text was updated successfully, but these errors were encountered: