PSoC™ 4 Forum Discussions
Hi,
i'm trying to use the die temperature sensor.
It seems to working ok with a reference of 1.024v.
But with a reference of 3.3volts the result is way off. I've converted the voltage as mentioned in the datasheet.
If someone could have a look and tell me where i'm going wrong, id appreciate it.
kind regards,
Damian
Show LessHi All,
I am using CYBLE 012011-00 module in my system.
basic function of the module is whatever received from PC based application to put it to UART.
I am facing issue in implementation of low power modes idea for my system is when PC will want to connect/send data to it, module should wakeup from sleep/deepsleep.
problem is i don't have any HW pins to wakeup the module and don't know can connection request from PC can wakeup the module.
i am using low power mode code from UART-BLE Peripheral example
but the problem is before connection to PC it is going to sleep i even tried putting delay but after connection module is getting disconnected and put into deepsleep and never wakesup.
attaching settings please suggest any changes need to do?
Show LessI have the CYALKIT 02. I have tried flashing the kit with the eddystone project # 50.
The device is now broadcasting the cypres.com URL, but ONLY while the beacon is still attached to the debug board.
When it is not attached to the debug board it no longer broadcasts the URL.
I have a program on my phone called "beacon monitor" that shows the device is sending SOMETHING about 1 time an hour or even less than that. however it is not showing the cypress.com URL like it does when attached, but it looks like an unnamed beacon with some random packet info, if that makes sense.
I have tried re-flashing with PSoC 4 set to "release".
I have tried attaching a 3.3 volt coin cell to the battery terminals on the beacon. Nothing so far has worked.
I see that this device uses 022001 which is the EZ-BLE I think. But I notice most people here are discussing the pioneer kit or an evaluation board. So I am having a hard time figuring out how most comments relate to my situation. Am I posting in the right place?
I really want to get this working if it is even possible.
Show LessHi
I have a project related to Adaptive Frequency Hopping (AFH). I am in basic level with the hardware and I do not know if I can have access to the
AFH pattern and update it in SYPRESS devices. I have tried nordic and TI devices but unfortunately I could not find my answer with those hardware.
Regards
Ali
Show LessHow do I download and install the CapSense Gesture component?
My CY8CKIT-046 kit does not use the CapSense Gesture component (just the CSD). The kit example rolls it's own gesture code. The 4200L in this kit should support CapSense Gesture according to the data sheet.
I need to create a 15 mm x 15 mm single finger touch pad.
I created several such touchpad/slider designs on Arduino compatible shields and would like to try them out.
Do let me know if I'm going about this wrong. I've already done this on Arduino but would ideally replace my gesture code with CapCanse Gesture and also realize a better a SNR.
Thanks,
Show LessThere seems to be limited information as to what the BLESS is doing while in DeepSleep. I can successfully put the BLESS into DeepSleep followed by placing the MCU into DeepSleep.
The BLE module is configured in the Central Role with a custom profile. It is connected to a peripheral device when I put both BLESS and MCU asleep. Immediately after putting the BLESS and MCU to sleep, it wakes right up. So I am not getting the very low microamps power level I am looking for.
The device is supposed to be asleep in very low power until a switch is pressed to wake it up. I can remove all external ISR's from the design and work only with the BLE to troubleshoot the problem and ensure nothing else is waking it up. All tests point to the BLESS is waking up the MCU as soon as it goes to sleep.
This is very frustrating and do not undertsand why or what I can do different. It appears that when it is connected to a peripheral, this occurs. If I try without a connection, then I get the expected results and the BLESS stays asleep. Is there a setting or missing code?
Here is the basic low power code which I see is used in multiple applications
/* Local variable to store the status of BLESS Hardware block */
CYBLE_LP_MODE_T sleepMode;
CYBLE_BLESS_STATE_T blessState;
uint8 intrStatus;
/* Put BLESS into Deep Sleep and check the return status */
sleepMode = CyBle_EnterLPM(CYBLE_BLESS_DEEPSLEEP);
/* Disable global interrupt to prevent changes from any other interrupt ISR */
// CyGlobalIntDisable;
intrStatus = CyEnterCriticalSection(); // disable interrupts
/* Check the Status of BLESS */
blessState = CyBle_GetBleSsState();
// isr_SW1_ClearPending();
// SW1_ClearInterrupt();
if(sleepMode == CYBLE_BLESS_DEEPSLEEP)
{
/* If the ECO has started or the BLESS can go to Deep Sleep, then place CPU
* to Deep Sleep */
if(blessState == CYBLE_BLESS_STATE_ECO_ON || blessState == CYBLE_BLESS_STATE_DEEPSLEEP)
{
CySysPmDeepSleep();
}
}
else
{
if(blessState != CYBLE_BLESS_STATE_EVENT_CLOSE)
{
/* If the BLESS hardware block cannot go to Deep Sleep and BLE Event has not
* closed yet, then place CPU to Sleep */
CySysPmSleep();
}
}
CyExitCriticalSection(intrStatus); // re-enable interrupts
Hi everyone.
I'm working on communication client-server.
I have some questions
- Attribute MTU Size in BLE datasheet
Maximum Transmission Unit size (bytes) of an attribute to be used in the design. Valid range is
from 23 to 512 bytes. This value is used to respond to an Exchange MTU request from the GATT
Client.
I don't understand exactly.
If MTU size increase 512 from 23 bytes. What effects are observed ?
In which situations should I increase or decrease mtu size?
Thanks,
Show LessI've been using a CY5677 BLE Dongle with my project based on a CY8C4248 PSoC 4 device and I just purchased a CY5672 RDK (http://www.cypress.com/documentation/development-kitsboards/cy5672-proctm-ble-remote-control-reference-design-kit-guide) which comes with a very similar BLE Dongle and I can't get CySmart1.2 to recognize the new dongle.
Looking in Windows Device Manager with the dongle plugged in I see several devices that aren't present when the dongle is removed:
1 USBUART - No driver loaded
2 HID-compliant consumer control devices with a standard Windows driver
2 HID-compliant devices with a standard Windows driver
2 USB Input Devices with a standard Windows driver
I searched the Cypress website for a driver and came up empty. I did find a few threads in the forums about similar issues but some had links to files that no longer exist or simply didn't include any viable answers.
What do I have to do to get CySmart to recognize the dongle that comes with the CY5672 RDK?
-lance
Show LessHello,
I am working with the S6SAE101A00SA1002 Solar-Powered IoT Device Kit and I am currently trying to change the advertisement rate of the CYBLE-022001-00 EZ-BLE PRoC Module to 10 minutes.
The code I am looking at is the example code "EH_Motherboard". In the main.h file there is the following define:
#define ITRVL_SENSOR_ON (10240u) /* 10.24s */
First of all, the default value 10240 should lead to an advertisment of 10.24s. I measured the blink frequency of the "User LED" on the receiver, the LED blinks every 5.8s. (I assume the LED blinks as soon as a packet arrives?)
However, even if I increase the value ITRVL_SENSOR_ON
, the LED still blinks every 5.8s. If I decrease the value, the LED blinks more often (at least...).
The problem I see is that ITRVL_SENSOR_ON
is given to the function
CYBLE_API_RESULT_T Beacon_GappStartAdvertisement(uint32_t advertisingInterval)
and is therefore casted into a uint32_t.
In the function itself the value is then casted to a uint16_t:
cyBle_discoveryModeInfo.advParam->advIntvMin = (advertisingInterval << 3) / 5;
cyBle_discoveryModeInfo.advParam->advIntvMax = cyBle_discoveryModeInfo.advParam->advIntvMin;
I think it is not possible to increase the advertisement rate to 10 minutes using this code. Any suggestions on how I get the chip to send the data every 10 minutes? 🙂
Thank you a lot in advance for your help!
Best regards,
sma
Show Less