PSoC™ 5, 3 & 1 Forum Discussions
Greetings,
I am trying to get a CY8CKIT-059 PSoC 5LP up and running on Windows 10. Unfortunately, after getting everything installed, the device will not appear as an available Debug Target in PSoC Creator 4.2, and I am getting pretty frustrated! Here are the steps I followed:
1.) Run the CY8CKIT-059 Kit Setup installer linked from the device page on cypress.com. Image of download link follows. This installs Creator 4.2, Programmer 3.27.1, and all the support files.
2.) Plug in the device (with "snap off" programmer attached) and check Device Manager. The install of drivers was successful because I see the device correctly recognized under the Ports section. See image.
3. Launch PSoC Creator and create a new project targeting this device model and using the HelloWorld_Blinky1 example app. Image attached of the device I chose when starting the project.
4.) Attempt to Program the device. Here's the trouble: The dialog where I would choose a target is blank! See image.
The Creator is making *some* kind of recognition here because when I attempt this again after UNplugging the device, message appears in that same window saying "Port Aquire Failed, No Devices Detected."
I have tried uninstalling all software, restarting Windows, reinstalling, and restarting again before plugging in the device and opening the app, nothing changes.
I have also tried manually updating the drivers to "KitProg2 USB-UART" which come with the software install. No difference.
I have also tried running the Creator Update Manager and updating everything possible, which were an update to the Programmer and a download of Creator 4.4. Neither of these updates changed the outcome 😞
Just in case it matters, here's an image of the About box in Creator:
I am running Windows 10 on a MacBook Pro with BootCamp. The machine only has USB-C ports so I am using a USB-C male to USB-A female adapter. Could this be a problem? I wouldn't think so. When I plug in the device I get solid green and orange lights on the programmer, and blinking blue light on the device.
Any advice would be greatly appreciated! Getting really frustrated over here!
Show Lesswe are currently working in the healthcare industry. We are using the CY8C5268AXI-LP047 microcontroller in our Product for the last 3 years. Now we are planning to add an OTA feature for the MCU.
Here is the detail of the system:
CY8C5268AXI-LP047 is connected with a Linux-based system through USB it received the hexadecimal commands from the Linux through USB and based on the commands it performs the serval task. We have a working code to upgrade(program) the firmware into MCU through USB with the help of PSOC(bootloader) but as our system is having a Linux operating system we are not able to flash the firmware remotely or over the air.
Please let us know if is there any way to flash the firmware code remotely/over the air on Ubuntu 16.04 LTS.
Show Less
Hello!
I'm trying to implement a few of the Self-Test functions from AN78175 into an existing project that requires testing of the SRAM at runtime.
I started with the workspace included in AN78175. After removing the custom linker script which was calling out a non-existent "micro-names.inc" include file (see here), the project compiled just fine for a CY8CKIT-050 and the SelfTests_SRAM_March() and SelfTests_SRAM_Checkerboard() functions appear to work fine and the SRAM checks out as OK.
Where I'm running into a problem is using the Self Test SRAM functions in my own project for a CY8C5667AXI-LP040. Using the example project code as a guide, I created tests for both Flash (using ECC, seems to work OK) and a SRAM test function, which is what I'm having an issue with:
bool Perform_SRAMTest (void){
uint16_t init_marchcounter = 0;
uint8_t result;
/* Initialize RAM base address for checkerboard test */
SelfTests_Init_SRAM_Test();
/* Initialize RAM base address for March test */
SelfTests_Init_March_SRAM_Test();
/***************************************/
/* Run March RAM Self-test */
/***************************************/
/* Wait for end of SRAM test */
result = SelfTests_SRAM_March();
printf("R:%d\r\n",result);
init_marchcounter++;
while((result != PASS_COMPLETE_STATUS) && (init_marchcounter != NUMBERS_OF_TEST_CYCLES))
{
result = SelfTests_SRAM_March();
printf("R:%d\r\n",result);
init_marchcounter++;
}
if(init_marchcounter == NUMBERS_OF_TEST_CYCLES)
{
/*error*/
DBG_UART_PutString("SRAM MARCH ERROR\r\n");
return true;
} else {
DBG_UART_PutString("SRAM MARCH PASS\r\n");
return false;
}
}
This should be functionally identical to the example project, but with some printf() calls to track the result of each call of SelfTests_SRAM_March(); I am finding that every call results in a result of 1. I have also tried using SelfTests_SRAM_Checkerboard(WORDS_IN_BLOCK); but that also returns error status.
So unless the SRAM in this part is bad (unlikely) I must have done something wrong, or maybe I need to adjust something for the change in part from a CY8C5868AXI-LP035 to a CY8C5667AXI-LP040? What might I be missing here?
I have made and attached a test project that exhibits the problem for CY8C5667AXI-LP040. It performs a SRAM test and a FLASH test using ECC and spits the result out via UART. There's only a few components (a few IO pins, a timer, and a status register). It at least tells me that it's probably unrelated to any of my code in the large project.
Any tips would be greatly appreciated!
Show Less
Hello,
I have been trying to configure the TImer component in the PSOC Creator library to implement the functionality mentioned in the PSOC 101: Lesson 9 Timer, but can't seem to properly configure the Timer component properly.
I know the PSOC 4 has a special TCPWM component, which is used in the tutorial.
Can anyone help me how to bring the same functionality of the Lesson 9 with PSOC 5LP and give some explaination for the same?
Looking forward to get some insight.
Regards,
Yash
Hello,
I am currently working with a PSoC5LP (precisely CY8C5888LTI-LP097) and my application is meant to power 7 LEDs with PWM supply.
I designed a Pcb on which my MCU is clipped (thanks to connector headers that are soldered on each holes of PSoC). The MCU is powered by a 5V regulator (on VDD/Ground pins) and its function is to send PWM signals to LED drivers that will supply the LEDs (powered by the pcb supply at average 350mA of current and 2.75V of tension).
Moreover, I want to monitor the PWM duty cycle of the signals delivered by the MCU thanks to .net application.
The USB communication is possible thanks to the micro-USB connector which takes place on the target board.
The fact is I suppose I can not power at the same time the PSoC with USB and also an external source.
So what are your solutions to avoid the two supplies to "kill each other" if it what will happen ?
I reflected about sth : what about if i desolder only vdd head connectors so that the external source is not seen anymore by the MCU, it would mean only the USB port Ground and the external supply ground will be in contact).
The second question is :
Is there a risk of ground loop with the current out of the leds ? I mean do the currents out of LEDs have a chance to go through the usb port ground instead of external supply ground ? Is there a risk for USB port to be damaged ?
I attach the pdf file which illustrate the pcb (supplied by 24V).
I am looking forward to hearing from you, thanks
Best regards,
Antoine
Show LessI am using interrupts in FreeRTOS to read data from USB and pass to UART (Using as software USB/UART bridge in one configuration). I need to be able to control a DTR pin based on USB_GetLineControl(), but I am not sure how to detect a change in its status via an interrupt. What interrupt will fire when this status changes?
Show Lessi am looking for PSoC5LP ICs suppliers, which are present on your suppliers list. But everywhere stock is '0'.
Can anyone let me know actual reason behind this?
when this will be over?
Show LessHi All.
I want to configure a SysTick Timer in such a way that the SysTick Timer Interrupt should invoke every 1 ms. I am using
CY8CKIT-059 PSoC® 5LP Prototyping Kit.
In PSoC 4, I did this same functionality by using the following code :
#define NO_OF_TICKS 24000u
int *tick_CM0_ENABLE = (int *) CYREG_CM0_SYST_CSR;
uint32 SysTick_value;
CY_ISR_PROTO(MySysTickHandler);
void SysTick_Timer_Enable(void); //Enabling SysTick Timer
void SysTick_Timer_Disable(void); //Disabling SysTick Timer
void SysTick_Timer_Enable(void){
*tick_CM0_ENABLE |= 1; // For Enabling the Tick Counter
/* Enable SysTick timer with desired period/number of ticks */
SysTick_Config(NO_OF_TICKS);
}
void SysTick_Timer_Disable(void){
*tick_CM0_ENABLE &= (~1); // For Disabling the Tick Counter
}
void Initialize(void)
{
CyGlobalIntEnable;
CyIntSetSysVector((SysTick_IRQn + 16u), MySysTickHandler);
SysTick_value = 0;
}
void main(void)
{
Initialize();
}
CY_ISR(MySysTickHandler)
{
SysTick_value++;
if(SysTick_value >= 1000u)
{
SysTick_value = 0;
SysTick_Timer_Disable(); // Stop after 1000 ms
}
}
I do not know why but this method does not work for PSoC5.
I am interested in performing amplitude modulation as outlined in this document:
https://www.cypress.com/file/119731/download
The message I need to modulate is sinusoidal and centered around 0V, exactly like in the above document. But from what I've gathered, PSoC I/Os cannot accept or output a negative voltage. Is this correct? If so, how could it be possible to do AM as the application note shows?
By the way, I need to do DSB-SC modulation.
Thanks
Quinn
Show Less