Forum Discussion

Fred_Barkins's avatar
Fred_Barkins
Icon for New Contributor rankNew Contributor
8 months ago

DE1-SOC 5CSEMA5F31 isn't detected in Quartus Program Device

Hello, I'm having trouble programming my DE1-SoC from the Quartus Programmer. The board is powered and connected correctly and I've managed to find and program it before, multiple times, but even then it was very inconsistent in finding it. I tried to understand under what circumstances it finds the board but I really didn't do anything special in those times.

Under Hardware Setup --> Hardware Settings --> Currently selected hardware there only appears "No Hardware", and the DE1-SoC isn't listed:

I don’t manage to take a screenshot when the list is open, but the only option is “No Hardware” and the board isn’t listed.


$ ~/intelFPGA_standard/24.1std/quartus/bin/quartus_sh --version
Quartus Prime Shell
Version 24.1std.0 Build 1077 03/04/2025 SC Lite Edition
Copyright (C) 2025 Altera Corporation. All rights reserved.

$ uname -a
5.15.0-124-generic #134-Ubuntu SMP Fri Sep 27 20:20:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/udev/rules.d/51-usbblaster.rules
BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6810", MODE="0666"


I run quartus using sudo. I tried Terasic support but they suggested to reinstall, I find it weird because the hardware will occasionally (very very rarely, and I don't know what determines it) be found.


Any help would be much appreciated

Hdl

6 Replies

  • FvM's avatar
    FvM
    Icon for Super Contributor rankSuper Contributor
    8 months ago

    Hi,
    your .rules file is different from specification in USB Blaster II user guide. There should be an additional pid 6010 entry which is required for initial firmware download after USB Blaster II plug-in.

    Linux driver setup is a bit tricky, suggest to follow instructions exactly.

    Regards
    Frank

    • Fred_Barkins's avatar
      Fred_Barkins
      Icon for New Contributor rankNew Contributor
      8 months ago

      @FvM Thank you. Any chance you could link me to the specific guide showing what you mentioned please? couldn't find it
      Also, how does it fit with the fact that the software was able to detect the device on previous, random scarce occasions?

  • Fred_Barkins's avatar
    Fred_Barkins
    Icon for New Contributor rankNew Contributor
    8 months ago

    I should also mention:

    $ cat /etc/modprobe.d/DE1-SoC.conf

    alias usb:v09FBp6810* ftdi_sio install ftdi_sio /sbin/modprobe -i ftdi_sio && /bin/echo 09fb 6810 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id

    $ lsusb

    Bus 001 Device 006: ID 10c4:ea70 Silicon Labs CP2105 Dual UART Bridge

  • Fred_Barkins's avatar
    Fred_Barkins
    Icon for New Contributor rankNew Contributor
    8 months ago

    I Try with
    $ cat /etc/udev/rules.d/51-usbblaster.rules
    SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6010", MODE="0666"
    SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6810", MODE="0666"

    Still nothing.

  • FakhrulA_altera's avatar
    FakhrulA_altera
    Icon for Regular Contributor rankRegular Contributor
    8 months ago

    Hi Fred_Barkins,


    Just following up, any updates on your side?


    Have you had the chance to check the DIP switch settings for the MSEL configuration? Misconfigured MSEL settings can often lead to detection or programming issues.


    You might also find some helpful suggestions from similar cases in the Intel forums:

    1. DE1-SoC Cyclone V not getting detected
    2. Unable to program DE1-SoC device


    Let me know if you’ve tried any of these steps or need further assistance.


    Best regards,

    Fakhrul


  • FakhrulA_altera's avatar
    FakhrulA_altera
    Icon for Regular Contributor rankRegular Contributor
    7 months ago

    Hi Fred_Barkins,


    As we haven't received a response to our previous notification, this thread will be transitioned to community support. We hope all your concerns have been addressed. If you have any new questions, please feel free to open a new thread to receive support from Intel experts. Otherwise, community users will continue to assist you here. Thank you.