11-29-2010 03:47 PM
I really like the updates to PicoBlaze - in particular the OUTPUTK which is going to save me significant valuable code space!
I've got my first kcpsm6 build up and running using Windows 7 64-bit without any problems! (although at this stage only some simple led flashing code.)
I have however not been able to get the JtagLoader.exe to see my hardware. After running 'settings32.bat' & running it I get the following:
__ _ __ _
\ \| |_ __ _ __ _ / / ___ __ _ __| | ___ _ __
\ \ __|/ _` |/ _` |/ / / _ \ / _` |/ _` |/ _ \ '__|
/\_/ / |_| (_| | (_| / /___| (_) | (_| | (_| | __/ |
\___/ \__|\__,_|\__, \____/ \___/ \__,_|\__,_|\___|_|
JTAG Loader by Kris Chaplin, Xilinx UK
Use the -h option if you need help
Info:Connecting to cable (Usb Port - USB21).
Info:Checking cable driver.
Info: Source driver files not found.
Info:The Platform Cable USB is not detected. Please connect a cable.If a cable is connected, please disconnect
and reconnect to the usb port, follow the instructions in the 'Found New Hardware Wizard', then retry
the Cable Setup operation.
Info:Cable connection failed.
(Targetting a SP601 dev board which loads fine using Impact.)
I'm guessing that I will need a 64-bit version of JtagFlasher.exe? If so, is one likely to be available soon or should I get to work on a UARTloader implementation...
11-30-2010 01:55 AM
I have not specifically tried with Windows 7 64-bit. However, as a part of our rollout, I will be installing Win7-64 this week. I'll take a look later on to see if I can spot the issue.
In the mean time, have you checked that the ISE tools and libraries are in your path?
11-30-2010 05:01 AM
I tried using settings64.bat (from the ISE_DS folder) but JtagLoader.exe would not run, when I switched to using settings32.bat it ran but gave me the results posted previously. I've noticed that while the ISE install includes 32 and 64 bit versions of most of the applications, it only includes a 64-bi version of Impact - this leads me to believe that a 64-bit version of JtagLoader.exe will have to be used.
12-03-2010 07:48 AM
I have added a new thread in this forum introducing an Alpha program for 64-bit support. Please read through this, and apply to help me test this!
12-17-2010 11:40 AM
"f you can help confirm that the KCPSM6 assembler is stable under your environment then it would make sense for me to add legacy support for KCPM3 into the KCPSM6 assembler (or a variant of it). That would also cover the requests I’ve received from KCPSM3 users that would just like to be able to use the enhanced syntax of the new assembler which is something else I can’t add in the old one."
Okay, I've been using KCPSM6 for a while now (as well as some of my other co-workers). And we would all like KCPSM3 functionality for Win7 64-bit. We don't really care about enhanced syntax. If you just get the current version of KCPSM3 working on Win7 64-bit that's all we need.
01-17-2011 07:58 AM
I have just finished writing an KCPSM3 Assembler for Windows. It should not come as any surprise to know that this has been derived from the KCPSM6 Assembler so it also supports the new syntax options for definition of constant values etc.
However, this is very much intended to be an interim solution for users. When possible, I would recommend users to continue using the original tools provided with KCPSM3 as that solution is known to be stable. Then when possible to move fully over to KCPSM6 and the newer generations of silicon devices.
As such, I cannot claim to have performed much testing of this Windows version of the KCPSM3 Assembler so I am now looking for users that are prepared to try it out and provide me with feedback. So if you would like to help please email me privately (do not make a request on this forum). My email address is provide on page 3 of 'KCPSM3_Manual.pdf' as well as in various KCPSM3 files.
Principal Engineer, Xilinx UK
02-06-2011 12:54 PM - edited 02-06-2011 01:11 PM
Just to let everyone know. I have just tested out Ken's new Win7 64-bit compatible version of kcpsm3 compiler and it works _perfectly_. It produced identical verilog/vhdl results as the DOS-based version - but with one big difference - no more need for a virtual machine running XP!! Great job Ken!! This will make my job much easier.