First build: Find pin assignments automatically
Then lock found pins
Build again: Results in more warnings!
That#s a bit difficult to answer without having the input at hand.Can you post your complete project, so that we all can have a look at all of your settings? To do so, use
Creator->File->Create Workspace Bundle (minimal)
and attach the resulting file.
I didn't attach the archive intentionally, as I see this as a fundamental problem. Pin-assignments, which are found by the software, should not lead to different results, when I start the same software with them. - But ok. Attached my archive. - Thanks!
I removed all the locks for the pins, rebuilt the project and got 3 warnings and two notes.
Then I locked all pins again, rebuilt and got two warnings and some notes.
One warning was about an unused variable, the other was the same as in the run before, telling that some unused I/O pins were additionally used to route to the the required target-pin.
So I cannot reproduce your issue
Strange! I did four runs. First pair with eight pre-locked pins, second pair without. Everytime locking all pins found in the first run of the pair. Strange things happen. Most weird is the message of opamp-output not compatible with P1_2. Analog wiring view shows everything correct. Second is the setup time violation. Sometimes yes, sometimes not. Is there any kind of fuzzy logic in Creator? And 28fs!? Would you care about this? I won't.
Best greetings, Andreas
You might consider filing a CASE on this and pointing to this thread. This type
of inconsistency ripe for repair.
/* Style Definitions */
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
To create a technical or issue case at Cypress -
“Create a Case”
You have to be registered on Cypress web site first.