I tried to change the modes of the ADC via firmware.
code:

void SetADCMode (enum sar_mode mode) {
uint32 reg_sar, reg_sample;
reg_sar = CY_GET_REG32 (CYREG_SAR_CTRL);
reg_sar & = ~ 0x00000EF0;
reg_sample = CY_GET_REG32 (CYREG_SAR_SAMPLE_CTRL);
reg_sample & = ~ 0x00000004;
switch (mode) {
case vref: //
reg_sar | = 0x000002C0;
reg_sample | = 0x00000004;
break;
case vref2:
reg_sar | = 0x00000EC0;
break;
case vdda:
reg_sar | = 0x00000270;
reg_sample | = 0x00000004;
break;
}
CY_SET_REG32 (CYREG_SAR_CTRL, reg_sar);
CY_SET_REG32 (CYREG_SAR_SAMPLE_CTRL, reg_sample);
CyDelay (5);
}

And I received false readings ADC.The project is built with the ADC configuration as shown in Figure 1.
+[0] 1A -+[1] 1A -+[2] 1A -+[3] 1B -+[4] 1A -+[5] 1B -+[6] 1A -+[7] 1A -+[8] 1A -+[9] 1A -+[10] FFFFF856 -+[11] FFFFF896 -+[12] FFFFF8BF -+[13] FFFFF8CA -+[14] FFFFF908 -+[15] FFFFF91C -+[16] FFFFF920 -+[17] FFFFF922 -+[18] FFFFF922 -+[19] FFFFF922 -+[20] FFFFFA09 -+[21] FFFFF988 -+[22] FFFFF93F -+[23] FFFFF8D7 -+[24] FFFFF8B9 -+[25] FFFFF876 -+[26] FFFFF84A -+[27] FFFFF83E -+[28] FFFFF800 -+[29] FFFFF800 -

Hello Everybody!

Creator suggests using a control file for making it fit my project into four UDBs. When using the suggested lines, nothing changes. Please see my Forum-entry "Unable to pack the design into 4 UDBs - Control file doesn't help form 3rd of August. Thanks!

A new Beta version of RSVP (Reference System Virtual Platform)  has been released for PSoC4/CY8CKIT-049 at :

https://github.com/rsvpsis/rsvpsis/tree/master/rsvpsis/brds_lib/Cypress/CY8CKIT-049

RSVP includes a fully populated project with UART, I2C, ADC, DAC, etc.
components already wired up and ready for your application.

RSVP is an easy way for new users to start with a working project
that includes the most used components along wth a IPMI compliant metadata store,
command line interface, and many other features.

best regards,

Tom
@PatternAgents

Hello,

I'm trying to measure a capacitive 'button' that changes by around 10pF between no-touch and full-contact scenarios.  I would like to be able to quantify intermediate values as well (so being able to measure 25%, 50% or 75% of full-contact by reading capacitance values between the no-touch and the touch limits).

My issue is that I would like to use the SmartSense to do this because the manual settings seem to be less reliable; however, I can't get a large enough range in SmartSense mode.  Even with the sensitivity at 10, I easily saturate the sensor when changing from no-touch to touch. 

Is there any way to lower the sensitivity (increase the range) even more in the SmartSense mode?  I would like to have the full-contact at around 80% of the max sensor value (around 200 for 8-bit sensor).

Thanks,

Dillon

I am PSoC4 beginner, so I am a little confusing about ECO. When I read PSoC4 datasheet and it explain XTAL24I can input 24-MHz crystal or external clock input. But a diagram in the datasheet show crystal is only connected at XTAL24I pin. Therefore, I suspect if I can input external clock signal into XTAL24I pin.

Please tell me whether I  can connect external clock signal into XTAL24I pin or not.

Thank you.

I designed a new pcb for the azi 48 pin tqfp version. Ordered some chips from cypress store, but they haven't shipped yet.

Has anyone already got some and would be willing to sell and ship 1 or 2  to me in knoxville tn asap?

Thanx,

Ed

Hi

I am using the proximity example with the tuning tool. That worked ok until I tried to use the debugger as well. The software did not jump to the required breakpoints as the code was not compiled in by default. After running the debugger, I could not program the board again as it is not seen in the list of devices.

I rebooted the pc and reloaded the PSoC Creator software. The Pioneer board is seen and is in the devices list of the pc as the Kitprog device but the software does not see the device. So I cannot program it anymore. 

Any suggestions please?

P.S. I am very new to all of this 😞

Regards

Marius