Post Go back to editing

ADICUP 360 Disconnects Automatically During DEBUG Mode

Hi,

I am working with an ADICUP360 EVAL-BOARD for the past 3-4 weeks. I am using the board for reading values from ADXL355-PMDZ accelerometer.

Recently, I have noticed that the board disconnects itself automatically after a duration of 3-4 seconds, whenever I am using it in DEBUG mode through a USB cable. The switches configuration is (S1: 0 || S2: 0 || S3: 1 || S4: 0). Often, the device gets disconnected before the program is completely booted into it.  I am using CROSSCORE EMBEDDED STUDIO. 

When I am reading the values in USER mode (through serial in PUTTY), the device remains active and does not show any abnormal behavior. Can someone help me out to identify the problem here and how to fix it? I will be thankful.



Mistake in title has been fixed.
[edited by: its.saadur at 12:02 AM (GMT 0) on 28 Mar 2019]

Can you provide some more information? 

Can you tell me what operating system you are using?  Does this happen if you try to load the blinky or CLI demo example from Github?  Do you have any other boards…

  • I am using Windows 10 on a laptop.

    This happens regardless of whether I am uploading a program or not. Like, I connect the board via USB with the computer and after 5-10 secs, it disconnects itself and…

  • Can you provide some more information? 

    Can you tell me what operating system you are using?  Does this happen if you try to load the blinky or CLI demo example from Github?  Do you have any other boards which you could try to see if this problem exists?  

    There is a note on the ADXL355 user guide page that says you should remove R1 on the EVAL-ADXL355-PMDZ when using the ADICUP360, have you done that?  (https://wiki.analog.com/resources/eval/user-guides/eval-adicup360/hardware/adxl355 )

  • I am using Windows 10 on a laptop.

    This happens regardless of whether I am uploading a program or not. Like, I connect the board via USB with the computer and after 5-10 secs, it disconnects itself and connects itself afterwards (2-3 secs after).

  • Hello Saadur,

    What revision is the board? And what version of CCES are you using?

    Regards,

    Andrei.

  • Hi Anrei,

    CCES version is 2.8.2.0

    Board revision 1.1.

  • There might be a workaround, but it's a bit uncomfortable.

    Nonetheless, try the following:

     1. Connect the ADICUP360 board to the PC.

     2. Restart the PC with the board connected. This serves to both update/install the driver in case it's necessary and undo the various changes starting CCES has done.

     3. Start CCES and try to debug the project.

    Until the real solution to this problem is found this process might help.

    Let me know if this works.

    Regards,

    Andrei.