Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Customer using CYBLE-416045-02. Files built using PSoC Creator vary in size depending on the PC on which they are created.
As a verification, I built a sample program of "BLE_Alert_Notification" and compared customers HEX, but the size was different. When I checked it with software that compares HEX files, I found data that existed in only one of them.
I've managed to build and flash the provided demo application, and the board successfully boots but then halts shortly after with "ERROR: stack overflow" — the attached screenshot shows what is happening. This happened with no WiFi credentials set, I then tried to set WiFi credentials and the error still happened.
Any help in resolving this issue would be appreciated!
I am trying to send some BLE notifications from PSoC6 MCU (peripheral) to android. Using nrfconnect ble scanner app as central. Whenever I s...
I am trying to send some BLE notifications from PSoC6 MCU (peripheral) to android. Using nrfconnect ble scanner app as central. Whenever I send a notification out, I get CY_BLE_ERROR_INVALID_PARAMETER error code on the device side for Cy_BLE_GATTS_Notification . BLE stack runs on CM0.
The characteristic size is 512 bytes but I am only sending 50 bytes in this notification. Could this be the problem?
I'm working on enabling the backup domain on the PSoC 6. I followed the instructions in this post, and found that the new code generated b...
I'm working on enabling the backup domain on the PSoC 6. I followed the instructions in this post, and found that the new code generated by PSoC Creator removed a call to Cy_SysLib_ResetBackupDomain() during initialization, as well as some code to disable and enable ILO. I then found that this function's description mentions an "ILO glitch" which can occur when the PSoC is reset due to POR/BOD/XRES while the backup voltage is supplied to the system.
When I generate code with "vBackup Source" set to VDDD, this function is called, but when I generate code with "vBackup Source" set to "Dedicated supply" it is not. However, the description of this function would seem to imply that the ILO glitch it is meant to address will only occur if the system has a dedicated backup power supply connected to VBACKUP. Could anyone shed light on why this function call is necessary when there is no backup supply? Is there any harm in removing this call if VBACKUP is shorted to VDDD?
but I need to push a button to run my application, or reset to run the bootloader.
In my application, I will have a computer connected via USB, and at startup I need to have a batch on the PC to send a command to check the firmware version, and if it's not the latest, to download the new firmware, all done automatically.
How can I do that? I'm thinking setting a variable in the "EEPROM" and then reset, the bootloader checks for that variable, and if it's not set jumps directly to the application or goes to the bootloading part of the code...
Is there an easier way? is there an example for ModusToolbox that implements an "automatic" bootloader (without pushing buttons or setting jumpers)?
With this approach I see one problem, what happens if the bootloadable app doesn't set that variable... the bootloader will never be called again.
What considerations do I need for initialization of the USB (once in bootloader and once in the application)
Discussion forum regarding PSoC® 6 - 32-bit Arm Microcontroller (MCU) Forum, discusses the 40-nm technology - best combination of ultra-low-power consumption, flexibility, security and high-performance topics.