Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
X
x353
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
Elphel
x353
Commits
f9979c6b
Commit
f9979c6b
authored
Jul 26, 2015
by
Andrey Filippov
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
reformatting README.md
parent
d0085ebb
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
README.md
README.md
+8
-0
No files found.
README.md
View file @
f9979c6b
...
@@ -30,15 +30,21 @@ WARNING:Xst:3152 - You have chosen to run a version of XST which is not the defa
...
@@ -30,15 +30,21 @@ WARNING:Xst:3152 - You have chosen to run a version of XST which is not the defa
on the XST command line or in the XST process properties panel.
on the XST command line or in the XST process properties panel.
```
```
also failed. After I added recommended options:
also failed. After I added recommended options:
```
```
run -use_new_parser no -ifn x353.prj -ofn x353.ngc -top x353 -p xc3s1200eft256 -uc x353.xcf -opt_mode speed -opt_level 1
run -use_new_parser no -ifn x353.prj -ofn x353.ngc -top x353 -p xc3s1200eft256 -uc x353.xcf -opt_mode speed -opt_level 1
```
```
and ISE noticed that:
and ISE noticed that:
```WARNING:Xst:1583 - You are using an internal switch '-use_new_parser'.
```WARNING:Xst:1583 - You are using an internal switch '-use_new_parser'.
```
```
It still repeated the same WARNING:Xst:3152 (see above) disregarding its own suggestion.
It still repeated the same WARNING:Xst:3152 (see above) disregarding its own suggestion.
So we will need to find a way how to replace lines in the
*
xst file that cause errors in XST:
So we will need to find a way how to replace lines in the
*
xst file that cause errors in XST:
```
```
204 TIMEGRP "CPU_ADDR" = pads("A<*>");
204 TIMEGRP "CPU_ADDR" = pads("A<*>");
205 TIMEGRP "CPU_ADDRCE" = "CPU_ADDR" pads("CE*");
205 TIMEGRP "CPU_ADDRCE" = "CPU_ADDR" pads("CE*");
...
@@ -49,10 +55,12 @@ So we will need to find a way how to replace lines in the *xst file that cause e
...
@@ -49,10 +55,12 @@ So we will need to find a way how to replace lines in the *xst file that cause e
209 TIMEGRP "DREQ_PAD"= pads("DREQ*");
209 TIMEGRP "DREQ_PAD"= pads("DREQ*");
210 TIMEGRP "ALLPADS"= pads("*");
210 TIMEGRP "ALLPADS"= pads("*");
```
```
```
```
ERROR:Xst:1888 - Processing TIMEGRP CPU_ADDR: User group 'pads("A<*>")' defined from other
ERROR:Xst:1888 - Processing TIMEGRP CPU_ADDR: User group 'pads("A<*>")' defined from other
user group pattern not supported.
user group pattern not supported.
```
```
Even Google does not know what to do about this Xilinx XST feature: No results found for "ERROR:Xst:1888".
Even Google does not know what to do about this Xilinx XST feature: No results found for "ERROR:Xst:1888".
So we'try to find other ways to re-formulate old timing constraints preserving the same meaning and try
So we'try to find other ways to re-formulate old timing constraints preserving the same meaning and try
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment