"Patrick Dubois" <prdubois@gmail.com> wrote in message news:1184331575.895094.145910@n60g2000hse.googlegroups.com...> On Jul 13, 7:19 am, "Symon" <symon_bre...@hotmail.com> wrote: > >> Hi Patrick, >> So I'm still using 8.2, and this isn't the behaviour I see. An import >> overwrites any previous edits. Is this a new feature for 9.1? >> >> > In order to help you setting up the Chipscope Analyzer project, take a >> > look at csptool: >> >http://code.google.com/p/csptool/ >> >> I downloaded it, sounds interesting, many thanks. >> >> All the best, Syms. > > I have been using Chipscope since v7 and I think that it's always been > like that. After you load a new bit file, disconnect and reconnect the > JTAG (JTAG chain menu). Chipscope will then discover that the number > of signals changed and a dialog will pop-up asking if you want to > preserve signals names (choose yes). Then you will see new unnamed > signals in your signals list (they won't be in the waveform). Now you > can simply import the new cdc file to retreive the name of these new > signals. The rest of the Analyzer design should stay intact. > > Cheers, > Patrick >Hi Patrick, So, I followed your instructions, but at the point where I import the new cdc file, the signal names _ALL_ revert to the names in the design, even ones I have renamed. The triggers and busses do remain unchanged, but signals that have been renamed revert their names. Arse! This is with 8.2. Cheers, Syms.
Chipscope 9.1: Any easy way to rename and regroup signals?
Started by ●July 12, 2007
Reply by ●July 13, 20072007-07-13
Reply by ●July 13, 20072007-07-13
On Jul 13, 11:36 am, "Symon" <symon_bre...@hotmail.com> wrote:> Hi Patrick, > So, I followed your instructions, but at the point where I import the new > cdc file, the signal names _ALL_ revert to the names in the design, even > ones I have renamed. The triggers and busses do remain unchanged, but > signals that have been renamed revert their names. Arse! > This is with 8.2. > Cheers, Syms.Oh, I had misunderstood your problem. Yes the signals names will revert to the ones in the cdc file... What is kept is things like colors, buses you created, triggers... But not the names, sorry about the confusion! I never ran into that problem because I don't change the names of the signals. Yet one more simply feature that the Chipscope GUI should have... If you really need that feature, you could try to modify the csptool script to create a "custom cdc import" feature. That would be fairly involved however because csptool can only parse .cpj files, not .cdc ones. Alternatively, you could try to modify the cdc file to only keep the new signals, and then import this partial cdc file. If you're lucky it will work... Patrick
Reply by ●July 15, 20072007-07-15
"Patrick Dubois" <prdubois@gmail.com> wrote in message news:1184344666.626506.194870@m3g2000hsh.googlegroups.com...> On Jul 13, 11:36 am, "Symon" <symon_bre...@hotmail.com> wrote: > > Oh, I had misunderstood your problem. Yes the signals names will > revert to the ones in the cdc file... What is kept is things like > colors, buses you created, triggers... But not the names, sorry about > the confusion! I never ran into that problem because I don't change > the names of the signals. Yet one more simply feature that the > Chipscope GUI should have... >Hi Patrick, Thanks for your reply, I'm glad that we see the same behaviour. I thought I was missing out on something!> > If you really need that feature, you could try to modify the csptool > script to create a "custom cdc import" feature. That would be fairly > involved however because csptool can only parse .cpj files, not .cdc > ones. > > > Alternatively, you could try to modify the cdc file to only keep the > new signals, and then import this partial cdc file. If you're lucky it > will work... > > Patrick >Actually, this might not be too bad, the cdc file is pretty obvious, and it would be easy to remove the 'pathname' of the instance with a perl script. Even though it wouldn't keep renamed signals, at least I could reduce the length of the names to something more manageable. If I get around to bashing one out, I'll post it. Thanks again, Syms.
Reply by ●July 15, 20072007-07-15
On Jul 12, 6:29 pm, Patrick Dubois <prdub...@gmail.com> wrote:> On Jul 12, 12:03 am, Yao Sics <yao.s...@gmail.com> wrote: > > > Hi Xilinx Killers, > > > It is really annoying to rename and group all the signals everytime > > when design is modified and new bit file is used to configure the > > fpga. Anybody knows how to avoid renaming and regrouping signals in > > the analyzer when new bit file is loaded to FPGA? > > When adding new signals to a Chipscope project, I try to add them at > the end to avoid screwing up the project. That way you can simply > import your new .cdc file into your Chipscope Analyzer project and all > the previous signals will stay intact (and the new signals will > appear). Avoid inserting new signals by moving other signal positions > around, as this will screw up the project. > > In order to help you setting up the Chipscope Analyzer project, take a > look at csptool:http://code.google.com/p/csptool/ > > It's a little Perl script that regroups buses for you. Might be > overkill if you have a few buses, but if you have tens, it can be very > handy. > > > And one more quick question, how to investigate state_reg of a FSM by > > usingchipscope? Because the original name of the interesting > > state_reg is modified after synthesis, I dont't know which signal I > > should investigate now. > > You can look at the synthesis report to see how XST encoded the > states. Then I suggest that you create a .tok file to display the name > of the state in the waveform window. Look at \ChipScope_Pro_9_1i\bin\nt > \token\token_sample.tok for an example. > > PatrickHi Patrick, How do I download your script source code? At csptool:http://code.google.com/p/csptool/ I couldn't fine any download files. Thank you. Weng
Reply by ●July 16, 20072007-07-16
On Jul 15, 3:21 pm, Weng Tianxiang <wtx...@gmail.com> wrote:> Hi Patrick, > How do I download your script source code? > > At csptool:http://code.google.com/p/csptool/I couldn't fine any > download files. > > Thank you. > > Wenghttp://code.google.com/p/csptool/source Click on "Subversion repository". Then browse to \trunk\csptool.pl Alternatively, I made an executable available (long overdue): http://csptool.googlecode.com/files/csptool.zip Thanks for your interest Patrick.
