4 Replies Latest reply on Oct 14, 2020 4:45 AM by AlanH_86

    Thermometer share pins?

    MiMi_1891471

      In the PSOc Creator thermometer example (CE218138_BLE_Thermometer_RTOS) , they use 2 separately pins that are physically connected externally.

       

      Is this necessary? Why can't they share a THER_OUT pins?  I was able to get device configurator in MTB to do it on port 10, but is there any reason it won't work?

       

      2020-10-08 21_24_56-CE218138_BLE_Thermometer_RTOS - PSoC Creator 4.3  [C__..._CE218138_BLE_Thermomet.png

        • 1. Re: Thermometer share pins?
          VasanthR_91

          Hi Mike,

           

          This is primarily due to one limitation of SAR Sequencer(The part of SAR ADC which takes care of the sequencing and conversion formats without CPU intervention). Using the same signal for the positive half of one channel and the negative half of another channel under SAR Sequencer control is not feasible, and in general is not recommended due to the way that differential pairs are designated in the SarMux. In this case, it is possible to use the amxubus as a workaround and route both, but at the expensive of reduced performance for the negative input of channel 0 (which must route through an additional switch and traverse the high-capacitance amuxbus). The best option left is to use an additional pin for this purpose.

           

          Best Regards,
          Vasanth

          1 of 1 people found this helpful
          • 2. Re: Thermometer share pins?
            MiMi_1891471

            Thanks Vasanth. My design is remarkably low on pins, to the point way may not meet requirements unless we can save some. So even though this may not be ideal, it is a thermometer, so I'm not too worried about conversion speed.

             

            Can you clarify: "not feasible, and in general is not recommended" ? It would seem options are: 1. maybe feasible but not recommended, 2. not possible.

             

            Given I seem to have been able to route it, it seems it will operate, or am I mistaken?

            If it will operate, can you suggest how to best deal with the less than ideal routing. Should I slowing the conversion or averaging in more values compensate for the longer path and switching?

             

            This is what I have:  Thanks.

            2020-10-09 08_48_02-Analog Route Editor - Device Configurator 2.20.png

            2020-10-09 08_57_57-C__Parachute_Firmware_Parachute_PoC_COMPONENT_CUSTOM_DESIGN_MODUS_TARGET_CY8CPRO.png

             

             

             

             

             

            • 3. Re: Thermometer share pins?
              VasanthR_91

              Hi Michael,

               

              I assumed that you were using PSoC Creator seeing the first schematic image. The Analog MuxBux component in PSoC Creator  prevent the routing due to some limitation.  As using Amuxbus was the only option left which not the best option, it was not recommended.

               

              But as you are using ModusToolBox this issue is resolved. ModusToolBox 2.2 latest version allows this routing . You can use the dedicated pins for the purpose without any problem. As you are using the dedicated pins(SARBUS connections) for the purpose, there is no issue here. You have to re-use the one dedicated from different channels. The following image(not actual settings) should give more clarity. This should help you to save one GPIO pin.

               

               

               

               

               

              Best Regards,
              Vasanth

              • 4. Re: Thermometer share pins?
                AlanH_86

                This was done to increase the accuracy of the measurement.  There is an excellent application note which talks about these issues.

                https://www.cypress.com/documentation/application-notes/an66477-psoc-3-psoc-4-and-psoc-5lp-temperature-measurement