Search the Community: Showing results for tags 'fault'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • GadgetBox Universal IoT Hardware
    • GadgetBox General Discussion
  • Papilio Platform
    • Papilio General Discussion
    • Papilio Pro
    • Papilio One
    • Papilio DUO
    • Papilio Wings
    • DesignLab IDE
    • DesignLab Libraries
    • RetroCade Synth
    • Papilio Arcade
    • Papilio Loader Application
    • Papilio Logic Sniffer
    • Retired
  • Electronics
    • Modules
  • Soft Processors
    • ZPUino
    • J1 Forth
    • AVR8 Soft Processor
  • Community
    • Gadget Factory
    • Documentation
    • FPGA Discussions
    • Community Projects
    • Pipistrello
  • Open Bench
    • Open Bench Logic Sniffer at Dangerous Prototypes
    • OpenBench Logic Sniffer at Gadget Factory
  • Gadget Factory Internal Category

Categories

  • Papilio Platform
    • Papilio One
    • Papilio Plus
    • Papilio Wings
    • LogicStart MegaWing
    • ZPUino
    • Papilio Pro
  • Papilio Arcade
  • RetroCade Synth
  • Logic Sniffer
  • FPGAs
  • DesignLab
    • Example Projects
    • Libraries

Categories

  • Papilio FPGA
    • Papilio UCF (User Constraint) Files
    • Papilio Bit Files
  • Papilio Arcade
  • RetroCade Synth
  • General
  • Beta (Test) Releases
  • Books

Found 1 result

  1. Hi there, I'm on Ubuntu 14.04 and after much faff trying to get my PP to work, I think it is knackered. I get this when programming: Programming to SPI FlashUsing built-in device listCannot find device having IDCODE=00010440Unknown Papilio BoardUsing built-in device listCannot find device having IDCODE=00400400IOException: Cannot open file USB transactions: Write 4 read 3 retries 0Error while burning bitfile. The IDCODE fields seem to be random when I run papilio-prog several times. I assume that means the FTDI is mangling the serial data? Any ideas? I've also got a DUO. Works perfectly with this same setup. I tried installing the linux 'drivers' but these seem to just install libftd2xx which isn't even linked against the papilio-prog (which uses open source libfdti) AND doesn't contain a linux kernel module either so I don't understand their relevance to anything. It does have a libusb in there though. Haven't tried that, get the feeling it's not going to help things.. The default FTDI drivers in Ubuntu work fine after running ubuntu-setup.sh, with the Duo. Minor note: Think it would be a good idea to remove all references to ftdi_user.sh. Spent a while searching the net for this script before discovering somewhere it is now ubuntu-setup.sh. Error msg in DesignLab 1.0.7 still refers to ftdi_user.sh too. Kind Regards,Chris