Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I want to test PWM with lowpass filter as a DAC, reading samples from a lookup table (sine wave). On the scope I do not see the width changing at all....
I want to test PWM with lowpass filter as a DAC, reading samples from a lookup table (sine wave). On the scope I do not see the width changing at all. What am I missing? Does the ISR have to be in sync with the PWM's clock?
int sineTableSize = 255;
uint16_t low = 10;
uint16_t high = 5000;
CyGlobalIntEnable; /* Enable global interrupts. */
(sineTableIndex==sineTableSize) ? sineTableIndex=0 : sineTableIndex++;
/*  END OF FILE */
I am trying to update the firmware in some devices, but when ever I plug in the miniprog3 into my Computer, I get the USB not recognized error in wind...
I am trying to update the firmware in some devices, but when ever I plug in the miniprog3 into my Computer, I get the USB not recognized error in windows. If I reboot, or let it sit unplugged for a while (sometimes hours) it might work, but then will fail when I go to turn on the units power., which then tells me to disconnect the USB again to fix the issue. This causes the whole cycle to begin again.
Anyone have any advice on how to get this to work?
I've gotten everything working and I can correctly program all the PSoCs memories, but the PSoC won't boot and function normally after the final reset. However, if I power-cycle the system, the PSoC boots and behaves normally.
I know I am actually programming it, because it has a firmware version number that it sends over SPI to another MCU and this does change when I program different firmware versions. It also sends other data, which is how I know if it is working.
If I use the MiniProg 3 to program, the PSoC boots as it should. Both the MiniProg and the bitbanger use the dedicated XRES pin on the TQFP package. The difference is that the MiniProg plugs into a header routed to the combined JTAG/SWD interface, while the MCU is routed to the SWD/USB pins. These pins are only used for programming, they're not used as USB or GPIO.
I have a breakout with all the relevant signals and I've scoped these to compare my implementation with what the MiniProg does. The MiniProg actually does things a bit different from what the official app note says, but there's nothing special about the final reset. It just holds down the reset for about 20ms, the release it and the PSoC boots and starts sending SPI data.
Since I've confirmed that I correctly program all the memories, I find it really surprising that the PSoC won't just come out of reset and start working. There shouldn't be any difference between using XRES and the PSoC doing a POR.
We've bought some CY8C5868AXI-LP035 with the final characters "ES" and I'm trying to program it on both methods: PSoC Creator (4.4) and PSoC Pro...
We've bought some CY8C5868AXI-LP035 with the final characters "ES" and I'm trying to program it on both methods: PSoC Creator (4.4) and PSoC Programmer 3.29.1 and I'm getting the follow errors:
PSoC Programmer: Program Finished at 15:15:26 | | Programming Terminated ERROR! ---> | The hex file does not match with the acquired device, please check the device Device set to CY8C5888AXI-LP061 at 15:15:26 | 262144 FLASH bytes Device Family set to CY8C5xxxLP at 15:15:26 | | Automatically Detected Device: CY8C5888AXI-LP061 | JtagID: 2E 13 D0 69
PSoC Creator: "this device was recognized, but PSoC Creator does not support using at this time"
The PSoC® 5LP, PSoC 2 and PSoC 1 Forum discusses - 24-bit Digital Filter Block (DFB), 24 UDBs, DMA controller and integrating AFE, digital logic with user interface ICs with an Arm Cortex-M3 CPU solutions.