I am working with the CYBLE-416045-02 chip (with CY8CPROTO-063-BLE KIT) but i am declaring a function in my .h file as the following:
uint8_t WriteCommandPacket(uint16_t cmd);
and the user can send differents commands:
#define CMD_WATER (0x3608)
#define CMD_ALCOHOL (0x3615)
#define CMD_STOP_MEASUREMENT (0x3FF9)
#define CMD_SOFT_RESET (0x0006)
#define CMD_READ_I (0x367C)
#define CMD_READ_II (0xE102)
it is why i am using the uint16_t type to send this command. But the PSoC Creattor 4.4 is telling me the following error:
masterI2C.h:68:9: error: conflicting types for 'WriteCommandPacket'
uint8_t WriteCommandPacket(uint16_t cmd);
The strage thing that i can use this type inside of the functions
Can someone help me out?
I've successfully have gotten my CY8CPROTO-062-4343W board configured as MSC device to work. I'm using the MTB project "USB_Mass_Storage_File_System".
However, every time I record another sound file (rec_xxxx.raw), the PC host doesn't see it unless I either unplug the USB connection or perform a board RESET.
Is there a event signal I can send to the PC host to request a refresh of the cached directory info the PC host has?
I realize that, in general, it is assumed with the MSC device, the host has 100% control of the storage device. It is not normally expected for the MSC device to "self-update" its contents.
Maybe there is an event packet to send the PC host to check if the directory has been corrupted?Show Less
we are working on the Smart Lock project using the Matter protocol or CHIP
I am trying to connect the PSOC 6 with matter protocol/ CHIP software loaded and the Raspberry pi wifi/zigbee interface
Matter protocol buildwithmatter.com
i followed the docs provided in the /connectedhomeip/examples/lock-app/P6/Readme.md
I executed the : zcl OnOff On 1234 1 0 ---- command
not connecting , below is the error message
Please reply me the possible solution.
chip-device-ctrl > zcl OnOff On 1234 1 0
[1637573653.279080][9954:9960] CHIP:DL: Avahi resolve failed
[1637573653.279196][9954:9960] CHIP:DIS: Node ID resolved failed with ../../src/platform/Linux/DnssdImpl.cpp:692: CHIP Error 0x000000AC: Internal error
[1637573653.279257][9954:9960] CHIP:CTL: Error resolving node id: ../../src/platform/Linux/DnssdImpl.cpp:692: CHIP Error 0x000000AC: Internal error
Failed to update node address: 172
^Z[1637574457.431856][9954:9954] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-zQ6w1Q)
[1637574457.433052][9954:9954] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1637574457.433175][9954:9954] CHIP:DL: NVS set: chip-counters/boot-reason = 5 (0x5)
[1637574457.433553][9954:9954] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-mnlqAQ)
[1637574457.434501][9954:9954] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1637574457.434610][9954:9954] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1637574457.434666][9954:9954] CHIP:DL: Inet Layer shutdown
[1637574457.434892][9954:9954] CHIP:DL: BLE shutdown
[1637574457.434957][9954:9954] CHIP:DL: System Layer shutdown
pure virtual method called
terminate called without an active exception
Aborted (core dumped)
The second stage of the programming algorithm (5.5 identify silicon), uses the subroutine CallSromApi, which is defined in the subroutine section (5.2.2, pages 32-33).
This function uses the define IPC_INTR_STRUCT_INTR_MASK_OFFSET, which I can't figure the value of.
As far as I can see, this variable is referenced only in this function. I could not find any place that says what the value of this define should be. I also looked in a PSoC project (as some of the other defines exist there as well), but could not find any reference to this variable.
All the other defines that I have encountered exist in the constants part of the document (section 5.2.1), but this define is not there.
What should be the value of this variable?
Am I missing some more documents/information that I should use in order to implement this program?
Any help will be greatly appreciated,
With Kind Regards,
I'm currently working on a project for my PSoC 6-based Cypress board, and I need a simple and quick way to set up my board as a HTTP client to download data (in a JSON format) from a server.
Are there any libraries or APIs from Cypress that implement RESTful services ?Show Less
Please add a link to the webpage for the BLE version of PSoC 64, CYB06447BZI-BLD53 that will help customers find the datasheet.
Webpage for CYB06447BZI-BLD53 @ https://www.cypress.com/part/cyb06447bzi-bld53 <-- Does NOT have a link to the datasheet.
Datasheet for CYB06447...-BLD @ https://www.cypress.com/documentation/datasheets/psoc-64-mcu-cyb06447bzi-bldx-datasheet-preliminary
Aside: There is a link to the CYB06447...-BLD datasheet from the PSoC 6 webpage under the Products tab https://www.cypress.com/products/psoc-6-microcontrollers-32-bit-arm-cortex-m4m0
I have a project with PSOC 6, recently I did a merge from my teammate and i start to get this error during compilation, I am not able to fix the same please help me solve the same.
Failed while attempting to update project 'QBL_PSOC': Could not find a part of the path 'C:\Sandbox\QBL\bitbucket\qbl_v3_firmware\QBL_PSOC.cydsn\Generated_Source\PSoC6\pdl\cmsis\include\arm_common_tables.h'..
I am aware that the generated code in the above path does not have the cmsis but I am not sure why the code is not generated even when I chose the option Build->Generate Application.
Hi everyone. I have the following issue. I just installed the new version of IDE Modus Toolbox in 2.4.
After going through the entire installation procedure on my Linux Manjaro machine.
My sample applications compile fine, but when I do Debug or Program it throws the following error and does not allow me to program my PSoC6.
Could not determine GDB version after sending: /home/user/ModusToolbox/tools_2.4/gcc/bin/arm-none-eabi-gdb --version, response:
I want to emphasize that I had previously installed the Modus Toolbox 2.3 version and it was working fine
Can you guide me to solve this problem, please?Show Less
I am developing a product using the CYBLE-416045-02 module.
When nothing needs to work, both CM4 / CM0 + CPUs are DeepSleep using Cy_SysPm_DeepSleep.
In rare cases, the MCU will restart in Cy_SysPm_DeepSleep.
I found that it restarts at the following points of EnterDeepSleepRam.
/ * The CPU enters Deep Sleep mode upon execution of WFI / WFE * /
SCB_SCR | = SCB_SCR_SLEEPDEEP_Msk;
I have modified what is in KBA229335.
The frequency of occurrence varies depending on the individual.
It does not reproduce at all in one individual, but it reproduces 100% in another individual.
Are there any other similar reports?
Also, please give me some advice on how to solve this problem.
Dear Sirs and Madams,
I'm reviewing the datasheet, TRM and application notes to review the PSoC6 hardware.
Which is recommended for handling the VDDUSB terminal when the PSoC 6 USB is not used?
1. Page 38 of PSoC6 MCU : CY8C61x6, CY8C61x7 datasheet
2. Page 4 of AN218241
The data sheet can be read as recommending applying a voltage of 1.7V to 3.6V, however the application note recommends floating.