Arduino uno not connect with quickeval software

Hi i use a arduino uno with FT232RL from ftdi chip for convert UART to USB as Linduino use, i upload to my arduino the sketchbook DC590B and i can take the message "hello" from my serial port wich that mean sketchbook have  successfully upoload and work , but the problem is that can not connect with QuickEval software, where is the problem?

thanks

Top Replies

Parents
  • 0
    •  Analog Employees 
    on Mar 1, 2021 9:39 PM

    Hi Yiannis,

    So QuikEval and the individual, part-specific example sketches are mutually exclusive. QuikEval requires that the "DC590 emulator" sketch be loaded:

    https://github.com/analogdevicesinc/Linduino/blob/master/LTSketchbook/Utilities/DC590B/DC590B.ino

    This sketch is a command interpreter and not really useful aside from using with QuikEval.

    The idea is, get the hardware up and running with QuikEval GUI, then move on to the part-specific sketch for further application development.

    What eval board are you connecting the Linduino to? Note that QuikEval will not do anything without an additional eval board connected, as it queries an identification EEPROM. But you do say that you see the "hello" message in the terminal, which is to be expected from the DC590 emulator, so perhaps this is the problem?

    Another possibility - are you trying to run QuikEval with the Arduino terminal open? If so, the terminal will claim the USB serial port, and QuikEval won't be able to access it. Try closing the terminal, and the Arduino IDE, too, just to be extra sure.

    A screenshot, and even a photo of your setup may also help.

    -Mark

  • 0
    •  Analog Employees 
    on Mar 1, 2021 10:21 PM in reply to mthoren_adi

    Realizing I overlooked the consequences of your Arduino setup. QuikEval also requires that the FTDI chip have the following string for a description:

    USB SERIAL CONTROLLER

    You would need to download the FTprog utility from FTDI to program this in. But if this does not work right away, there might be some other subtlety that I haven't thought of.

    Even after getting that sorted out, you'd need to either wire your ARduino's I2C bus to the eval board's EEPROM, or implement a hack in the DC590 emulator that's not terribly difficult, but might not be worth the effort.

    Again, depending on which part you're using, the QuikEval GUI may just be intended to show signs of life and basic functionality. (Not always true though.) The part-specific drivers and code examples tend to be much more useful. And once we know which part you're using, we can move the discussion to the appropriate product forum.

    -Mark

  • HI Mark and thanks for your help! i make the change you ask me to FT232RL and i change it from "FT232 USB UART" as was to "USB SERIAL CONTROLLER" and yes i see a difference action:
    1) first its take about 15 sec to take from QuickEval the message " The Usb to Serial controller not connected" and only RX pin of arduino led blink, before the change i take the above message in zero time like not connect nothinc on USB port.
    2) two times was connect after ten times tray and i take the message " Usb Controller connected but not board find" and disconnect after from maybe 2 or 3 seconds.

Reply
  • HI Mark and thanks for your help! i make the change you ask me to FT232RL and i change it from "FT232 USB UART" as was to "USB SERIAL CONTROLLER" and yes i see a difference action:
    1) first its take about 15 sec to take from QuickEval the message " The Usb to Serial controller not connected" and only RX pin of arduino led blink, before the change i take the above message in zero time like not connect nothinc on USB port.
    2) two times was connect after ten times tray and i take the message " Usb Controller connected but not board find" and disconnect after from maybe 2 or 3 seconds.

Children