PSoC™ 4 Forum Discussions

I'm trying to do a power budget and decide whether it's safe to write a log to flash when my rechargeable battery is going dead but still has some capacity left.

But I can't find any specs on how much more current it takes to write to flash. I'm using the CYBLE-214015 module (which contains some flavor of CY8C4248, I believe). This has 256K of flash.

Does anyone have a maximum current value for this write operation?

Thanks!

I am new to Cypress PRoC/PSoC solutions for BLE. I am trying to establish an authenticated connection between a peripheral and a central device using a pre-known static passkey. Here is what I have so far:

Peripheral side:

- configured as GATT server, GAP peripheral

- successfully starts BLE stack

- successfully starts advertising with 5 sec interval

- allows central device to connect

- waits for central device to start authentication process

- on receiving CYBLE_EVT_GAP_AUTH_REQ, calls CyBle_GappAuthReqReply() with No Bonding, key size 16, security 0x02

- on receiving CYBLE_EVT_GAP_PASSKEY_ENTRY_REQUEST, calls CyBle_GapAuthPassKeyReply() with static passkey

- waits for CYBLE_EVT_GAP_AUTH_COMPLETE or CYBLE_EVT_GAP_AUTH_FAILED

Central side:

- configured as GATT client, GAP central

- successfully starts BLE stack

- successfully starts scanning with fast scan mode

- successfully discovers target peer device

- successfully connects to target device using CyBle_GapcConnectDevice() with return 0x00

- on receiving CYBLE_EVT_GAP_DEVICE_CONNECTED, calls CyBle_GapAuthReq() with No Bonding, key size 16, security 0x02

After calling CyBle_GapAuthReq() the central device gets CYBLE_EVT_GAP_PASSKEY_DISPLAY_REQUEST the very first time, and then stays there without generating any other events from the BLE stack. And the passkey displayed is not the static passkey I'm trying to use.

Can someone shine light on the faults in the process above, for both the central and peripheral devices?

Hi everyone,

we are a company manufacturer of electronic racing components for motorsport.

One of our customer ask us to develope a product with BLE receiver for a heart rate chest.

We want to use the chip CY8C4247LQI-BL483.

We have bought CY8CKIT-042-BLE and we are using HRM collector example project; testing the demoboard with a Suunto chest we don't have any kind of problem, we receive heart rate and all the data correctly, using another chest (this chest work correctly with a specific app with an android mobile)  we have a problem and we can't understand which could be the error, the demoboard reply with some informations without heart rate.

Attached you can find the report of the demoboard.

Any help would helpful, thanks in advance.

Question in the title. Scenario being that if my application is a bad build that ends up writing to the last page in flash accidentally resulting in the metadata file at the end of flash being erased.

I had hoped that maybe I could get away with just repairing the pointer to the application, but I don't think that will work since it appears to depend on additional information. I basically use the bootloader block object for the single functionality of assisting in launching into the application.  Everything else is set to a custom interface. I have the application validation and bootloader validation turned off. What needs to be done in order for my boot loader to successfully launch a newly loaded application if the metadata file is corrupted?

Hi!

I have a project in which an SPI master sends four continuous bytes of data to an SPI slave. All four bytes are transferred in one-go without releasing the SS pin. The SS pin is released high after all four bytes are transferred.

The input from the ,master is received correctly by the slave via MOSI pin. However the MISO pin gets glued to high position randomly and corrupts the slave output data. It also appears that the MISO pin goes to high impedance after the SS pin is released. (MISO output voltage slowly ramps down to 0V from initial 5V when SS pin is released)

(Blue = MISO. Yellow = SS)

Please help