PSoC™ 4 Forum Discussions
Hi I want to interface thermistor with PSOC4 . so i am using cypress example program.
i am using 10k thermistor . while using this example project i am getting some random outputs. kindly help me to resolve this. i have attached the thermistor data sheet and program.
thermistor part number:B57540G1103H000.
psoc kit used :CY8CKIT-042
thanks and regards
Rajakumar
Show LessHello,
When I directly connect Logic Low '0' to Digital Output Pin, it seems that the output pin should be always Low but it is always high voltage when I checked the output pin with Digital Multimeter.
Why is its output always high?
Best regards,
...
...
Add my project. if you find any problem, please let me know anything.
Show LessHello,
I am using a capsense Evalkit (4045) with example Code CE210291.
That Programm is adjusted for a One Button/Sense with low power consumption.
Now I'm trying to modify that programm to work with 8..9 Buttons. I have configure "Capsense" with 7 additional buttons.
Unfortunately still only one Button is detected.
I think I need to add additional code in the main.c, but I am not sure how much I need to change? Maybe it need only one line of code?
I think I have to modify follow line, but I am not sure - maybe somebody can confirm/ give some correction, advice?:
line 176
/* Configure button sensor parameters and connect it to AMUXBUS */
CapSense_CSDSetupWidgetExt(CapSense_BUTTON0_WDGT_ID, CapSense_BUTTON0_SNS0_ID);
CapSense_CSDSetupWidgetExt(CapSense_BUTTON1_WDGT_ID, CapSense_BUTTON1_SNS0_ID);
CapSense_CSDSetupWidgetExt(CapSense_BUTTON2_WDGT_ID, CapSense_BUTTON2_SNS0_ID);
CapSense_CSDSetupWidgetExt(CapSense_BUTTON3_WDGT_ID, CapSense_BUTTON3_SNS0_ID);
etc....
line 243
/* process button widget */
CapSense_ProcessWidget(CapSense_BUTTON0_WDGT_ID);
CapSense_ProcessWidget(CapSense_BUTTON1_WDGT_ID);
CapSense_ProcessWidget(CapSense_BUTTON2_WDGT_ID);
CapSense_ProcessWidget(CapSense_BUTTON3_WDGT_ID);
etc...
line 248 ... line 300
/* If button is active, reset software counter */
if (CapSense_IsWidgetActive(CapSense_BUTTON0_WDGT_ID) || CapSense_IsWidgetActive(CapSense_BUTTON1_WDGT_ID) || etc....)
{
/* Reset the software counter if any button is active. */
softCounter = RESET;
}
else
...
..
/* If button is active, switch to active mode */
if (CapSense_IsWidgetActive(CapSense_BUTTON0_WDGT_ID) || CapSense_IsWidgetActive(CapSense_BUTTON1_WDGT_ID) || etc....)
{
/* If sensor is active in slow-scan mode, skip sleep
* and perform sensor scan
*/
thank you
Show LessHello,
Our product uses PROC BLE Module (CYBLE-022001-00), and we are running some emissions test at the Test Labs,And we are using CYSAMRT to run the tests.
And Test Lab folks want the way to control the BLE module Operating frequency. I think there is a CHANNEL MAP selection command under SEND COMMANDS tab,
The 37 bit value could be used to control channels, but I am not really sure which bit controls which frequency.
Could you please confirm if I am on right path or there is other way to control the operating frequency?
Thanks,
Naga.
Hi everyone.
I have some questions. I use CYBLE-022001-00 BLE module.
A device Client
B device Server
I'm working on communication client-server. There is no problem communicating.
I use communication protocol when connecting modules.
Connect packet 0x01 0xC0 blemacid1 blemacid2 cheksum 0x04
I want to pair the modules.
Client module connect to server module with connection package.
I turn off the devices and turn them back on again, I want the client module to connect to the server module pair. I want the client module to connect to the server we have mapped to.
When we want to connect to another server, the reset communication package is sent, then the connection package is sent to connect to the new server.
How can i match modules?
Which methods should I use?
Best Regards.
Show LessI have an Upgradeable Stack OTA project, which was previously built in Creator 4.1 update 1 with latest components version. The OTA function works fine if the upgraded firmware generated from 4.1 Update1.
However, I moved to the Creator 4.2 latest version and updated the components versions today and got the issue. After I successfully upgrade the firmware and stack (combined) through OTA, the system stacked in InitializeBootloaderSRAM().
After that I use miniprog3 to reprogram the chip, the stack issue solved and I can update the firmware, built from 4.2.
I just wondering did anyone else find the same problem? Any solution or I need to keep using the same IDE version?
Show LessI'm hoping someone can help me with this CYBLE_HCI_INSTANT_PASSED_ERROR issue. There isn't a lot of documentation surrounding this for PSoC in general but from what I've pieced together with some other forum posts on various sites it seems like a core issue where a peripheral/central doesn't respond in it's allotted time-frame and may not stay connected as a result of this. People have suggested updating the version of the stack I'm on (3.30) which I have tried (to 3.50) with absolutely no change. Some iphone/android devices are able to maintain the connection without fault, some get disconnected almost immediately on every connection. This happens both using our custom app and using off the shelf ble scanner apps.
This is actually the second PSoC 4 product we've produced this year using the CY8C-4248LQI-BL573 part. On the first part we never encountered this issue. I've double checked that all the connection settings between the two products are exactly the same but have had no success.
If anyone has any experience or suggestions I'd appreciate it.
Thanks,
Nick
Show LessSee: https://sourceforge.net/projects/mecrisp/files/Cypress/
With this FORTH-pagage it is possible to test all C-applications interactively without debugger. The Kernel have integrated an interpreter and compiler.
The Compiler is extendabel in FORTH itself. The porting for the PSoC 6 is also planned.
If you would like to know more about FORTH, you will find the classic Starting-FORTH and Thinking-FORTH by Leo Brodie:
http://thinking-forth.sourceforge.net/
The Definition of ANS FORTH you can find here: http://lars.nocrew.org/dpans/dpans.htm
If you want to know more about Mecrisp-Stellaris you are right here:
https://www.forth-ev.de/filemgmt_data/files/4d2015-arm.pdf
Have fun
Klaus
Show LessI'm just trying to port the examples to PsocCreator 4.,2 and CYBLE-224110-00.
building bootloader is fine, but bootloadable will not link.
ERROR: address 0x241a0 of ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.eh_frame' will not fit in region `rom'
ERROR: address 0x241a0 of ..\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: address 0x241a0 of ...\ARM_GCC_541\Debug\BLE_OTA_FixedStack_Bootloadable01.elf section `.text' is not within region `rom'
ERROR: section .cyloadablemeta loaded at [0001ffc0,0001ffff] overlaps section .cybootloader loaded at [00000000,0001ffff]
ERROR: region `rom' overflowed by 0 bytes
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
Bootloader size is (38.4%), so I don't think I've overflowed.
I can't seem to find a memory map for the device, but don't see why the linker would make this mistake.
Workspace is attached. Thanks.
Show LessDear Community Team,
Please find attached project with SCB block for external EEPROM use internal slave I2C block.
The issue we are facing is that when we build this file with SCB block component version 1.2 project gets built correctly. But when we update that component to version 4.0 (latest) . The same program shows 13 critical error and does not get built.
Please suggest us necessary corrections/changes so that we can use latest version 4.0 of SCB block.
Best Regards,
Pavan.
Show Less