2 of 2 people found this helpful
1) We are checking internally about the connectivity issues in Modus. Meanwhile PSoC 6 does not have output connectivity to 16 GPIOs. It supports 16 channels in the hardware. The port 10 pins which can be directly connected to the ADC through SARMUX, 2 inputs through AMUX BUS(AMUX Bus A and AMUX Bus B), output of the opamps, the die temperate input are the connections possible for the ADC. The channel maximum is set to 16 because that is the maximum channel count that the hardware supports. The way to fully utilize these 16 channels is to replicate one input on multiple channels. This is useful because each channel corresponds to a dedicated result register in the SARSEQ so replicating a channel allows multiple results to be stored before the CPU needs to awaken and handle the results. For example, consider a design with the maximum 12 sensors, of which 4 need to be sampled twice as frequently as the other eight. You could implement this entirely in hardware by assigning each of the four "fast" sensors to two channels and assigning each of the remaining eight "slow" sensors to one channel.
2) Port 9 pins are recommended to be used as ADC input after port 10 pins. Other port pins can be also connected but with the restrictions as said in errata. Please check hardware design considerations application note. Regarding the Modus Toolbox part I will update you.
3)Switching due to SPI/CLK can affect the results. So it is advisable to use different ports or not use such signals during ADC conversion in the design.
Thank you for your time and response. I understand the nature of AMUX but I guess what I am saying is that only port 10 pins seem to be an option and for complete routing of 16 channels we need 8 more pins somewhere and somehow in ModusToolbox. I am also suggesting that the language of the errata seems to imply (or I am incorrectly inferring) that the analog "stuff" is only available/connected/route-able to ports 9 and 10.
"The Programmable Analog Sub-System (PASS), including the SAR ADC, is connected to Ports 9 and 10."
Currently we have three sensors on SPI/SCB/Port 9 pins that we plan on using SPI/CLK as fast as we can. In light of the errata I am considering a redesign now and I am trying to asses where to move things around to but I cannot do that until I know where all my Analog A2D pins are as we plan on using all 16 channels in differential mode. It is a bind for us because we are actually using all 128 pins of the device as well as all SCBs. So this analog stuff really took a punch at us.
This is why I am trying to understand the errata comments. Digital switching from clocks vs switching from SAR sequencing or from SPI data lines etc...? A lot of different kinds of "switching" could exist on port 9 and port 10 and I am trying to pick the worse of all evils in this case....
Switching in Ports 9 and 10 is restricted to 1 MHz (no more than 2 outputs) with
slow slew rate setting and, in this case, the ADC error may be up to 12 counts
Please let us know about ModosuToolbox routing first chance you get and thank you again for the support.
There was an inaccuracy in the previous response. Correcting the point number 3, the switching due to SPI/CLK can affect the results. So it is advisable to use different ports or not use such signals during ADC conversion in the design.
Regarding your question of inability to use other ports for Modus, this will be resolved in the next version of Modus which is going to be released soon.