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 am writing a test code for sharing memory between CoreM0+ and M4 using the linker file.
I declared a bunch of 1-byte and 4-bytes variables in a "shared_v.h" file as follows:
and configured the linker files as follows:
I use UART ISR with CoreM4 to print the values and addresses of the variables Payload1 (which is an array of uint8_t) and Payload2 (which is an array of uint32_t). I use another ISR (GPIO ISR) to print the the contents of Payload1 and Payload2 through CoreM0.
With CoreM4, Payload1 and Payload2 are printed as expected.
With CoreM0, Payload1 and other uint8_t variables print as expected. However, any attempt by CoreM0 to access or print Payload2 causes CoreM0 to freeze, but CoreM4 is still responsive.
I then modified Payload2 to uint8_t instead of uint32_t, and it was printed with CoreM0.
-> Same response occurs with another uint32_t variable declared as "uint32_t Tx_packet_counter".
I was using sprintf() and then replaced it with the PDL UART_Put(), and observed the same behaviour.
Any clue what I could be doing wrong ?
Does CoreM0+ treat the uint32_t variables differently than CoreM4 ?
I attached the code for reference.
thanks a lot
MCU CY8C6347BZI-BLD54 is used as a CPU on our product and it has been produced for 50K-100K units. However, there are a few units (less than 1%) having boot-up issue after executing the process of secure boot. The failure symptoms are listed below:
1. Power up for several cycles and then finally it could boot up successfully. The cycle time of powering up can't be calculated. It's a random.
2. Always fail to boot up so it becomes a brick.
3. 1 unit succeeds to boot up intermittently.
The eFuse of these units is burned successfully if we check the eFuse bit after the unit succeed to boot up. Thus, we can't read any debug information from the SWD port. Then some signal waveforms are captured and compared on both the situation of successful and fail boot-up. The main differences are
1. The power rail behavior of MCU_VIND2, MCU_VRF, and MCU_VBUCK1
2. The activated timing of SWDIO
Please refer to the attachment for more detail waveforms. We suspect this issue results from the process of eFuse burning but we don't have solid evidence to prove it. Thus, we need your thoughts and insights on this issue. It's getting more critical now due to the increasing production volume. Thanks.Show Less
Due to lack of stock CY8C6247BZI-D34, new boards came out with CY8C6247BZI-D54 and am figuring out firmware compatibility, as by default JTAG ID is different, and cyacd2 also fails.
From the data-sheet it looks like the -D54 brings the crypto block in addition to what -D34 has, however hex file is different all over when recompiled for D54.
So I wonder do you think the same firmware can run on both CPU (and not using crypto at all) or there are more "fine details" making this impossible?
I have a use case where 2 central devices need to connect to one peripheral. I am using psoc6 as a peripheral and phone as central devices.
The problem I see is that when one central device is connected to psoc6, the other central device does not discover the peripheral. I have increased the Max number of ble connection to 2 in BT configurator, but not able to connect two devices.
I am using 'BLE_Battery_Level_FreeRTOS' example and just increased the Max number of ble connection to 2. If I connect one phone via 'CYSmart' app, cysmart app on another phone does not show the peripheral in the list.
Is there anything additional thing needed to establish connection other than increasing the Max number of BLE connections in BT configurator?
Kit used: CYCKIT-062-BLE
I want to port the following programs from CYW9M2BASE-432012BT to CY8CKIT-06S2-43012.
2) Audio_ Headset _and _Speaker,
3) Audio_Sink ( All 3 programs are present in AIROC Bluetooth BSP).
I am trying to port a PSoC 6 project from creator to modustoolbox and the last thing I need is to port to do is port our BLE OTA. The OTA is almost identical to the example project CE220960. I've added DFU into modus and changed the necessary function and variable names but I'm struggling with the linker scripts since as far as I can tell, there doesn't seem to be any examples for a BLE upgradable stack bootloader for modus. Basically what I'm looking for is any help with getting the linker files working for this port for the 3 projects (main app, launcher, stack). I put this project aside and just came back to it so apologies if I missed any information. Thank you in advance.Show Less
How do I force the WiFi and Bluetooth transmitter to output test signals, e.g. OFDM 54 Mbps 10 dBm, DH5 5 dBm, etc.?
I am using:
WICED Studio with C/C++ Luna SR 2(4.4.2)
PSoC 6 WiFi-BT Pioneer Kit
I'm working on the PSoC6 BLE Pioneer Kit CY8CKIT-062-BLE in modus toolbox and having trouble sending and receiving inputs from the keyboard. Id like to be able to type in the terminal and have it show up after hitting enter.
I have retargetIO initialized and printf working but it gets/getchar/fgets aren't loading anything to the terminal. Could my issue be the terminal I'm using is the "open a terminal" button on the modus toolbox banner? Or is there something else I'm missing.