DC2026C and DC2591

Hi All,

I have two of each of these boards and I'm having trouble with one of the DC2026 (Linduino). I'll just go through the debugging I've done. I've tested both Linduinos with:

1) Both DC2591

2) Both USB cables

3) Both power cables

4) Using both the Arduino IDE and MatLab

5) Both with only one Linduino connected, and with both Linduinos connected

One of the Linduinos works under all conditions, the other one does not work under any condition. Normally I would say that it's probably dead, however if I connect it as per its datasheet, I get the "hello" message in the Arduino IDE. However if I then send the command "CH0:ENA" (from the datasheet for the DC2591), I get no response. If I then give the command "CH0:VOL 0.5" nothing happens. Additionally, nothing happens if I give the command "*IDN?". If I do the same thing with the working Linduino, it operates as expected.

Can anyone help me with this?

Thank you.

UPDATE____________________________________________________________________

I probed the I2C signals for the device that works and the device that doesn't work. I noticed that on power-up, there is an I2C signal that the Linduino sends out (presumably to determine what's connected to it). I get that on the Linduino that works, regardless of whether the DC2591 is connected or not. I do not get that on the Linduino that doesn't work. Is it possible to flash the firmware, or did I just get a lemon?



UPDATE____________________________________________________________________ I probed the I2C signals for the device that works and the device that doesn't work. I noticed that on power-up, there is an I2C signal that the Linduino sends out (presumably to determine what's connected to it). I get that on the Linduino that works, regardless of whether the DC2591 is connected or not. I do not get that on the Linduino that doesn't work. Is it possible to flash the firmware, or did I just get a lemon?
[edited by: AR_MacDonald at 7:57 PM (GMT -4) on 29 May 2021]
  • Hi Mark,

    Since the SCK line is being driven low, the SCK led is continuously on.

    I tried uploading the sketch you provided and it failed. This is the error message I got:

    Arduino: 1.8.5 (Windows 7), Board: "Arduino/Genuino Uno"

    avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53
    Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
    Copyright (c) 2007-2014 Joerg Wunsch

    System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"

    Using Port : COM29
    Using Programmer : arduino
    Overriding Baud Rate : 115200
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x96
    avrdude: stk500_recv(): programmer is not responding
    avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x96

    avrdude done. Thank you.

    Problem uploading to board. See www.arduino.cc/.../Troubleshooting for suggestions.

    I think it's dead.

    Thanks for your help!

  • 0
    •  Analog Employees 
    on Jun 1, 2021 2:12 PM in reply to AR_MacDonald

    Let's check one more thing (maybe two) - There is a little copper trace labeled "jumper" on the reverse side of the board - can you verify that it is intact? (It will be if the board came from stock, through an authorized distributor.) The idea with this jumper is that IF you want to use one of the various debug tools through the 6-pin ISP header, you can cut that trace and do so. But it must be intact in order to use the normal Arduino IDE (AVRDude) programmer. IF the trace is cut, solder a wire (or 2mm jumper if you have one) from JP2, pins 1-2.

    The fact that you get the hello message implies that the processor is NOT in reset (R18 intact), but the fact that you can't program it implies that somehow the reset signal is not getting through. Also inspect C21 for cracks, cold solder, anything else suspicious.

    -Mark

  • Hi Mark,

    JP2 is okay. I ran a continuity test, and the trace is connected. I also inspected C21, and it looks fine, and both pads are connected as they should.

    He's dead, Jim.

  • 0
    •  Analog Employees 
    on Jun 4, 2021 1:07 AM in reply to AR_MacDonald

    Yup, it's looking that way, although I don't quite have an explanation. Corrupt bootloader maybe?

    Contact your vendor (assuming it was an authorized distributor.)

    -Mark

  • Yes, it's definitely strange. I don't think I've ever seen microcontroller peripherals selectively fail. Normally if any peripheral fails, the whole thing fails.

    I've already contacted Mouser and initiated an RMA.

    Thanks for your help!

    -Alexander