PSoC™ 4 Forum Discussions

hello,

In my application I need a USB bootloader. I know that USB could takes time to enumerate so I try to avoid this issu with a switch between the bootloadable and the bootloader.

I undestand that the Bootloadable_Load() in the bootloadable main.c is use to go to the bootlader.

but I do not understand the code in the bootloader example :

if((Wait_Forever_Read() == 0/*Pressed*/) || (BL_GET_RUN_TYPE == BL_START_BTLDR))

    {   

        BL_SET_RUN_TYPE(BL_START_BTLDR);

    }

    BL_Start();

-> why the bootloader have a "button test" ? the button test on the bootloadable is not enought ?

-> i do not understand the other part of the if test : (BL_GET_RUN_TYPE == BL_START_BTLDR)

and what this one does : BL_SET_RUN_TYPE(BL_START_BTLDR);  ?

Thank you for your help

I'm working on a project with the CYBLE-222014-01 module, and I'd like to use 3-wire SPI.  The SCB component doesn't support this.  The SPI Master component does support this, but not for this device. 

I would bit-bang, but I'd like to use DMA, so I would prefer a "proper" SPI solution.  Am I out of luck?

Hi,

I am working on setting up radio tests for a product with PSoC 4 BLE. I am using the DTM/HCI mode for the PSoC 4 BLE with the CMW500 Bluetooth Tester. Is there any command to control the TX power level? Is using the following API method the only means of setting the power level when using DTM/HCI mode?

CYBLE_API_RESULT_T CyBle_SetTxPowerLevel (CYBLE_BLESS_PWR_IN_DB_T *bleSsPwrLvl);

And, is the HCI_VENDOR_SET_TX_PWR cmd supported by the PSoC 4 BLE? (that is, v4.2 core spec)

Thanks,

Jimit

I have build a OTA application with upgradeble stack.

This application is starting correct up one one module. Now I have tried to load the same application on a different CYBLE 222014 module.

The second one didn't start up correctly.

If i enable the debugger it stopped at

_libc_init_array();

in cm0Start.c

    /* Invoke static objects constructors */

          __libc_init_array();

did'nt continue here:

        (void) main();

If i load a simple application to the module it start up as normal.

Any suggestion how that could be ?

Br

Esben

Hello,

The datasheet for this module only states typical values for RF Current Specifications (Page.26).

Please tell me the maximum/minimum value of each RF Current.Also, for the antenna gain on page 12, similarly, what are the maximum/minimum values ​​of Peak gain and Average Gain?

Regards,

Shimamura

您好，

CY8C4248LQI-BL573T能否PIN TO PIN 等效替换 CY8C4247LQI-BL463 ？蓝牙4.2版本是否兼容蓝牙4.1？等效替换都需要主要哪些内容？

谢谢https://cypress.force.com/partner/01t1a000001Esmj

Hi Sir，

Can CY8C4248QI-BL573T replace CY8C4247Qi-BL463 with PIN TO PIN? Is Bluetooth 4.2 compatible with Bluetooth 4.1?What are the main elements of equivalent substitution?

thank you

Hello,

I am using simple Cypress example, Day015_Bonding with updated BLE component 3.66, PSoC Creator 4.3, on Pioneer board with CY8C4248LQI-BL583 and CySmart 1.3 with dongle CY5677 (CYBL11573-56LQXI, latest hex file).

I use default settings of the dongle, and example project settings has not changed (except target device).

When I press connect, it asks to pair, I enter passkey, it pairs, and it says that it has bonded. Then I disconnect, connect, it asks to pair, when I say yes - it asks to enter the passkey again.

My understanding is that if the two are bonded, there shouldn't be any more passkey entries. But this is not happening.

I remember a few years ago on older cypress dongles bonding was working, maybe something has changed and I am not up to date?

Please see attached device and cysmart log.

Hi,

I'm working with a PSoC 4 BLE device project. After pairing two devices, the device in central role starts observing and the peripheral device starts broadcasting I'm seeing the connection drop occasionally after the central device starts observing. Here is the method that starts observing. Any help would be appreciated.

void StartObserving(void)

{

    cyBle_discoveryInfo.scanTo = CYBLE_SLOW_SCAN_TIMEOUT;

    cyBle_discoveryInfo.scanIntv = CYBLE_SLOW_SCAN_INTERVAL;

    cyBle_discoveryInfo.scanWindow = CYBLE_SLOW_SCAN_WINDOW;

    cyBle_discoveryInfo.scanType = 0;

    cyBle_scanningIntervalType = CYBLE_SCANNING_SLOW;

    CyBle_GapcStartDiscovery(&cyBle_discoveryInfo);

}