PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
Team 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 Lesswhat does charinstance mean in function CyBle_EsssSetCharacteristicValue ?
I have the PSoC 4 BLE Pioneer kit and have supplemented the ADC example code with authenticated encryption BLE code. My peripheral device is called "Shelf sensor" However, I don't think I have done this correctly because after running CySmart on multiple Android devices, the "Shelf Sensor" only appears on the Nexus 9 and not the two phones. Other PSoC examples show up in CySmart on all three Android devices. So something I did makes the PSoC only appear on the Nexus 9. What could I have done to cause this problem?
I do have pairing enabled, but not the private addresses. The peripheral always has the same address. I did not start from the "Privacy" example.
Show LessHi, I am using the PRoC eval module (black PCB) and I'm trying to figure out how to change the name of the device through a mobile app. Is there a selection in Creator's schematic editor to allow for this? Or, do I need to write custom code?
Erik
Show LessHello,
I am developing application on PROC4 BLE as a central device. My side is client side.After passing address of peer device to which my device wants to connect to the Gapc_connectdevice function it gives api result :CYBLE_ERROR_INVALID_STATE which is explained as : On calling this API not in Disconnected state.
I have called Cyble_gapcstopscan() and CyBle_GapDisconnect(cyBle_connHandle.bdHandle) before calling Gapc_connectdevice () function.
But it still shows "not in Disconnected state" result and hence CYBLE_EVT_GAP_DEVICE_CONNECTED is also not generating.What is exact meaning of this api result?
What are the possible faults?
Thanks.
Show Lesshi.
i have to work on 3.3 V in my project but i gives 5 V to psoc-4. is that any configuration in psoc-4 which takes 5V and work on 3.3V ???
Show LessI'm trying to write a simple BLE application. I've done a GAP peripheral, GATT server, on pioneer kit, and I can see the results on Android application from Cypress. Of course it result as Unknown service, but I can read my data.
Now I'm trying with counterpart: the central (client). But I have problems.
Unfortunately the BLE central's examples are very few and something is wrong.
First step: a very simple check.
The main program initialize the system and the BLE's callback function and I wait for CYBLE_EVT_STACK_ON event after call of CyBle_Start .
I show the stack ON event with a green LED and a message sent via UART to a terminal, but nothing happens.
What's wrong?
I attach my project.
Thanks, Fabrizio
Show Less