• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About amalawi

  • Rank

Profile Information

  • Gender Not Telling
  1. Magnus, this is strange as both of the front 2 USBs as well as some of the back ones (3 USBs) are giving this high number of retries ~32000, however, there is also another 2 back USBs which gave ~4000 retries !? maybe its the PC or the power line or another thing, I'll keep investigating, but thanks for indicating that this number should be normally 0. Using the -C or -c trick with the lower retries ports (the 2 back USBs) does the trick but should be on a separate terminal line. Another thing is that after batching progalgxc3s.cpp with your code snippet, I'm me able to use the -r option, though, this should be on a separate invocation (2 steps, program cmd line, reconfiguration cmd line). I had looked through the source code of butterfly.cpp and noticed that reconfiguration does not happen when the user wants spiflash (which is my case), thus I had also make a kludge and copied the "if (reconfigure)" from the else branch of "if (spiflash)" into the positive branch (after line 347). After compiling I can now specify the -r option in the same command line and get it also reconfigured after programming (Great!) I'll continue with the tutorial and at the same time check if I can pin down the issue of high number of retries. Thanks! Ala'a
  2. nither -vc nor -C caused the gadget to show the example code. I needed to power cycle it. here is the terminal output : sudo papilio-prog -vC Using built-in device list JTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9 STAT Register ID_ERROR = 0 IDCODE not validated. DONE = 0 Input from the DONE pin. INIT = 0 Input from the INIT pin. MODE = 000b Input from the MODE pins (M2:M0). GHIGH_B = 0 0 = asserted. GWE = 0 0 = all FFs and Block RAMs are write-disabled. GTS_CFG = 0 0 = all I/Os are 3-stated. IN_ERROR = 0 Legacy input error. DCI_MATCH = 0 DCI is matched. DCM_LOCK = 0 DCMs are locked. CRC_ERROR = 0 CRC error. USB transactions: Write 6 read 4 retries 1 In the moment power cycling should not be a big issue. Any way thanks for the support!
  3. After playing again, it will work after I disconnect the device and reconnect it. Is this the correct way? that it will not run after programming and I need to unplug-plug the usb cable? Thanks in advance
  4. Thanks for the prompt response. I tried the command line which gave the following output that says everything is ok (erasure, verification, programming and final verification) , however, the fpga is not programmed (meaning the example is not working as expected) : sudo papilio-prog -f chapter7.bit -b ~/Downloads/Papilio-Loader-master/Fpga/bscan_spi_lx9.bit -v -sa -rUsing built-in device listJTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9 Uploading "/home/alaa/Downloads/Papilio-Loader-master/Fpga/bscan_spi_lx9.bit". DNA is 0x39ea4e6060d673ffDone.Programming time 540.1 ms Programming External Flash Memory with "chapter7.bit".Found Macronix Flash (Pages=32768, Page Size=256 bytes, 67108864 bits).Erasing :Doing Partial Erase......OkVerifying :......PassProgramming :......OkVerifying :......PassDone.SPI execution time 17319.6 msUSB transactions: Write 6851 read 6682 retries 6492
  5. Hi, I have a papilio pro board and going through IntroToSpartanFPGABook. I notice that while using Papilio Loader 2.7, I can test the examples using the 'FPGA' write to: option, but the 'SPI Flash' will not persist if i disconnected the usb cable. The terminal shows the following: : sudo papilio-prog -b chapter7.bit -s e -v Using built-in device listJTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9 Uploading "chapter7.bit". DNA is 0x39ea4e6060d673ffDone.Programming time 541.9 msErasing External Flash Memory.Uknown Flash Manufacturer (0x00)Error: SPI Status Register [0x00] mismatch (Wrong device or device not ready)..Error occured.USB transactions: Write 178 read 10 retries 9 I'm running Linux Mint 17.1 - x86_64 (3.13.0-37-generic #64-Ubuntu SMP)