PSoC™ 4 Forum Discussions

I am trying to implement a polarised resistance measurement using a PSoC4245 (CY8CKIT-049-4200)

I have successfully implemented a single channel measurement implementation.

I use an IDAC as current source, and a ADC to measure the voltage the IDAC outputs.

I am using an differential AMUX, where I connect one input to a pin, which is connected to ground. I haven't found a programmable analog ground source, therefore using an external pin to ground. The other input of the AMUX goes to the IDAC/ADC combination, and the output go to pins where I wish to measure.
(Design02.cydsn)

So far, this works fine. However, when I try to configure multiple channels, it fails,

I have tried to select the channel first, then the polarity, then the "Generate Application" function optimises out the channel selection, therefore making it impossible to select a channel.

Info: pft.M0106: AMux component (AMux_Sel) has been optimized out of the design and will not do anything.

(Design02_SEL_POL.cydsn)

I have tried to select the polarity first, then the channel, then it fails to generate the application, complaining about it is not possible to hook up the muxes like this.

Net "Net_180" is connected to analog mux "AMux_Channel_CYAMUXSIDE_A" and analog mux "AMux_Polarisation_CYAMUXSIDE_A", but it may connect to only one analog mux when it is an analog mux common connection

(Design02_POL_SEL.cydsn)

• My questions:
  Is it possible to implement something like a multi channel polarised resistance measurement using this PSoC, or any other?
  Is it possible to reach an analogue ground without the need to connect it to an external pin?

So my code compiled fine when I was using CYBLE-222014-01.   Then I realized I needed to test this on the CY8C4248LQI-BL583 since that is part of the development kit I have.  So I changed to that device, but when I did so, I got all the following errors after the build:  Mostly unable to find typedefs defined in ctypes.h file and incompatible pointer types.  I made no changes to my own code that would have resulted in this.

So I decided to go back to the CYBLE-222014-01 device, as the last known good version.  However, now I get the same errors on that version!   It shouldn't work that way. The application should be smart enough to recreate the same conditions for a successful build as long as nothing else has changed.

I am using PSOC Creator 4.1 Update 1

I am a novice at electronics as well as psoc so forgive me here... I have an application that uses a control register with 7 outputs... From what I can understand, when I call I_Control_Reg_Write(0) I turn it off, and if I call I_Control_Reg_Read() first and use the value I read from that and call I_Control_Reg_Write(value) that it will turn this Control Register back on?

I'm trying to implement USB on my PSOC4 CY8C4247AZI-L475 device. The board is powered from USB through a 3.3V regulator. And the USB data lines are directly connected to the PSOC4. I'm loading the example project USBFS_HID01 and change the processor to the one i'm using. But when i program the device the USB is not working. Device manager doesn't detect a new device. Is there something I have to set up additionaly or could it be related to windows drivers.

Kind regards,

Corné@@

Hi,

I currently have some blocking I2C that runs perfectly on PSoC 4. I was wondering if it's possible to use the I2C interrupts instead and sleep between interrupts? According to AN86233, "All other peripherals and clocks continue to run" during sleep, so I'm assuming that it would be possible to sleep between the I2C transaction steps. However, My code is blocked in CySysPmSleep(). Here's my code for the I2C read:

// buf[0]: ADDRESS + W

// buf[1]: REG ADDRESS

int I2C_Read(unsigned char *buf, int bufSize) {

    uint32_t slaveAdr = (buf[0] >> 1) & 0x7F;

    // Sending Start and register

    if ( I2C_I2CMasterSendStart(slaveAdr, 0) != I2C_I2C_MSTR_NO_ERROR ) {

        return -1;

    }

    if ( I2C_I2CMasterWriteByte(buf[1]) != I2C_I2C_MSTR_NO_ERROR ) {

        return -1;

    }

    // Sending Restart and reading data

    I2C_I2CMasterReadBuf(slaveAdr, buf, bufSize, I2C_I2C_MODE_COMPLETE_XFER | I2C_I2C_MODE_REPEAT_START);

    while( !(I2C_I2CMasterStatus() & I2C_I2C_MSTAT_RD_CMPLT) ) {

        CySysPmSleep();

    }

    return bufSize;

}

The code for a Write is pretty similar. However, it's stuck at CySysPmSleep(). Is it possible at all to sleep between I2C interrupts?

Thank you,

Fred

I have an Upgradeable Stack OTA project that's been built with PSoC Creator Ver3.3 and runs successfully.  I've already discovered that if I build it with PSoC Creator Vers4.0 without updating any components the resulting cyacd files for the Stack and Loadable sub-projects are compatible with the launcher built by Creator Ver3.3 (i.e. the OTA update works and the updated program runs OK).  I'd like to know if this will still be true if I upgrade the components (particularly the BLE stuff) to the latest under Creator Ver4.0.   I can't test this right now because there's a problem building the BLE Stack project that I haven't been able to solve.  It seems likely that this would work though since the only components in the Launcher are the Bootloader and the UART, both of which are at rev 1.50 with Creator 3.3 and 4.0.  With the original (not updated) components the elf and hex files created by the two versions of Creator are different, possibly due to changes in the toolchain or properties.

Hi

Could someone glance over my attached project. It is of I2C master taking data from BME280 environmental sensor and then transmitting the data out over BLE. I would like to view this data in Cysmart but I am unable to do so. Could someone have a look over my project please.

Regards

Hi,

I'm developing a linear slider on the CY8C4125LQI-483 with a driven shield. Just wondering if there is a maximum limit on the capacitance of the shield electrode before it stops being effective.

Thanks,

Tony