PSoC™ 4 Forum Discussions
I'm just starting to experiment with the CY8CKIT-049-42xx prototyping kit (also new to Cypress PSOC in general). I'm following the documentation for the board, starting with the projects in the SCB_Bootloader workspace. I cannot get very far in the build process due to this error:
The instance 'Bootloadable', of component Bootloadable_v1_30, contains an error. Unable to locate and customize component 'Bootloadable_v1_30' used in schematic 'C:\Users\Steve\Documents\PSoC Creator\Firmware\SCB_Bootloader\Bootloadable Blinking LED.cydsn\TopDesign\TopDesign.cysch'.
The component catalog only has V1.50 of the Bootloadable/-loader, and I am unable to find any references to compatibility between versions 1.3 and 1.5. Is there some way to find out what is on the proto board? I'm assuming the Bootloadable version has to match what is on the board, but that's definitely an uninformed assumption. The bootloader component in the TopDesign.cysch (for Bootloadable Blinking LED) cannot be opened and just displays this message:
Cannot find v 1.30 of component Bootloadable
This design uses an older version of a component than is available in your dependencies. Please update the component via the Project > Update Components menu.
I tried to get both 1.30 and 1.50, but the component list continues to display only 1.50. I had installed PSOC Creator 4.1 before getting the board, so I installed the software and documentation specific to the CY8CKIT-049-42xx kit after the Creator installation. Any tips or links would be appreciated. I searched the web for quite a while and wasn't finding anything that helped. Thanks!
Show LessI am trying to code for a temp sensor ADT7311 to basically send a signal if a nearby motor is overheating and to stop that function. I know that I should be using the SPI function but I'm pretty new at coding so I dont even have an idea where to start and can't find anything on it. Any help would be appreciated.
Show LessMy device is a Central that connects to a peer.
I am using CySmart to enable notifications.
It writes all relevant characteristic descriptors to enable notification with value 0x01. And indeed all notification work fine.
But when I look at CySamrt logs, I see that the read of some of the descriptors is 0x00.
Again, I do get notifications from the ones I read zero. But why do they read zeo?
What am I missing?
Show LessHi there!
I'm trying to get the RSSI value from a 214009 PSoC4BLE.
The process works quite well when using an Eval 214009 on the Pioneer Kit.
But when using the same code on a custom board equipped with the 214009, the RSSI is always out of scale (superior to +20).
All other BLE operations will work similarly between the Eval on the Pioneer Kit, and the custom board.
PSoC Creator is v4.1
BLE block is v3.4
This just drives me nut.
Any idea?
Show LessHi ,all:
我想问一下LIN组件的内存占用大小是否可以裁剪?目前发现生成底层的代码,debug模式下会占用9.6K左右,release模式会少2k,是否有基于占用内存小的方式?谢谢!
Hello,
Does anyone have a bootloader host python script for code upload?
PSOC4 芯片,PSOC Creator 导入IAR的工程,编译后生成的hex 每行64个字节, 怎么改成16个字节, 客户的hex转bin的工具只识别16个字节长度的hex
PSoc4のBLEでPropertiesがNotifyの処理をどのように実装したらよいかがわかりません。
コミュニティーで下記の書込みを見つけました。
https://community.infineon.com/t5/PSoC-4/How-to-send-the-notification-in-psoc-4-ble/td-p/201114
しかしながら、
GitHub のDay024_Throughputサンプル プロジェクト
https://github.com/Infineon/PSoC-4-BLE/tree/master/100_Projects_in_100_Days/Day024_Throughput
書込みの中でやりとりをしているプロジェクトファイル
notificationtest.cywrk.Archive01.zip
notificationtest.cywrk.Archive02.zip
notificationtest.cywrk.Archive03.zip
のいずれもTopDesign.cyschのBLEの部分がエラーになってしまいます。
たぶん古い環境で作成されたものだからだと思います。
現在PSoC Creator4.4を使用しておりますがそちらでも見えるようになる方法はありませんでしょうか?
Show Less
MTB 3.0 with PDL release-v1.6.1:
Building the project will result in a warning message where callback pointer is not compatible.
Is it possible for the PDL to be updated so that there is no need to manually update these files?
main.c:674:50: warning: initialization of
'cy_en_syspm_status_t (*)(cy_stc_syspm_callback_params_t *, cy_en_syspm_callback_mode_t)' from incompatible pointer type
'cy_en_syspm_status_t (*)(const cy_stc_syspm_callback_params_t *, cy_en_syspm_callback_mode_t)' [-Wincompatible-pointer-types]
This warning is due to the compatibility of the callback define type of cy_en_syspm_status_t and cy_scb_i2c.c and cy_scb_i2c.h.
main.c
/* Callback declaration for I2C Deep Sleep mode */
cy_stc_syspm_callback_t i2c_deep_sleep_cb = {Cy_SCB_I2C_DeepSleepCallback, /* Callback function */
CY_SYSPM_DEEPSLEEP, /* Callback type */
0, /* Skip mode */
&i2cCallbackParams, /* Callback params */
NULL, NULL}; /* For internal usage */
/mtb_shared/mtb-pdl-cat2/release-v1.6.1/drivers/include/cy_syspm.h
typedef cy_en_syspm_status_t (*Cy_SysPmCallback) (cy_stc_syspm_callback_params_t *callbackParams, cy_en_syspm_callback_mode_t mode);
Original: /mtb_shared/mtb-pdl-cat2/release-v1.6.1/drivers/include/cy_scb_i2c.h
cy_en_syspm_status_t Cy_SCB_I2C_DeepSleepCallback(cy_stc_syspm_callback_params_t const *callbackParams, cy_en_syspm_callback_mode_t mode);
Original: /mtb_shared/mtb-pdl-cat2/release-v1.6.1/drivers/source/cy_scb_i2c.c
cy_en_syspm_status_t Cy_SCB_I2C_DeepSleepCallback(cy_stc_syspm_callback_params_t const *callbackParams, cy_en_syspm_callback_mode_t mode)
Remove the "const" from the following declaration to remove the compilation warning message.
Modified: /mtb_shared/mtb-pdl-cat2/release-v1.6.1/drivers/include/cy_scb_i2c.h
cy_en_syspm_status_t Cy_SCB_I2C_DeepSleepCallback(cy_stc_syspm_callback_params_t *callbackParams, cy_en_syspm_callback_mode_t mode);
Modified: /mtb_shared/mtb-pdl-cat2/release-v1.6.1/drivers/source/cy_scb_i2c.c
cy_en_syspm_status_t Cy_SCB_I2C_DeepSleepCallback(cy_stc_syspm_callback_params_t *callbackParams, cy_en_syspm_callback_mode_t mode)
Show Less