PSoC™ 4 Forum Discussions

Hello Everyone,

Is there any DALI Slave / Master stack available for PSOC4. I am keep searching for DALI Slave libraries for Cypress PSOC.

Thanks in Advance.

Regards,

Naveen

Hi,

I need to create a bootloader that allows a host interfaced through an I2C bus to make any swr updates.

I saw that the PSoC systems already provide for this eventuality, but going to read in detail the operation I seemed to understand that the downloading protocol is set in the libraries.

Unfortunately I need to implement a custom I2C protocol.

Reading the datasheets of Cypress I seemed to understand that the implementation of a custom communication is possible, but I could not find APP notes or examples to use.

The only thing I could find is an application made by a user, shared on the web in a forum, where a bootloaded application is implemented through an I2C serial eeprom.

That proposal, however, does not seem to me a good example of customization since Cypress's design philosophy is not followed as the APIs produced by the APP generator are modified directly, modules that Cypress expressly invites not to modify.

What I ask is to get directions on how to proceed, and maybe some examples from which to take inspiration.

Thanks

Working on PSOC 4 with BLE.

Putting system to sleep in Deep Sleep mode.

According to documents this should disable the ECO and IMO high frequency clocks.

BUT, system kept waking up!

My solution was to add the CySySTickStop();

and only than it appears to work.

Can you please support on this issue?

Thanks!

Hello everyone!

I have a proplem with the Touchpad detection.

My design works with a CY8C4147AZI-S475. A 11x11 Touchpad Matrix was sensed in CSD mode. The position detection works fine but the gesture with click und double click works unsure.

With the Tuner, I can see that most of time the double touch is not detected in the raw data.

All the following touches are double, but only 3 are detected as double!

This is the code:

   CyGlobalIntEnable; /* Enable global interrupts. */

        /* Place your initialization/startup code here (e.g. MyInst_Start()) */

        /* Start the components */

         #ifdef TUNER

    EZI2C_Start();

    /*

    * Set up communication and initialize data buffer to CapSense data structure

    * to use Tuner application

    */

    EZI2C_EzI2CSetBuffer1(sizeof(CapSense_dsRam),

                          sizeof(CapSense_dsRam),

                    (uint8_t *)&(CapSense_dsRam));

    /* Start CapSense Component */

    CapSense_Start();

    /* Start initial scan */

    CapSense_ScanAllWidgets();

    for(;;)

    {

        /* Do this only when a scan is done */

        if(CapSense_NOT_BUSY == CapSense_IsBusy())

        {

            /* Process all widgets */

            CapSense_ProcessAllWidgets();

            /* To sync with Tuner application */

            CapSense_RunTuner();

            /* Start next scan */

            CapSense_ScanAllWidgets();

        }

        CySysWdtClearInterrupt();

    }

    #else

Is there anyone with an idea what the mistake is?

Many thanks and best regards

Matthias

Hi all

I am trying to build a project with some timing flags(16Hz/8Hz/4Hz...etc) so that I can perform the tasks accordingly.

According to the above table, since I don't have any comparator/I2C/GPIO interrupt in my project, the only wakeup source seems to be the WDT(Configured Timer0 to 16Hz).

But WDT timer introduce some weird behavior in my project (Enter ISR twice after waking up before going into any code), so I am trying to use SysTick to generate the flags.

Then I saw something on the internet saying SysTick can wakeup from DeepSleep, so I tried it.

Guess what! it works!

But since the spec suggest otherwise, I am here to ask did I do something wrong?

(e.g. Device didn't really enter DeepSleep, so SysTick didn't really wakeup the device but just generate some ticks while running...etc?)

Been confused for a while now

Hi,

I am working with PSoC 4 BLE 4.1 Compliant Pioneer Kit, I have a I2C Slave in a BLE GAP Peripheral device.

Now, I need to implement a BLE GAP Central and GATT Client role that initiates the connection with a GAP Peripheral device and sends data to it automatically, after have gotten a notification, without the need to use external signals such as uart, I2c, button, etc.

Could someone help me with this problem?

I am new to BLE. I am willing to build remote BLE switch. With the help of BLE remote switch I want to start, stop and increase speed or decrease speed of the motor. Please advise me which kit, module and software I have to buy.

The attached workspace is the Upgradable Stack Bootloadable ported to the CYBLE-224110 EVM with some new functionality added that runs fine outside a bootloadable BLE project on the PWM page.

But when merged with bootloadable, it hard faults in CyBle_ProcessEvents(), and of course there are no clues in the fault since the call stack is not visible. The PWM page can be disabled and enabled to show the issue follows the components and supporting code.  When faulted, xpsr=0x81000003

It seems like the functionality is unrelated. I don't see why the BLE is now failing when this code is added. How can I isolate further?