PSoC™ Creator & Designer Forum Discussions
PSoC™ Creator & Designer
After simulating the design, i go to BUILD and GENERATE PROJECT. Here a suitable device is selected and OK is pressed.An error called PROJECT ...
Show More
After simulating the design, i go to BUILD and GENERATE PROJECT. Here a suitable device is selected and OK is pressed.An error called PROJECT GENERATION ERROR is being shown.Please advice to overcome this problem.
Show Less
PSoC™ Creator & Designer
We have typed the following code to acces a port: mov a, REG[PRT2DR] OR A,0X0FF MOV REG[PRT1DR],A but the value at the por...
Show More
We have typed the following code to acces a port:
mov a, REG[PRT2DR]
OR A,0X0FF
MOV REG[PRT1DR],A
but the value at the port is not changing
please do help ASAP
Show Less
mov a, REG[PRT2DR]
OR A,0X0FF
MOV REG[PRT1DR],A
but the value at the port is not changing
please do help ASAP
Show Less
PSoC™ Creator & Designer
PSoC™ Creator & Designer
My project uses a setpoint region temperature valuator, with a point set at 30 degC When generating the application I get multiple errors a...
Show More
My project uses a setpoint region temperature valuator, with a point set at 30 degC
When generating the application I get multiple errors and the project is not generated.
In the FunctionParamDecl.h file, lines referring to the valuator look like :
#define ID_pse_valuator_1_m40,00_to_30,00_C_VALUE 0
#define ID_pse_valuator_1_30,00_to_125,00_C_VALUE 1
(etc.)
which are incorrect in C langage (inexpected commas).
This is because the implicit decimal separator used in some non-US countries, e.g. French, is a comma, not a point.
One solution is to make Windows change the implicit decimal separator when running PSoC Designer, but this is tedious and prone to forgetting.
Question : is there a workaround currently available in PSoC Designer ? Show Less
When generating the application I get multiple errors and the project is not generated.
In the FunctionParamDecl.h file, lines referring to the valuator look like :
#define ID_pse_valuator_1_m40,00_to_30,00_C_VALUE 0
#define ID_pse_valuator_1_30,00_to_125,00_C_VALUE 1
(etc.)
which are incorrect in C langage (inexpected commas).
This is because the implicit decimal separator used in some non-US countries, e.g. French, is a comma, not a point.
One solution is to make Windows change the implicit decimal separator when running PSoC Designer, but this is tedious and prone to forgetting.
Question : is there a workaround currently available in PSoC Designer ? Show Less
PSoC™ Creator & Designer
Hello, I have been out of the PSoC loop for a while, and want to get started with it again. Unfortunately I have run into a problem....
Show More
Hello,
I have been out of the PSoC loop for a while, and want to get started with it again.
Unfortunately I have run into a problem.
I have a PSoC ICE-4000 with USB-4000 usb adapter, which all worked perfectly under designer 4.2
However I now installed (on a new PC) Designer 5.0, which basically seems to refuse to work with anything else than a ICE-CUBE.
After some searching, I have found and installed the PSoC Progammer utility, which enables me to program a PSoC using the ICE-4000. This also works inside Designer 5.0, but I still am unable to select, configure and use the ICE functionality.
Does anyone know how I can get my ICE-4000 up and running under Designer 5.0 ?
Thanks in advance.
Best regards,
Robin Stevenhagen Show Less
I have been out of the PSoC loop for a while, and want to get started with it again.
Unfortunately I have run into a problem.
I have a PSoC ICE-4000 with USB-4000 usb adapter, which all worked perfectly under designer 4.2
However I now installed (on a new PC) Designer 5.0, which basically seems to refuse to work with anything else than a ICE-CUBE.
After some searching, I have found and installed the PSoC Progammer utility, which enables me to program a PSoC using the ICE-4000. This also works inside Designer 5.0, but I still am unable to select, configure and use the ICE functionality.
Does anyone know how I can get my ICE-4000 up and running under Designer 5.0 ?
Thanks in advance.
Best regards,
Robin Stevenhagen Show Less
PSoC™ Creator & Designer
There used to be a USB Host forum for support- it seems to have been nuked by Cypress. I am having extreme difficulties getting any support fo...
Show More
There used to be a USB Host forum for support- it seems to have been nuked by Cypress. I am having extreme difficulties getting any support for the CY7C6200 and 6300 Embedded USB host.
What is the deal? Why has it been nuked? Show Less
What is the deal? Why has it been nuked? Show Less
PSoC™ Creator & Designer
According to the documentation with ISSP (version 1.909), the device can be driven by a command of this form: issp cy8c29666 mycode.hex...
Show More
According to the documentation with ISSP (version 1.909), the device can be driven by a command of this form:
issp cy8c29666 mycode.hex -p -n
This does not seem to work.
The green and red lights flash briefly, then go off; the status flashes for a bit (as it does when using the ISSP from its GUI), then (after not long enough time to do the programming), the red light comes on. Programming this part from the GUI works fine.
The program appears to be returning an ERRORLEVEL of zero, supposedly signifying success.
Also, BTW, the documentation says there is a file issp.bat with the distribution - that does not appear to be the case. Show Less
issp cy8c29666 mycode.hex -p -n
This does not seem to work.
The green and red lights flash briefly, then go off; the status flashes for a bit (as it does when using the ISSP from its GUI), then (after not long enough time to do the programming), the red light comes on. Programming this part from the GUI works fine.
The program appears to be returning an ERRORLEVEL of zero, supposedly signifying success.
Also, BTW, the documentation says there is a file issp.bat with the distribution - that does not appear to be the case. Show Less
PSoC™ Creator & Designer
Hi, my app: - PSoC doing CSD as its main task - communication to master via SPIS - SPIS switched of during CSD (becaus...
Show More
Hi,
my app:
- PSoC doing CSD as its main task
- communication to master via SPIS
- SPIS switched of during CSD
(because sales man from cypress says irq from SPIS may corrupt CSD sample)
- SPIS multiple bytes in each cycle (e.g. 4 bytes)
- SPIS using software SS
- SPIS irq not enabled, polling
- PSoC slave is only sending, not receiving
- clocks from SPI master in cyclic packets (for the multiple bytes)
- PSoC-slave may start listening to SPIS in the middle of a clock packet
and may therefore not be able to send all its multiple bytes out, so using timeouts
for first byte, for other each byte, for all bytes. If timeout occures speeping to
synchronize on next clock packet.
Problem:
1. documentation says:
"On the falling edge of the Slave Select signal, the data is transferred from the Tx Buffer register to the Shift register."
Finding: SPIS_EnableSS() and SPIS_DisableSS() have no influence on when TX data buffer is transfered to shift register.
2. documentation says:
"Data to be transmitted to the SPI Master is written to the Tx Buffer register. This clears the Tx Buffer Empty status bit."
Finding: On first SPIS_SetupTxData(...) data is automaticaly/imediatetly transfered to shift register and TX_BUFFER_EMPTY flag is therefore set.
On second SPIS_SetupTxData(...) data stays in TX data buffer and TX_BUFFER_EMPTY flag is reset.
3. documentation says:
"SPIS_bReadStatus ... Side Effects: The status bits are cleared after this function is called."
Finding: SPIS_bReadStatus() has no influence on status bit TX_BUFFER_EMPTY.
I have a problem with 1. How can i controll when TX data buffer is transfered to shift register, by my selfe?
What is the difference of TX_BUFFER_EMPTY and SPI_COMPLETE flag?
documentation says:
"Choosing the second option, "TxComplete," delays the interrupt until the last bit is shifted out of the Shift register."
But shift register is automatically loaded from TX data buffer when every bit of it has been shifted out (SPI_COMPLETE will be signaled) and then also SPI_COMPLETE flag would be set, or?
How could i tell the SPIS state machine that it should ignore the data automaticaly transfered from TX data buffer and go directly to the state when shift register is empty?
I think software has too low influence on the state machine.
State machine is not documentet correctly/enough.
A state diagram would be very helpfull.
Best regards
Michael Show Less
my app:
- PSoC doing CSD as its main task
- communication to master via SPIS
- SPIS switched of during CSD
(because sales man from cypress says irq from SPIS may corrupt CSD sample)
- SPIS multiple bytes in each cycle (e.g. 4 bytes)
- SPIS using software SS
- SPIS irq not enabled, polling
- PSoC slave is only sending, not receiving
- clocks from SPI master in cyclic packets (for the multiple bytes)
- PSoC-slave may start listening to SPIS in the middle of a clock packet
and may therefore not be able to send all its multiple bytes out, so using timeouts
for first byte, for other each byte, for all bytes. If timeout occures speeping to
synchronize on next clock packet.
Problem:
1. documentation says:
"On the falling edge of the Slave Select signal, the data is transferred from the Tx Buffer register to the Shift register."
Finding: SPIS_EnableSS() and SPIS_DisableSS() have no influence on when TX data buffer is transfered to shift register.
2. documentation says:
"Data to be transmitted to the SPI Master is written to the Tx Buffer register. This clears the Tx Buffer Empty status bit."
Finding: On first SPIS_SetupTxData(...) data is automaticaly/imediatetly transfered to shift register and TX_BUFFER_EMPTY flag is therefore set.
On second SPIS_SetupTxData(...) data stays in TX data buffer and TX_BUFFER_EMPTY flag is reset.
3. documentation says:
"SPIS_bReadStatus ... Side Effects: The status bits are cleared after this function is called."
Finding: SPIS_bReadStatus() has no influence on status bit TX_BUFFER_EMPTY.
I have a problem with 1. How can i controll when TX data buffer is transfered to shift register, by my selfe?
What is the difference of TX_BUFFER_EMPTY and SPI_COMPLETE flag?
documentation says:
"Choosing the second option, "TxComplete," delays the interrupt until the last bit is shifted out of the Shift register."
But shift register is automatically loaded from TX data buffer when every bit of it has been shifted out (SPI_COMPLETE will be signaled) and then also SPI_COMPLETE flag would be set, or?
How could i tell the SPIS state machine that it should ignore the data automaticaly transfered from TX data buffer and go directly to the state when shift register is empty?
I think software has too low influence on the state machine.
State machine is not documentet correctly/enough.
A state diagram would be very helpfull.
Best regards
Michael Show Less
PSoC™ Creator & Designer
- « Previous
- Next »