jamesglanville Posted May 7, 2013 Report Share Posted May 7, 2013 EDIT: fixed, needed to change fpga startup clock to CCLK instead of JTAG. I'm having some trouble with my ppro loading its program from flash. I've tried papilio loader 2.1 and 2.4, and write to spi flash runs, and looks like it has worked from the pc end, as it says: JTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9Using devlist.txtJTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9Uploading "C:\Program Files (x86)\Gadget Factory\Papilio Loader24\programmer\bscan_spi_xc6slx9.bit". DNA is 0x19413851fc72cbfeDone.Programming time 547.0 msProgramming External Flash Memory with "G:\Downloads\LCD-Driver-0.1\LCD-Driver\controller.bit".Found Macronix Flash (Pages=32768, Page Size=256 bytes, 67108864 bits).Erasing :Doing Partial Erase......OkVerifying :......PassProgramming :......OkVerifying :......PassUsing devlist.txtDone.SPI execution time 17254.4 msUSB transactions: Write 17348 read 17179 retries 0JTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9Using devlist.txtISC_Done = 0ISC_Enabled = 0House Cleaning = 0DONE = 0However, afterwards the board just sits doing nothing. writing straight to the fpga works fine. This is on win8 x64 if that makes any difference. If anyone could help it'd be appreciated. Link to comment Share on other sites More sharing options...
jamesglanville Posted May 7, 2013 Author Report Share Posted May 7, 2013 I've tried with xc3sprog in a vm, and get this: james@ubuntu:~/Papilio-Loader/xc3sprog/trunk$ sudo ./xc3sprog -c papilio /home/james/controller.bit -v -R -I ./bscan_spi/bscan_spi_lx9_papilio.bit XC3SPROG © 2004-2011 xc3sprog project $Rev: 691 $ OS: LinuxFree software: If you contribute nothing, expect nothing!Feedback on success/failure/enhancement requests:http://sourceforge.net/mail/?group_id=170565 Check Sourceforge for updates:http://sourceforge.net/projects/xc3sprog/develop Using devlist.txtUsing cablelist.txtCable papilio type ftdi VID 0x0403 PID 0x6010 dbus data 00 enable 0b cbus data 00 data 00Using Libftdi, Using JTAG frequency 6000000JTAG chainpos: 0 Device IDCODE = 0x24001093 Desc: XC6SLX9JEDEC: ff ff 0xff 0xffunknown JEDEC manufacturer: ffCreated from NCD file: controller.ncd;HW_TIMEOUT=FALSE;UserID=0xFFFFFFFFTarget device: 6slx9tqg144Created: 2013/05/07 19:41:54Bitstream length: 2724832 bitsProgramming not yet implementedUSB transactions: Write 6 read 4 retries 8 I don't know if the unknown manufacturer bit is the relevant part, but it looks dodgy. Link to comment Share on other sites More sharing options...
alex Posted May 8, 2013 Report Share Posted May 8, 2013 Try again with Papilio loader 2.4 and after the programming has completed, power board off and on again. Does the board still sit there doing nothing or does it work as expected? Link to comment Share on other sites More sharing options...
jamesglanville Posted May 8, 2013 Author Report Share Posted May 8, 2013 It just sits doing nothing. am I right that the gui hasn't been updated with the new version number everywhere? The 2.4 version I'm using says 2.1 at the top. Link to comment Share on other sites More sharing options...
jamesglanville Posted May 8, 2013 Author Report Share Posted May 8, 2013 Just a thought, I think I've pressed the reset button at some point, could that have caused the problem (though i've never got auto boot to work)? I'm trying to understand the multiboot xilinx datasheet but it's going over my head at the moment. Link to comment Share on other sites More sharing options...
jamesglanville Posted May 8, 2013 Author Report Share Posted May 8, 2013 Fixed it I had to right click on "generate programming file", go to startup options, and set the FPGA start up clock to CCLK instead of JTAG. I have no idea why it was set to that in the first place :s maybe this is something that should go in the faq/ papilio loader should complain if the .bit file has the wrong option for this? Link to comment Share on other sites More sharing options...
hamster Posted May 8, 2013 Report Share Posted May 8, 2013 Excellent to hear that you have found the problem - that is a tricky one to find! I don't think the loader will be able to tell what the startup clock is set to - the BIT file is a bit of a black box.... Link to comment Share on other sites More sharing options...
Jack Gassett Posted May 8, 2013 Report Share Posted May 8, 2013 Phew, I'm glad you got that worked out... That's a strange one, it implies that the problem was only showing up with bit files that you were making in your version of ISE right? Jack. Link to comment Share on other sites More sharing options...
jamesglanville Posted May 8, 2013 Author Report Share Posted May 8, 2013 Yeah I guess so, I haven't tried anyone else's .bit files. It's a really strange issue, I'm so chuffed I worked it out, it took me reading a lot of the lx9 datasheet and guessing. It surprised me that ISE didn't warn me, since it warns about other stuff, and starting off the jtag clock seems like an unusual configuration. Link to comment Share on other sites More sharing options...
Jack Gassett Posted May 8, 2013 Report Share Posted May 8, 2013 Yeah, that is one of those options I never looked into that much, weird it was defaulting to it... Jack. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.