Programmers are not connected.

[debbieguo]

Hi DediProg team,
I recently received a new SF100 programmer and try to connect to my Linux computer, was able to built the software tool but got an issue to connect it.

$ ./dpcmd --list

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 14 2024

 
libusb: error [get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/003/018, errno=13
libusb: error [get_usbfs_fd] libusb requires write access to USB device nodes
Error: Programmers are not connected.

$ lsusb
...
Bus 003 Device 018: ID 0483:dada STMicroelectronics SF100-ISP
...

Could you help on this issue and/or provide a starting guide to connect it?

Thanks!
Debbie

[dan-gut1]

Look at the edit
I've also had the same issue, Am i doing something wrong?.
The programmer and SPI memory are recognized but when trying to program the flash programmer is not connected.

dmesg
[78504.834024] usb 1-3: new high-speed USB device number 8 using xhci_hcd
[78504.982648] usb 1-3: New USB device found, idVendor=0483, idProduct=dada, bcdDevice= 0.01
[78504.982652] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[78504.982654] usb 1-3: Product: SF600-ISP
[78504.982655] usb 1-3: Manufacturer: SF600-ISP
[78504.982657] usb 1-3: SerialNumber: 20101207-0000
_______________________________________________________________
sudo ./dpcmd --check

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024


1,      SF700397
        Programmer type : SF700
        Firmware version : 4.1.017
        FPGA version : 0x0a20
        Hardware version : 4.1

________________________________________________
sudo ./dpcmd --detect

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024



Device 1 (SF700397):    detecting chip
By reading the chip ID, the chip applies to [  N25Q00AA11G MT25QU01GB ]
N25Q00AA11G chip size is 134217728 bytes.
________________________________________________
 ./dpcmd --auto ~/SMARC.bin

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024


Error: Programmers are not connected.


SF100Linux-master$ sudo ./dpcmd -u~/SMARC.bin

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024


Error: Programmers are not connected.


________________________________________________
sudo ./dpcmd --list-device-id 1

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024


Error: Programmers are not connected.

Edit: Get ready for the OOOPPSSS
after writing this comment I've noticed different ticket with referring to commit that stating that --device flag with device ID should be applied to every command (There is no information for that anywhere), the command in the example works for me, maybe you should do the same.

 sudo ./dpcmd --device 1 --auto ~/SMARC.bin

DpCmd Linux 1.14.20.12 Engine Version:
Last Built on Aug 20 2024


By reading the chip ID, the chip applies to [ N25Q00AA11G ]

N25Q00AA11G parameters to be applied by default
N25Q00AA11G chip size is 134217728 bytes.


Loading file, please wait ...(/home/USER/SMARC.bin)

Auto Sequences, please wait ...
Device 1 (SF70018D):
26.7s elapsed

Device 1 (SF700397):
Automatic program OK

Checksum(whole file): 87148448
Checksum(Written part of file): 87148448

#89

[JacobLevinson]

Also having this issue, using the --device 1 worked for me.

[sylv-io]

Hi there,
Yes, this is a duplicate of my issue #89.
The regression is caused by commit 436ac5c from PR #87.

I will look into it since we have not heard back from the maintainers after 3 weeks.

[sylv-io]

I will look into it since we have not heard back from the maintainers after 3 weeks.

Nevermind, this code base is such a mess. 💩

[dan-gut1]

Dediprog wake up your programmers are costing fortune, even the windows software are full of bugs and crashing all the time!!!!!!
The minimum you need to provide is a decent software!

[debbieguo]

I have to use sudo to run ./dpcmd plus --device 1 to detect the proggramer.
But I still cannot flash ROM file, it gives no error message... Ended with using Windows tool.

[Benwang217]

Sorry guys, as @sylv-io mentioned it is cased by #87 , I will try to fix it and it will be fixed by next Friday.
@dan-gut1 Thx for your advice, if you can list real bugs for us, it will deeply appreciate your advice.

[robingergg]

@Benwang217 Is it solved? I ran:
./dpcmd --device 1 --check
but gives the error:
Error: Programmers are not connected.
Also I tried to run:
./dpcmd --device 1 -d
and got this output:
Error: Programmers are not connected. 1, detecting chip no deviceno deviceno deviceno deviceno deviceno deviceError: chip not identified or chip is not supported.

[Benwang217]

@8Klaro8 Yes, I just restored from #87, please try again.

[robingergg]

@Benwang217 For both command I get the very same result/error.
EDIT: it seems to be working. Thank you!

[jamesbergeron]

Hi, I've grabbed the latest build from here and I still have this problem in linux where I cannot program with --device 2.

I can do --device 1 it will program only the first device, or omit --device and it will program BOTH devices on my system but if I do --device 2 I get

(LOCALHOST):> dpcmd --auto myrom.rom --device 2

DpCmd Linux 1.14.21.12 Engine Version:
Last Built on Feb 24 2025

Error: Programmers are not connected.

dpcmd --list-device-id 0

DpCmd Linux 1.14.21.12 Engine Version:
Last Built on Feb 24 2025

1, SF120395
2, SF119778

But if I use the detect or blink function it does work!

(LOCALHOST):> dpcmd -d --device 1

DpCmd Linux 1.14.21.12 Engine Version:
Last Built on Feb 24 2025

1, detecting chip
By reading the chip ID, the chip applies to [ MX25U12835F MX25U12890F MX25U12873F ]

    MX25U12835F chip size is 16777216 bytes.

(LOCALHOST):> dpcmd -d --device 2

DpCmd Linux 1.14.21.12 Engine Version:
Last Built on Feb 24 2025

2, detecting chip
By reading the chip ID, the chip applies to [ MX25U12835F MX25U12890F MX25U12873F ]

    MX25U12835F chip size is 16777216 bytes.

(LOCALHOST):>dpcmd -d

DpCmd Linux 1.14.21.12 Engine Version:
Last Built on Feb 24 2025

Device 1 (SF120395): detecting chip
By reading the chip ID, the chip applies to [ MX25U12835F MX25U12890F MX25U12873F ]
MX25U12835F chip size is 16777216 bytes.

Device 2 (SF119778): detecting chip
By reading the chip ID, the chip applies to [ MX25U12835F MX25U12890F MX25U12873F ]
MX25U12835F chip size is 16777216 bytes.