• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 47 subscribers
  • Views 574 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AFE7071EVM: the evaluation board's GUI does not function correctly

amir ayalon
Prodigy 80 points

Part Number: AFE7071EVM
Other Parts Discussed in Thread: AFE7071

hello.

we bought the AFE7071 evaluation board.

after downloading the GUI we connected the power and USB connectors to the board and attampted to use the GUI.

the GUI is heavily lagging and non-responsive, read attampts  mostly fail (only some registers appear if at all) and sending settings has no effect.

occasionally the GUI reports usb failure.

is there some diffrent driver not included with the GUI installation that is needed for the GUI to function correctly?

we are supplying a 60Mhz clock in J4 and for an initial basic test tried to use the GUI to enable the Y4 output which should result in the clock being output in J5.

  • 0
    TI__Intellectual 775 points

    Hi Amir,

    I am looking into this and will get back to you soon.

    Regards,

    Abdallah

  • 0 in reply to Abdallah Obidat
    Prodigy 80 points
    found the problem, or at least A problem :)

    i had a thought and disconnected everything from all the computer's USB ports except for the port connected to the evaluation board.

    the GUI now no longer lags, reads are successful and i can change settings.

    a bit of reconnecting the ports one by one and the issue appears when a USB blaster is connected to any USB port

    my current theory is that the GUI doesnt just test USB ports to find the evaluation board and then uses the relevant port but instead sends and listens through all possible ports with anything that is not a mouse or keyboard being considered (can't verify that anything other
    than keyboard/mouse would kill the GUI since i didnt test with other devices but a usb blaster at least definatly would)
  • 0 in reply to amir ayalon
    TI__Intellectual 775 points

    The USB Blaster utilizes an FTDI driver, as does the EVM. It seems plausible that the GUI would have trouble differentiating between the two. Newer GUIs employ USB enumeration as to avoid this specific issue. The simplest solution would be to leave the USB Blaster unconnected while using the GUI.