- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had a pin set up as analog in to a comparator and also digital in. I moved it to a scanning comparator, and got this error:
Cannot use pin as digital HW output when it is connected to an analog HW mux.
If a GPIO pin is connected to an AMuxHW component, its digital input is expected to be used by the matching digital control signal on the AMuxHW component. So this GPIO pin's digital input signal should be reserved for the matching digital control signal on AMuxHW component only.
This is because it kept the hardware digital connection but automatically disabled the digital output?
The digital output probably shouldn't be disabled without also disabling the HW connection? Otherwise we have to click to enable output and then disable HW and then disable output again.
Also I don't understand the second part of the error. There is a digital control signal I could access that matches what the GPIO's digital output would be?
Solved! Go to Solution.
- Labels:
-
PSoC Creator Software
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jonathan,
I agree that the error message could have been improved in this case. The actual issue is due to AmuxHW mux implementation which prevent from connecting same input to the multiple inputs. An alternative solution to resolve your problem might be to use a comparator and AMux software mux combination.
Best Regards,
Vasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Actually even after I disable the HW connection it still produces the same error:
Cannot use pin as digital HW output when it is connected to an analog HW mux.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wait, why does it says digital OUTPUT? It's an input pin, it was never used as an output. Even if I create a new analog pin and connect it this way, it still gives the same error.
Cannot use pin Pin_1(0) as digital HW output when it is connected to an analog HW mux.
But it's not!
I don't understand this error. It seems like a bug?
PSoC3
Scanning Comparator v1.10
Pins 2.20
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Then I get errors like
Signal "Net_5163" is expected to connect to only one GPIO analog pin but instead it connects to "\Comp_1:ctComp\". Please fix the connection.
and when I try to double click on it, it says
The selected notice does not have an associated 'location'.
But it does have a location, it's the net on the schematic. When I double click it should highlight that net.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the actual problem is that I had a single GPIO connected to multiple inputs of the scanning comparator, so it internally tries to connect it to multiple inputs of the AMuxHW. The error message could be improved to clarify this?
I want to scan 3 inputs with different thresholds for each, but also use 2 different thresholds for one of them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jonathan,
I agree that the error message could have been improved in this case. The actual issue is due to AmuxHW mux implementation which prevent from connecting same input to the multiple inputs. An alternative solution to resolve your problem might be to use a comparator and AMux software mux combination.
Best Regards,
Vasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok. It would be nice if things like this could be built into the existing scanning comparator component. (Comparing a single GPIO input to multiple VDAC thresholds.)