PSoC™ 4 Forum Discussions
Hi
I installed PSoC Creator 3.3 and CY8CKIT-042-BLE Kit. Rev today.(11/Jan/2016)
But not found Eddystone example in it.
Where can I get this project sample ?
regards
Moto
Show LessIs it possible to preserve the value of a variable during a reset? This is obviously not always possible, for example if the power source is removed, but for other resets like hibernate (which I use to "power on" my device), it shouldn't be impossible. If so, how is this done?
Show Less
Hello!
I'm developing my first program in PSOC 4 and wanted to know if there is some way or example to measure the decibel an example would be very useful to me and if there is any way to modify IAS or LLS to put more alarms
First of all
Thanks Regards!
Show LessHello,
I cannot change a characteristic on a 4200BLE using my iPhone 5. Here is the xcode running on my iPhone:
____________________________
let data: String = newAlarmValue.text! //this is coming from an xcode text field.
let value = data.dataUsingEncoding(NSUTF8StringEncoding)
print(value!)
print(alarmValueCharacteristic!) //the alarmValueCharateristic type on the 4200BLE is UInt8
selectedPeripheral!.writeValue(value!, forCharacteristic: alarmValueCharacteristic!, type: CBCharacteristicWriteType.WithoutResponse)
_______________________________
I print characteristic and value in my console to check I am writing to the right characteristic. I can change the value in the characteristic with the PSoC Creator interface and confirm the change has occurred in the xcode console. But I can't get the characteristic value to change over the air.
Do I need to do something in the event hanlder in main.c?
Thanks,
Pat
Show LessHello,
I experience some strange behavior.
Even if I set the Drive Mode in my code, this has no effect in the output.
I need to set the Rx to enable the pull up mode as the input can be not connected.
Here is the code snip:
BOOL xMBPortSerialInit( UCHAR ucPORT, ULONG ulBaudRate, UCHAR ucDataBits, eMBParity eParity ) { /* prevent compiler warnings because all settings are fixed in the UART Block */ (void)ucPORT; (void)ucDataBits; (void)eParity; /* Oversample fixed to 8 */ uint32 divider; divider = CYDEV_BCLK__HFCLK__HZ / 8 / ulBaudRate ; UART_clock_SetDivider(divider); ModBus_UART_Start(); ModBus_UART_SetCustomInterruptHandler(ModBus_RxTx_Isr); ModBus_UART_rx_SetDriveMode(ModBus_UART_rx_DM_RES_UP); return TRUE; }
Does anyone had this issue?
regards
Juan-Carlos
Show LessTeam Cypress,
I have "CY8C4248BZI-L489ES" parts here.
- guess that ES means engineering samples
- date-code: 1549
Can I use these for prototypes or are there any known anomalies that we should be aware of?
Show LessHi,
in our application we have designed an electronic board driven by a PSoC4 (CY8C4247LQI-BL483).
We did the software on the CYC8Kit-042 BLE, which allows programming directly from the PC through the on-board PSoC5 microcontroller.
However, is that possible to programm our own PSoC4 using this kit ? I mean, if SWDIO, SWCLK, RST, GND and VDD from the kit and from our own board are wired (and without any PSoC4 board plugged on the pioneer kit of course) does it work ? Or should we afford the MiniProg3 kit ?
Thank you in advance !
Show LessHowdy All,
After successfully following the BLE OTA Upgradable Stack example/tutorial, I now have a functioning system that can handle any of (1) App Upgrade, (2) Stack Upgrade, or (3) Both App and Stack Upgrade. The tutorials are excellent!
Along the way I've come across a curious case, which hopefully has a simple answer. If the Stack project is slightly altered (such as changing the Project Header printout by a single character) and the Application is rebuilt, attempting to push the Application OTA fails. I believe this is because the new Application is "expecting" a different Stack than the one it finds.
The Application fails in the InitializeBootlaoderSRAM() function, which for the GCC compiler is simply a wrapper for Bootloader_Start_c().
This function initializes the .BSS section of RAM. Debugging via UART printouts shows that a *good* OTA leads to a RAM initialization where the data source is 0x00000000 and the data destination is 0x00000000. A *bad* OTA leads to an initialization where the source is 0x00000000, but the destination is a random (?), much higher value.
Obviously a user should never be allowed to upgrade an Application on top of the wrong Stack, but it seems this should be an easy mitigation.
Is there a Bootloader/Bootloadable option or feature I am missing that would catch a mismatch like this? It is easy enough to store custom values in SFLASH, or even manually alter the Bootloader Metadata, but I am hopeful there is a better way.
Thanks!
Show LessI tried to measure the power consumption of CY8C4247LQI-BL483 device while it is in DeepSleep mode. I followed the instruction in "Project # 27: PSoC 4 BLE - Power Consumption Optimization" by measuring current across the jumper J15. The main() function consists of four lines of code as follows:
CySysClkIloStop();
CySysClkEcoStop();
CySysPmDeepSleep();
while(1);
The current across the jumper J15 shows around 1mA. But when I took the device out of the development kit and feed 3V directly to the device via VDDD and GND and measured the power consumption (between 3V source and VDDD), I got around 3uA as expected. I'm not sure what I did wrong when I try to measure the power consumption from the jumper J15.
Show Less