PSoC™ 4 Forum Discussions

Hi,

I am working on CYBLE 222014-01 module mounted on my board. I am facing issue with connection establishment between CYBLE 222014-01 and CySmart  App. While searching the answers I found that capacitance trim value need to write in register CY_SYS_XTAL_BLERD_BB_XO_CAPTRIM_REG. I changed this value to 0X0000A0A0 but unfortunetly unable to establish the connection.

According to this document BLE_v3_40.pdf if we are using any EZ-BLE module then change the Input capacitance value and output capacitance value in ECO on page 12,

Kindly see the reference image .

Can anyone provide proper value for Input capacitance value and output capacitance value in ECO

There are more than a hundred ways to skin a cat and I can see that there might be many more incorrect ways to code RX-ing  bytes with the Cypress PSOC 4200 SCB UART.

I have another processor Tx-ing exactly 48 bytes to the PSOC 4200 RX pin at 115200 baud every few seconds.

I can't find any example on the web that shows how to receive multiple bytes by the Standard UART, I can find only a far too simple video that shows how to echo each byte received back to the sending terminal.

I have use of only one UART, alias UA, RX only mode.

I have started the UART in main() correctly before the main() loop.

I have a char buffer Rx[48] to hold the receive bytes and the PSOC baudrate=115200,N,8,1 as well,

I have set the UART circular buffer RX FIFO buffer size to 48 bytes.

The only active interrupts I have selected:    RX FIFO buffer full, FIFO Overflow, Frame Error

I have come up with the code below.

Will this seemingly too simple code work and also robust enough to deal with possible various RX receive errors?

//var initialization before main()

static char Rx[48];

static char j;

// in main()

    if(UA_CHECK_CAUSE_INTR(UA_INTR_RX_FULL))

     {

       for(j=0;j<48;j++)

        { Rx=UA_UartGetByte();

        }

       UA_rx_ClearInterrupt();

     }

    else if(UA_CHECK_CAUSE_INTR(UA_INTR_RX_ALL))

     {

        UA_rx_ClearInterrupt();

        UA_Stop();

        UA_Start();

     }

Hi,

first of all: CySmart 1.3 works with CY5677 without any problems...

BUT: I try to scan bt-devices with the "api_examples" from "cysmart.zip"-package.

This example contains these DDL's.
cybleautobase.dll V1.0.0.0

cyblecommonbase.dll V1.0.0.0

cybledonglecommunicator.dll V1.2.0.122

With a CY5670 (BT4.1) the scanner.exe works fine. (scan and found devices...)

With a CY5677 (BT4.2) the scanner.exe aborted with "Not a valid CySmart dongle!"

The Firmware should be up to date. (see attachments)

Is there a more "current" api-example?

Are the DDL's sufficient for this example with CY5677?
What .Net-Framework is recommended? (under Win10, VS2017)


Please help
Thomas

I'm using PWM_3CMP-v1_00 component (found into community) to control RGB leds but initial drive state of external pin is forced High (1) at power up and is not possible to change it to low voltage. GPIO datasheet says that from version 2.10 "PSoC 4 HW digital output is driven by the signal  connected to it and hence the initial drive state  parameter should not be used."

(I attached the component for RGB leds driver)

How is possible to modify the PWM_3CMP_v1_00 component to avoid leds on at power up? Or there's  another way to solve this issue?

Thank you

We are working on OTA for our current and future products.  One strategy we are considering is programming the EEprom before production with a valid Bootable image with meta data, bootloader and application.

Will an unprogrammed CYBLE-012011 automatically go to the I2C connected EEprom to boot on power up?  Can it be made to do this?

Herb

Hello everyone,

I'm currently developping a product that includes a CYBLE-202007-01.

I am close to the end of development and the question of Radio Qualification is rising up now.

I am in contact with a lab that uses a specific tool to communicate with the module through HCI.

In PSoC Creator, I turned on the HCI over UART Option to activate this functionnality.

The guy in the lab made some attempts and send commands to the module through HCI but unsuccessfully.

He told me that the module seems to accept the command but does not execute it.

He think the module is not in DTM mode and it should be for the qualification.

I searched in the PSoC Creator but did not found such an option.

Could someone help me please.

Thank you in advance.

Hello,

I am working its PSOC 3.3 creator, SP 2.

The chip I am using is CYBLE 222014-00, Proc BLE family.

In the last 2 weeks, I am trying to integrate the OTA Fixed stack bootloader (ver. 1.30) into my project.

But, unfortunately, I encouraged few problems.

First I will explain my scenario –

I would like to move from my application in the boot loader by Application command because I don’t have switch buttons on my board. So, I have added new command to support it.

While it's in the bootloader, I would like it to stay there until bootloader host command is received. But, if the bootloader didn’t receive host command so after 1 minute it's jump to the boot-loadable application.

Of course, I decided to work with the "wait for command" option.

I found few problems:

1. The time is limited to 25.5 seconds (for my application its short).

2. When I choose wait_for_command (wait 25 seconds),

The code that was actually executed was: "wait for ever " in line 1088

Instead of: wait for command in line 1095

I read in the forum (https://community.cypress.com/message/45740#45740)

To change input parameter in line 1088 to "Bootloader_WAIT_FOR_COMMAND_TIME"

But it caused me to infinite resets in the bootloader application.

3. Also, I think there is a bug with calculating the timeout and actually it is divided by 10 so the maximum time is 250 mSeconds.

When I am writing on the wizard 25000 it is converted to 250 (100mSec resolution).

In Bootloader_HostLink() the read() from the BLE is executed 10 times.

Read is done by the CyBLE_CyBtldrCommRead().

In this function, the time is converted from 10mSec to 100uSec resolution.

/* Convert from 10ms units to 100us units */

timeoutUs = ((uint32) 100u * timeOut);

See the calculation bellow:

10 (the loop) * 250 (bootloader.h) * 100 (conversion from 10mSec to 100uSec) = 250,000 = 250 mSec 

So, it's waits 250mSec instead of 25 seconds.

Did I miss something?

4. I moved to wait_for_ever option, but now, it is stuck in the boot and not jumping to the application even though there is a valid application in the flash.

I would appreciate a quick response because it is urgent.

Thanks, Avi