CrossWorks can't find device drivers for CrossConnect Pro

Comments

10 comments

  • Avatar
    Paul Curtis

    They are identical, yes.  There are newer inf files in the latest distribution of the drivers.

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    ....I should also add that all CrossConnect Pros that have gone out are now in use and working well.  So, I know the drivers do work.  I assume your Pro installed correctly and is shown correctly in the Device Manager?

    0
    Comment actions Permalink
  • Avatar
    Sandy Kellagher

    Yes, Device Manager says that CrossConnect Pro is installed and working correctly. But CrossWorks complains with the error message above. I have tried uninstalling and re-installing the driver, but this makes no difference.

     

    To be precise, this is happening on my desktop PC only; my laptop does not report this error (and indeed my desktop didn't use to). The behaviour on my laptop  is that CrossWorks connects to the JTAG probe OK, but doesn't communicate reliably. For example, when I attempt to start a debug session, I will get a "Write operation timed out" error message when downloading the loader.elf.

    So I have not yet had any of the CrossConnect Pro's working reliably at this point (and have tried two different physical units).

    At the risk of being provocative, I am disappointed to be having difficulties with the CrossConnect Pro's when the Segger J-Link that we happened to have lying around has been working faultlessly for months now...

    Regards
    Sandy

     

     

     

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    What target CPU are you connecting to with the CrossConnect Pro?

    Also, there was an issue with a dangling c_str() coming out of a function; this has been corrected in the latest CrossStudio after we saw it.  It only manifests itself occasionally, but seems persistent on machines that suffer from this.

    I'll send you a link to the latest V2 hotfix for this.

    0
    Comment actions Permalink
  • Avatar
    Sandy Kellagher

    hi Paul,

    It's an Atmel ARM9 device - AT91SAM9XE512.

    Thanks
    Sandy

     

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    You may well need a firmware upgrade for this device.  It comes out of reset at 32kHz, IIRC, which requires a 5kHz TCK.  The Pro won't go that slowly without a firmware upgrade.

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    ...having said, that, the SAM9 uses adaptive clocking, so set Adaptive Clocking = Yes in the target interface and the 32kHz problem should disappear and you don't need a firmware upgrade.  But I believe you should upgrade to v2.3 of the firmware anyway.  I have issued this on an ad-hoc basis in the past, but we will now formalize it by either integrating it into CrossStudio or by providing a new updater.

    0
    Comment actions Permalink
  • Avatar
    Phillip Malawey

    I have experienced the same problem.  We just purchased a CrossConnect Pro a couple of months ago.  I just tried to fire it up on two different desktop systems.  The CrossConnect Lite works fine.  I am using an ARM LPC2366 target.  Was this issue resolved?

    0
    Comment actions Permalink
  • Avatar
    Paul Curtis

    Which issue are you discussing?  The title issue of not being able to find Pro drivers?

    0
    Comment actions Permalink
  • Avatar
    Dalgeo

    Paul,  I am using Fedora23 and the standard crossconnect works but the crossconnect pro does not work.  "Error - can not find USB device."   I bought it a while ago and never worked but thought it was because i was using an old version of Fedora.   I just upgraded and still get same results.

    How to configure the pro?  

    0
    Comment actions Permalink

Please sign in to leave a comment.