PSoC™ 5, 3 & 1 Forum Discussions
PSoC™ 5, 3 & 1
I have a system level capsense design with 10 buttons using CY8C20434. I2C hangs when inputs are configured as capsense. Using USBtoIIC window...
Show More
I have a system level capsense design with 10 buttons using CY8C20434. I2C hangs when inputs are configured as capsense. Using USBtoIIC windows utility it will sometimes list the device other times it will not. If it does it can take a minute or so to get picked up. Attempting to read button status the utility indicates that the I2C protocol is working but I may or may not read status change from a button. Sometimes the status will stick for a while before returning to zero.
I created an alternative sys level project with digital inputs on the same port pins. This works fine. It is only a problem when I am configured as capsense (CSA).
Have a previous design using CY8C20234 and 10 inputs, no problems.
The same product that has the 202434 and I2C problem has 6 other identical devices configured for two 10-segment sliders. These all work correctly.
What issue with button layout, shape, trace length, etc. might contribute to these symptoms. Seems to be only difference between my slider devices and this 10-button device.
Haven't received any response from my case for this, hope I may get something thru the forum.
thanks Show Less
I created an alternative sys level project with digital inputs on the same port pins. This works fine. It is only a problem when I am configured as capsense (CSA).
Have a previous design using CY8C20234 and 10 inputs, no problems.
The same product that has the 202434 and I2C problem has 6 other identical devices configured for two 10-segment sliders. These all work correctly.
What issue with button layout, shape, trace length, etc. might contribute to these symptoms. Seems to be only difference between my slider devices and this 10-button device.
Haven't received any response from my case for this, hope I may get something thru the forum.
thanks Show Less
PSoC™ 5, 3 & 1
I have just started using the CY3271 First Touch Starter Kit, and found that it works very well. I want to make an application for prox...
Show More
I have just started using the CY3271 First Touch Starter Kit, and found that it works very well.
I want to make an application for proximity sensing and need to see the raw data from the sensor.
The Bridge Control Panel shows both some digital and analog values, but how can I find the adress for my variables in the code?
Or: how can I define my variables so I can explore them via the Bridge Control Panel?
Thanks in advance
Poul Show Less
I want to make an application for proximity sensing and need to see the raw data from the sensor.
The Bridge Control Panel shows both some digital and analog values, but how can I find the adress for my variables in the code?
Or: how can I define my variables so I can explore them via the Bridge Control Panel?
Thanks in advance
Poul Show Less
PSoC™ 5, 3 & 1
I have been hearing rumors about cypress' giving up on CYFI.. Indeed, I couldn't get samples even through the distributor. Does that mean Cypr...
Show More
I have been hearing rumors about cypress' giving up on CYFI.. Indeed, I couldn't get samples even through the distributor. Does that mean Cypress is really planning to drop out CYFI?
Can somebody tell us about the availability of the chips for the next years?
Faysal, Show Less
Can somebody tell us about the availability of the chips for the next years?
Faysal, Show Less
PSoC™ 5, 3 & 1
Hello, I wasn't sure if this is the proper forum to post questions about problems with the CY4672 RDK I was having, if not, please let me k...
Show More
Hello,
I wasn't sure if this is the proper forum to post questions about problems with the CY4672 RDK I was having, if not, please let me know where to post and I'll do so.
Essentially, I want to try and build the firmware for the various wireless usb components in this RDK. The supplied CD came with PSoC Designer 4.4, but the installer gave me an few errors:
1 popup error message: "Error reading setup initialization file"
2nd popup error message: "1158:"
Helpful I know, but it only gets better.
The RDK release notes explicitly mentions the development was using Designer 4.4 with PD44SP1 Build 111.
Anyhow, I had no choose but to download and try Designer 5. During the project conversion process Designer 5 does to the .SOC file, it creates some backups of the boot template and various other files.
In the end, when when I try to build the keyboard firmware, the linker complains about the following:
....
Linking with linkfile
-F0x30 -g -blit:0xa9.0x1fff
-bdata:0.0xFF -bSSCParmBlk:0x00F7.0x00FF
-o"output/proc_lp_rdk_keyboard"
./obj/aes128common.o ./obj/aes128encrypt.o ./obj/battery.o ./obj/encrypt.o ./obj/encryptrand.o ./obj/flash.o ./obj/isr.o ./obj/keyboard.o ./obj/lpnonstreaming.o ./obj/lpradio.o ./obj/lpspi.o ./obj/mfgtest.o ./obj/notify.o ./obj/protocol.o ./obj/sysparam.o ./obj/timer.o ./obj/timer_a.o
C:/Cypress/WIRELE~1/CY4672~1.0/firmware/SOURCE~1/Keyboard/PROC_L~1/PROC_L~1/lib/libPSoc.a -LC:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/SMM C:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/CY7C60100/cms.a C:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/SMM/UASW/NoMAC/arith.a
ilinkm8c.exe -u ./obj/boot.o @linkfile
!E (297): area 'text' not large enough
want size 33
lo 8180 hi 8191 size 12
!E (297): area 'text' not large enough
want size 341
lo 8180 hi 8191 size 12
!E (297): area 'text' not large enough
want size 29
lo 8180 hi 8191 size 12
!E (297): area 'text' not large enough
want size 17
lo 8182 hi 8191 size 10
C:\PROGRA~1\Cypress\Common\CYPRES~3\tools\make: *** [output/proc_lp_rdk_keyboard.rom] Error 1
I have a hunch that the highlighted portion pertains to my flashsecurity.txt file, but I have no clue.
Heres what that file looks like BTW:
; 0 40 80 C0 100 140 180 1C0 200 240 280 2C0 300 340 380 3C0 (+) Base Address
W W W W W W W W W W W W W W W W ; Base Address 0
W W W W W W W W W W W W W W W W ; Base Address 400
W W W W W W W W W W W W W W W W ; Base Address 800
W W W W W W W W W W W W W W W W ; Base Address C00
; End 4K parts
W W W W W W W W W W W W W W W W ; Base Address 1000
W W W W W W W W W W W W W W W W ; Base Address 1400
W W W W W W W W W W W W W W W W ; Base Address 1800
W W W W W W W W W W W W W W W U ; Base Address 1C00
; End 8K parts
W W W W W W W W W W W W W W W W ; Base Address 2000
W W W W W W W W W W W W W W W W ; Base Address 2400
W W W W W W W W W W W W W W W W ; Base Address 2800
W W W W W W W W W W W W W W W W ; Base Address 2C00
W W W W W W W W W W W W W W W W ; Base Address 3000
W W W W W W W W W W W W W W W W ; Base Address 3400
W W W W W W W W W W W W W W W W ; Base Address 3800
W W W W W W W W W W W W U W W W ; Base Address 3C00
Any information would be much obliged if someone has run into a similar problem.
-Victor
Show Less
I wasn't sure if this is the proper forum to post questions about problems with the CY4672 RDK I was having, if not, please let me know where to post and I'll do so.
Essentially, I want to try and build the firmware for the various wireless usb components in this RDK. The supplied CD came with PSoC Designer 4.4, but the installer gave me an few errors:
1 popup error message: "Error reading setup initialization file"
2nd popup error message: "1158:"
Helpful I know, but it only gets better.
The RDK release notes explicitly mentions the development was using Designer 4.4 with PD44SP1 Build 111.
Anyhow, I had no choose but to download and try Designer 5. During the project conversion process Designer 5 does to the .SOC file, it creates some backups of the boot template and various other files.
In the end, when when I try to build the keyboard firmware, the linker complains about the following:
....
Linking with linkfile
-F0x30 -g -blit:0xa9.0x1fff
-bdata:0.0xFF -bSSCParmBlk:0x00F7.0x00FF
-o"output/proc_lp_rdk_keyboard"
./obj/aes128common.o ./obj/aes128encrypt.o ./obj/battery.o ./obj/encrypt.o ./obj/encryptrand.o ./obj/flash.o ./obj/isr.o ./obj/keyboard.o ./obj/lpnonstreaming.o ./obj/lpradio.o ./obj/lpspi.o ./obj/mfgtest.o ./obj/notify.o ./obj/protocol.o ./obj/sysparam.o ./obj/timer.o ./obj/timer_a.o
C:/Cypress/WIRELE~1/CY4672~1.0/firmware/SOURCE~1/Keyboard/PROC_L~1/PROC_L~1/lib/libPSoc.a -LC:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/SMM C:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/CY7C60100/cms.a C:/PROGRA~1/Cypress/Common/CYPRES~3/tools/lib/SMM/UASW/NoMAC/arith.a
ilinkm8c.exe -u ./obj/boot.o @linkfile
!E
want size 33
lo 8180 hi 8191 size 12
!E
want size 341
lo 8180 hi 8191 size 12
!E
want size 29
lo 8180 hi 8191 size 12
!E
want size 17
lo 8182 hi 8191 size 10
C:\PROGRA~1\Cypress\Common\CYPRES~3\tools\make: *** [output/proc_lp_rdk_keyboard.rom] Error 1
I have a hunch that the highlighted portion pertains to my flashsecurity.txt file, but I have no clue.
Heres what that file looks like BTW:
; 0 40 80 C0 100 140 180 1C0 200 240 280 2C0 300 340 380 3C0 (+) Base Address
W W W W W W W W W W W W W W W W ; Base Address 0
W W W W W W W W W W W W W W W W ; Base Address 400
W W W W W W W W W W W W W W W W ; Base Address 800
W W W W W W W W W W W W W W W W ; Base Address C00
; End 4K parts
W W W W W W W W W W W W W W W W ; Base Address 1000
W W W W W W W W W W W W W W W W ; Base Address 1400
W W W W W W W W W W W W W W W W ; Base Address 1800
W W W W W W W W W W W W W W W U ; Base Address 1C00
; End 8K parts
W W W W W W W W W W W W W W W W ; Base Address 2000
W W W W W W W W W W W W W W W W ; Base Address 2400
W W W W W W W W W W W W W W W W ; Base Address 2800
W W W W W W W W W W W W W W W W ; Base Address 2C00
W W W W W W W W W W W W W W W W ; Base Address 3000
W W W W W W W W W W W W W W W W ; Base Address 3400
W W W W W W W W W W W W W W W W ; Base Address 3800
W W W W W W W W W W W W U W W W ; Base Address 3C00
Any information would be much obliged if someone has run into a similar problem.
-Victor
Show Less
PSoC™ 5, 3 & 1
This issue affects Programmer 3.0, 3.05, 3.06, and the "beta 1" version of 3.10. The installer crashes if the "Distributed Transaction ...
Show More
This issue affects Programmer 3.0, 3.05, 3.06, and the "beta 1" version of 3.10.
The installer crashes if the "Distributed Transaction Coordinator" service is missing from the list of services in Control Panel > Administrative Tools > Services.
To fix the problem, try following these instructions:
1) Bring up a Windows Command prompt (Start > Run > cmd.exe).
2) At the command prompt, run the command:
msdtc - install
3) Try installing PSoC Programmer again.
If it still does not work, please follow these additional steps:
4) Open the Services GUI (Control Panel > Administrative Tools > Services)
5) Select "Distributed Transaction Coordinator", and click Stop.
5) At the command prompt, run the command:
msdtc -uninstall
6) At the command prompt, run the command:
msdtc - install
7) Open the Services GUI again, and verify that the services listed below have a status of "Started". If any of them are not started, select them and click Start.
COM+ Event System
COM+ System Application
Distributed Transaction Coordinator
System Event Notification
😎 Try installing PSoC Programmer again
Microsoft has documented the issue at the following link: http://support.microsoft.com/kb/891801
Modifying your registry is potentially dangerous. The Microsoft Help documentation for the registry editor program says the following - "Although Registry Editor enables you to inspect and modify the registry, normally you do not need to do so, and making incorrect changes can break your system." Show Less
The installer crashes if the "Distributed Transaction Coordinator" service is missing from the list of services in Control Panel > Administrative Tools > Services.
To fix the problem, try following these instructions:
1) Bring up a Windows Command prompt (Start > Run > cmd.exe).
2) At the command prompt, run the command:
msdtc - install
3) Try installing PSoC Programmer again.
If it still does not work, please follow these additional steps:
4) Open the Services GUI (Control Panel > Administrative Tools > Services)
5) Select "Distributed Transaction Coordinator", and click Stop.
5) At the command prompt, run the command:
msdtc -uninstall
6) At the command prompt, run the command:
msdtc - install
7) Open the Services GUI again, and verify that the services listed below have a status of "Started". If any of them are not started, select them and click Start.
COM+ Event System
COM+ System Application
Distributed Transaction Coordinator
System Event Notification
😎 Try installing PSoC Programmer again
Microsoft has documented the issue at the following link: http://support.microsoft.com/kb/891801
Modifying your registry is potentially dangerous. The Microsoft Help documentation for the registry editor program says the following - "Although Registry Editor enables you to inspect and modify the registry, normally you do not need to do so, and making incorrect changes can break your system." Show Less
PSoC™ 5, 3 & 1
Hi All, I'm trying to read from a SAR6 ADC and not getting much joy. I've got the SAR6 input from a PGA, and the PGA clocked at 32kHz. ...
Show More
Hi All,
I'm trying to read from a SAR6 ADC and not getting much joy. I've got the SAR6 input from a PGA, and the PGA clocked at 32kHz.
The PGA and SAR6 are started and set to high power mode. The PGA gain set to 1.
Then a call to SAR6_cGetSample seems to hang at;
mov reg[ASY_CR], ASY_CR_SYNCEN
From what I can gather, this waits for a rising edge on PHI1.
Is it possible that the clock PHI1 isn't running?
Any clues appreciated.
James. Show Less
I'm trying to read from a SAR6 ADC and not getting much joy. I've got the SAR6 input from a PGA, and the PGA clocked at 32kHz.
The PGA and SAR6 are started and set to high power mode. The PGA gain set to 1.
Then a call to SAR6_cGetSample seems to hang at;
mov reg[ASY_CR], ASY_CR_SYNCEN
From what I can gather, this waits for a rising edge on PHI1.
Is it possible that the clock PHI1 isn't running?
Any clues appreciated.
James. Show Less
PSoC™ 5, 3 & 1
Hello, I know that PSoC 3 has no SD card module so I want to know if there is any other way to store data on an SD card e.g. using I2C ...
Show More
Hello,
I know that PSoC 3 has no SD card module so I want to know if there is any other way to store data on an SD card e.g. using I2C or sth.
I am new to PSoC and a not-so-experienced programmer, so please respond accordingly.
Thanks. Show Less
I know that PSoC 3 has no SD card module so I want to know if there is any other way to store data on an SD card e.g. using I2C or sth.
I am new to PSoC and a not-so-experienced programmer, so please respond accordingly.
Thanks. Show Less
PSoC™ 5, 3 & 1
PSoC™ 5, 3 & 1
PSoC™ 5, 3 & 1
I used the ADC example with the pot. It worked great. When I added a mux and the 16 input channels the ADC complained about: ERROR: C:\...
Show More
I used the ADC example with the pot. It worked great. When I added a mux and the 16 input channels the ADC complained about:
ERROR: C:\DESIGN01\DESIGN01.CYDSN\GENERATED_SOURCE\PSOC3\ADC_DELSIG_2.C:70: 'CyIntSetPriority': requires ANSI-style prototype Show Less
ERROR: C:\DESIGN01\DESIGN01.CYDSN\GENERATED_SOURCE\PSOC3\ADC_DELSIG_2.C:70: 'CyIntSetPriority': requires ANSI-style prototype Show Less