Routing error

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

There is definitely fewer places I can find answers to issues I have here than if I were in the PIC world.

   

I tried Cypress Document Manager search, Cypress site search and Google search for the error code I get when I build my code (mpr.M0145) and got 0 results.

   

So I have to bother the good people here again.

   

First can someone tell me where I could have found the answer to this without a forum topic?

   

And, here is what I think is the easiest way to show my issue:

   

🙂 Well that did not work, can't insert jpg, so I attached it.

   

The .cydwr file shows a valid assigned pin but I am told I can not route to the pin.

   

1/2 hr on this was enough.

   

Thanks,

   

Dale

0 Likes
9 Replies
ETRO_SSN583
Level 9
Level 9
250 likes received 100 sign-ins 5 likes given

In the PSOC 4 family there is restricted routing, more so than the 3 and 5LP families.

   

Low cost parts equate to less features, a fact we all face as designers.

   

 

   

Best to post your project so forum can evaluate the root cause of the problem.

   

 

   

“File”                                                             Creator

   

“Create Workspace Bundle”

   

 

   

 

   

Regards, Dana.

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

First, I have just been adding peripherals to my .cysh from a blank sheet and I really don't know what I am doing yet.

   

Not sure what stops me from adding too many PWM's for instance the way PIC's Code Configurator does.

   

But I figure it should build.

   

Wow, that was a bigger file than expected 🙂

0 Likes
lock attach
Attachments are accessible only for community members.
ETRO_SSN583
Level 9
Level 9
250 likes received 100 sign-ins 5 likes given

I think this is the problem, attached, from TRM.

   

 

   

Regards, Dana.

0 Likes
Anonymous
Not applicable

Sounds like it but I thought I was just using it as a firmware pin that I feed a signal into and an interrupt is generated when the signal falls.

   

0 Likes
Anonymous
Not applicable

I moved it to P1[6] and I get even more complicated errors which I saw when I tried this before.

   

I went to the report file and it was no help so I went back to P5[0] and started the thread.

   

Any ideas when you put it to P1[6]?

0 Likes
Anonymous
Not applicable

So, the wording of your find, made me go back and look at the properties of the AMSINT pin.

   

On the input tab where you select the falling edge interrupt trigger, I saw a Sync Mode parameter which rung the bell.  I set it to Transparent and Voila!

   

Unfortunately, I now get the more complicated error I spoke of above!

0 Likes
ETRO_SSN583
Level 9
Level 9
250 likes received 100 sign-ins 5 likes given

On this specific route I would file a CASE, unless someone else can explain

   

this.

   

 

   

To create a technical or issue case at Cypress -

   

 

   

www.cypress.com

   

“Support”

   

“Technical Support”

   

“Create a Case”

   

 

   

You have to be registered on Cypress web site first.

   

 

   

Regards, Dana.

0 Likes
Anonymous
Not applicable

Thanks for your help!!

   

I will do it in the morning.

   

Dale

0 Likes
Anonymous
Not applicable

It turns out I made a simple error by routing my I2C lines backwards, not sure why it would 'let' me do that.

   

I had put SDA to SCK and SCK to SDA.

   

Great support, I had the answer within a couple hours of creating ticket!

0 Likes