PSoC™ 5, 3 & 1 Forum Discussions
text.format{('custom.tabs.no.results')}
I have an 050 Kit, which I only got a few months ago, and now the LP processor is out I was offered a 'free' upgrade by cypress. However the 'free' upgrade from Cypress incurs outrageous chipping costs and import duty making it almost as expensive as just buying the kit here in the UK.
Compare this to TI who ship kits and upgrades for free, with no shipping and no import duty.
It's yet another poor show from Cypress.
Show LessI tend to want to build in test (BIT) sections to my projects, allowing quick confirmation of large sections of the hardware and software.
To date - I've done this with software directives and "if" statements.
I'm wondering if there is a way to set a (hardware) complier directive to "build" internal "loopbacks".
For example - I have a section which creates via DAC output of "recorded" data, so I can check the rest of the data acquisition, processing, and communication.
The (analog) hardware output is "looped back" (via BNC cable) to the analog input - allowing "full system" checkout.
Is there any way to create a "hardware compile time" directive which "connects' (via DSI) that DAC output to the input - allowing check without physical access to the box / board?
thx
K
Show LessHello.
I built the circuit logic analyzer with "CY7C68013A-56PVXC" and now I'm trying to revive him.
The problem is that I can not install Cypress SuiteUSB that I pulled from the pages of cypress. Never met anyone with such a problem? More info on the picture. thank you
Guys,
I tried to blink those LED on PSOC, but the LEDs are so dim,
Does anyone know why ?
Here's the code :
//----------------------------------------------------------------------------
// C main line
//----------------------------------------------------------------------------
#include <m8c.h> // part specific constants and macros
#include "PSoCAPI.h" // PSoC API definitions for all User Modules
#include "delay.h"
#include "ports.h"
#include "bits.h"
void main(void)
{
unsigned int i; /* Delay var */
unsigned char j; /* LED var */
while(1)
{
P0_0(0); //Turns the LED Off.
P0_1(0);
P0_2(0);
P0_3(0);
Delay10msTimes(100);
P0_0(1); //Turns the LED On.
P0_1(1);
P0_2(1);
P0_3(1);
}
}
Thanks for reading and helping
Show LessHi,
There are several uncomitted OpAmps on some PSoC3s
The outputs seem to be connected to specific pins. Does this mean I can't route them to other pins? Does it mean I can't route them to other internal devices? E.G. ADC.
The inputs also seem to be connected to specific pins, but according to the TRM, there seems to be more options for connecting them to other buses. Is there some advantage to using those specific pins rather than other pins?
Is there any advantage to using those OpAmps rather than the ones in the SC/CT blocks?
Hugo
Show LessI'm trying to run auto turning(SmartSense), but I do not think accurate documentation about it, could you help me? I'm using a PSoC 3 and CY8CKit-001.
Thanks,
David
Show LessOne of our customer had a query regarding writing into flash. I thought reply sent to him can be put out in the forum which will be of help.
Whenever you have to make changes into the flash or write into flash following are to be done before you can call CyWriteRowData() function.
You must acquire the die temperature at least once to use Flash and EEPROM write functions.The die temperature is obtained by calling the CySetTemp() function. This function queries SPC for the die temperature and stores it in a global variable, which is used while performing Flash and EEPROM write operations.
If the Enable ECC option is disabled, you also need to allocate the buffer and pass it into the CySetFlashEEBuffer(uint8 *buffer) function. This buffer is used to store intermediate data while communicating with the SPC. buffer should be of length 256 + 32 = 288 where 256 refers to width of flash rom and 32 ECC bytes.
The description is detailed in the Flash and EEPROM section of System Refernce Guide.
Show LessI've tried downloading the psocdesigner exe file as well as PSoC programmer exe and both of those give me an error message that the file failed to extract and that it was most likely due to my memory being low or a corrupt cabinet file.
This was definitely not the case, so i tried redownloading them and got the same error message.
So then I downloaded the iso file and mounted that, and everything appeared to be working correctly until I got another error, this time 1335, which states that data1.cab could not be accessed.
Any help would be greatly appreciated, I need this software running by wednesday.
I'm running Windows 8 on parallel desktop 8 on a Macbook Pro 15 inch mid 2012 model with retina, thanks!
Show Lessis there such a thing?