You connected the temperature to the injection channel and left open channel 0 (zero). I would suggest you to connect channel 0 to an analog input pin and read the temerature (from time to tome) from the injection channel.
Leaving open ADC- inputpins is not allowed in Creator.
I connected it to the INJ channel, routed without error. The TRM
states this is the channel used.
Single ended mode is greyed out because (from TRM) -
the global configuration register SAR_CTRL. When Vminus
is connected to P2.1..P2.7, the single-ended mode is equiv
alent to differential mode. Note that temperature sensor can
only be used in single-ended mode; it will override the
SAR_CTRL [11:9] to 0. The differential conversion is no
available for temperature sensors; the result is undefined.
Here is a sample project and you can see how the ADC is connected. Also as stated by other members you can not let one of the ADC pins float.
Thank you for the help. I understand about the floating pin, and have it connected as suggested now, I was just following the datasheet strictly, and connecting to the injection channel and nothing else. Any ideas why the datasheet has that setup?
In my application, i need to read a voltage in the range of 0-vdda and i need to read the die temperature at a very low rate.
My first issue is that the API doesnt include the ability to switch Vref since die temp requires 1.024V interna ref and the 0-VDDA signal requires Vref=VDDA. I can see, from the trm, how to change the SAR_CTRL_REG but not sure of sequence and timing considerations.
I can sometimes get valid readings but mostly not. I also need a solid answer to the dietemp.c offsetreg fix as well
Can someone plese provide details on how to switch vref at run time, proper order of calls and proper UM setup.
Might be prudent to file a CASE -
To create a technical case at Cypress -
“Create a Case”
You have to be registered on Cypress web site first.
> Any ideas why the datasheet has that setup?
This bug just bit me too. The documentation for the Die Termperature component shows a floating input pin in the datasheet and has no discussion on what to hook up to it. Searching teh innerwebs with the error text led me here.
File a CASE and point to this thread, then post back results you get.