PSoC™ 4 Forum Discussions

Hello, I want to use the iDAC as a current source and my load resistance varies. I understand that I am not able to output more than ~2V due to the compliance voltage. However, is there a way to know when I have reached that ceiling? Do I need to check the iDAC's output voltage with an ADC, or is there a better way to know?

Thanks!

Hi,

Trying to find this info in the datasheet(s), but can't really say for sure.

• On the CY8C4248BZI-L489, are there ANY pins that is not Hi-Z in xres vs early-boot?

I think I know the answer but need to be sure that there aren't any hard scb peripheral blocks that happen to be active low or high during boot.

Thanks David

Hello,

I was wondering if it is possible to whitelist by using a manufacturer name, rather than device address. My business has many ble mesh systems up and running in schools (security systems), but I don't want all of my nodes scannable/connectable by everyone. It would be impossible to set up a whitelist for each device address as we may have up to 300 ble nodes and 100 tablets in a single building. In this scenario, if a single tablet was added, we would have to update the whitlist for 300 nodes. Hopefully you can see the issue!!

We have custom tablets built for us, with our company name as the manufacturer name. If this is possible to filter by, it would help with security issues. Curreny, I have the system allowing for a max connection time of 4 seconds, and only encrypted data is acceptable. However, I don't want anyone tinkering with my equipment.

Thank you for your time!

Andy

Hello,

AN86526 - PSoC4 I2C Bootloader is modified to work with CY8CKIT-145-40XX.

The AN86526 documentation describes how to debug Bootloadable.

I don't know how to set the Application Type to Normal.

Please tell me how.

Best regards,

Yocchi

Hello,

We are trying it with CY8CKIT-145-40XX.

We know that there is the "Measure Cmod and Cp of PSoC 4 CapSense - KBA225808".

However, this KBA only works up to CSD V6.0 and is obsolete in V7.0.

The arguments of the API functions below are different.

[up to CSD V6.0]

   uint32 CapSense_GetSensorCapacitance (uint32  widgetId, uint32  sensorId)

[CSD V7.0]

   uint32 CapSense_GetSensorCapacitance (uint32  widgetId, uint32  sensorElement,

                                                                        CapSense_TST_MEASUREMENT_STATUS_ENUM *  measurementStatusPtr)

Therefore, We added and changed the following codes.

[Addition]

   CapSense_TST_MEASUREMENT_STATUS_ENUM measurementStatusPtr;

[Change]

    // MyI2CRegs.u8_cpValue = (uint8)CapSense_GetSensorCapacitance (i, 0);

    MyI2CRegs.u8_cpValue = (uint8)CapSense_GetSensorCapacitance (i, 0, &measurementStatusPtr);

The result of measuring Cp is as follows.

[up to CSD V6.0]

    u8_cpValues are correct.

[CSD V7.0]

     u8_cpValues are incorrect.

We have confirmed that the value of measurementStatusPtr is CapSense_TST_MEASUREMENT_SUCCESS.

Why?

Best regards,

Yocchi

We've got a number of bits of deployed hardware that use CY5677's in them, and we've recently started building a new one with a 'red' CY5677 in it, and the software doesn't recognise it:

DongleManager.TryGetCySmartDongleCommunicator

returns err with 'Message = "Not a valid CySmart dongle!"'

Is there a document with the changes needed to support this?

Mike

    Hi,

I tried programming a custom pcb with the CY8C4125AZI-S433 chip but I get an error at checksum. I was wondering if this could be due to wrong software settings or it is more probably hardware related, maybe an error in my schematic? I tried programming with the miniprog connected with the 5 pin 100-mil SWD protocol, USB powered, and the PCB also had an external 5v power supply to power the PSoC4 device. The Target Power LED on the miniprog was not ON, which I think is weird?

Here is the message I get:

Programming device 'PSoC 4100S CY8C4125AZI-S433' with file 'C:\Users\jcbsk\OneDrive\Documents\PSoC Creator\4100S\CE216892 USB-HID Trackpad01.cydsn\CortexM0p\ARM_GCC_541\Debug\CE216892 USB-HID Trackpad01.hex'.

Device ID Check

Erasing...

Programming of Flash Starting...

Failed at checksum (Expected: D05F Actual: D345

Error: dbg.M0023: There was an error while programming the device: PSoC Programmer reported error (100 - )

Thank you!

We are using the CY8CTMA1036BUI-33 touch controller and need to make some changes in the settings.

We previously used  the Touch Tuning Host Emulator 3.3.5 software for this.

The Touch Tuning Host Emulator software is not available on the Cypress website. Can anyone help us downloading this version of the software?

Thanks.

Hello,

I am looking for a controller that has at least one capsense input, ADC input and a timer block.

The plan is to implement a touch switch with a momentary delay output. The user could adjust the potentiometer to adjust the delay in the sensor output from seconds to minutes.

What controller would you suggest that has those minimum requirement? Looking for an economical solution.

Thank you in advance.

OK, so I'm trying to learn how to implement OTA in my code.  It's sloooow progress, but I'm at least moving forward.

I've played around with the BLE_OTA_FixedStack_Bootloader and BLE_OTA_FixedStack_Bootloadable example programs, and can get them to work as expected.

Next step was to write a very simple LED blinking program that I can then (hopefully) update the blink rate via OTA.  This is where I've come unstuck.  I'm clearly missing something fundamental here, but for the life of me I can't see it!

I took the relevant .c and .h files from the BLE_OTA_FixedStack_Bootloadable example project and shoe-horned those into my LED_Blinker project as per the relevant instructions.

Attached is a bundle of my workspace with the off-the-shelf BLE_OTA_FixedStack_Bootloader project, along with my LED_Blinker project all contained in the same workspace.  Note that I've not modified the BLE component from the example project at all, and I'm not actually using it in my LED_Blinker project, so have just left this as is even though I'm not using the services that are set up in the BLE component (trying not to complicate my life any more than I have to at this point)

For whatever reason, I'm getting compile errors with the sections of code that make calls to some of the functions in the ota_mandatory.c file, event those have been declared in the ota_mandatory.h file, and I've included this in my main.h header.  These compile errors are associated with calls to ConfigureSharedPins() and BootloaderSwitch(), both functions that I need to allow me to put the hardware into Bootloader mode so I can upload a new version of my LED_Blinker code OTA.

Can anyone see what I'm doing wrong here?

Cheers,

Mike