PSoC™ 4 Forum Discussions
the code for the temperature sensor DS18B20 works fine using only the display. But when I add the BLE code, I can't get it to work, it disconnects before receiving the temperature value. I have tested the same BLE code with another max30102 sensor and it works perfectly.
Can you help me?
Thank youShow Less
Hi, in our application we use Cypress(Infinity) CY8C4128LQI-BL543 chip.
Development done with Cypress PSoC Creator 4.2 IDE.
Application should establish BT connection and send or receive some data.
All the time CPU and BLE in possible Sleep mode.
Accordance to data logs from our customers we know that sometimes program took Watch Dog reset.
Watch Dog timeout is about 20 sec.
We catch watchdog reset as following: LR : 0x00007027 PC : 0x00002536 (LR - Link Register,
PC – Program Counter Register).
During analyzing of disassembly file we find out that reset took place in the CyExitCriticalSection() that was called by ll_wait_to_exit_dsm.
ll_wait_to_exit_dsm called by: ll_exit_low_power_mode.
ll_exit_low_power_mode called by : CyBleController_ExitLowPowerMode or ll_task_handler.
CyBleController_ExitLowPowerMode called by:
CyBle_StackInit /CyBle_Shutdown/ CyBle_SoftReset/ CyBle_ExitLPM
It looks like Ble Stack can’t wake up BLE when application wants to send data.
Q: what can we do in application code to avoid such deadlock?Show Less
I have multiple I2C slaves on a network (they are all psoc4 mcu) and I would like to make a general call from the master to all the slaves using the general call address (0x00). Is it possible to accept general call address using EzI2C slave blocks? I tried finding a way to do it, but could not find any info.Show Less
I am using the CYBLE222014-01 in an application where I need to put the entire module to sleep in the lowest possible power mode. When in this mode, there is no BLE activity or MCU activity other than an accelerometer programmed to wake the module up with motion. Then the module will do a rest and start from the beginning.
The purpose of this operation is to store the device on the shelf for several weeks in this ultra sleep mode and then wake up when the device is moved.
The battery is 300mAH. Reading through all of the datasheets for this module, if both the BLESS is in deep sleep mode and the system MCU is in hibernate, the current should only be around 25uA. I am drawing 260uA and cant see why.
The only other two devices on the board are the accelerometer and an eeprom. Both of those combined draw less than 10uA.
I have confirmed by reading the BLE state prior going into system hibernation, it comes back as BLESS_DEEPSLEEP. I know the MCU is going into hibernation because the board will auto reset when it receives the interrupt from the accelerometer. Only hibernation mode will do an auto reset. I have also tried CYBLE_Stop(). It gives the same results.
I have changed the SWD pins to GPIO and that didnt change anything.
I am using a timer, I2C, ADC and PWM modules. I run the stop function for all of those before going to sleep.
The I2C pull ups are 2.2K to 3.3V supply.
Anyone have any ideas as to what is causing the extra current?
Does CYBLE-022001-00 module passed TUV certification？
IF not, what is the tool and guideline about Bluetooth fixed frequency test？
Can we use MBT for test？
I later realized that EXTCLK could not be entered into the PLL.
Eventually, a crystal oscillator will be connected to the ECO.
Regarding the current situation, is it possible to input a rectangular wave of a crystal oscillator with the same amplitude as the power supply voltage of the PSoC 4100S Plus to exco.eco_in on P0.6?
When the project has 4 buttons，There is no Rsv pin;but 5 buttons,there is;
The project contains 5buttons,How does this Rsv pin connect in PCB ?
Magsense 当使用4个buttons的时候没有RSV pin脚，我现在用5个buttons，这个RSV 在PCB 上怎么接呢？