PSoC™ 5, 3 & 1 Forum Discussions
text.format{('custom.tabs.no.results')}
When a packet of exactly 64 Bytes is transmitted using USBUART from PSoC to a PC and the result observed on a Terminal program, nothing is displayed on the Terminal program on the PC.
Reason and Workaround:
This is because of a bug in the USBUART User module code. The firmware is supposed to send a zero length packet after sending the 64 byte packet. The driver in the PC will know of the reception of the string only after receiving this zero length packet. As the firmware does not send the zero length packet, the PC driver is not aware of the reception of the data. This problem occurs only for a packet of exactly 64 characters. Packets with other lengths are received fine. The workaround for this problem is to split the 64 byte packet into two packets of any lengths, for example 32 + 32, or 62 + 2 etc.
This problem will be fixed in PSD5.0 SP6, which is expected by the end of September 2009. Show Less
In thermocouple example Thermocouple_GetVoltage() API accept temperature range maximum of 100 Degree.
But how can i modify that API for Full temperature range for any thermocouple.??
Show LessHi,
I have created a USB HID bootloader project and a bootloadable project for a PSoC5.
My test bootloadable project is just a PWM which toggles a LED. So far the bootloader works because once I load the bootloadable with the USB bootloader GUI software, I loose the USB device in the PC and the board starts toggling the LED as I configured it in the bootloadable.
The problem is that when I convert my application program to a bootloadable project and then program it to the PSoC using the bootloader software, it seems to do it but the progress bar never gets to the end. I hear the usb sound as disconnecting but then is connected again so my software never starts but instead stays in the bootloader.
I don't get any error. I configured the bootloadable with the same dependencies that I used for my first LED test bootloadable application so I don't know what the problem might be. I'm only using 26.2% of Flash and 32.8% of RAM in my application so I don't believe that could be the cause.
What could be causing this?
Thank you.
Show LessI just want to confirm that CY8C20434-12LKXI and CY8C20434-12LQXI is same, if not please tell me that it's details of specifications.
Regards.
Show LessHi,
A program I just finished makes extensive use of cos() sin() functions, which makes the whole algorithm way too slow on a PSoC 5LP at 67MHz...
I was wondering, could UDB be programmed to calculate this functions somehow via hardware... (I'm in the process of trying Taylor/Cheby polynomials, but a hardware solution would definitevitely do it!! )
THANKS!
Show LessDear Sirs, I'm trying to solve a problem on a capacitive keyboard that is quite odd.
Sometimes the capacitive keyboard is stuck and doesn't works no more; just a re-programmation of the mcu CY8C21434 solves the block of the capacitive keyboard. We obtain the block just doing some voltage dips on the main supply.
On different boards after 230V interruption the flash of the microcontroller is completely zeroed (every single byte is 0x00) and in some rare cases the flash mem is just corrupted (checksum different from hex).
No writing to flash are done in the firmware.
In the first firmware there was no watchdog and no LVD enabled moreover there was the CPU_Clock setted to work @ SYSCLK/1 but the supply voltage was 3.3V and this is not allowed (datasheet page 19/50) because the oscillator operates outside the valid operation region (yes the cpu in most cases works also outside VOR).
With a new FW with WDG, LVD enabled and SYSCLK/4 (so now working inside the VOR) all seems to work correctly and there are no blocks.
Now If i can accept a flash corruption (there is acompressor near the board) I can't explain ho can all the flash to be erased.
Can someone tell me how the mcu can be completely erased
Best regards and many thanx to anyone will help
Show LessHi everyone:
Hi,
I'm testing the communication between 2 CY3275 devkits.
This web page, http://www.cypress.com/?id=4&rID=46587, indicates that the "TX_delay" variable was to be configured. I didn't find any information on this feature. Does an Application Note exist on this subject?
Thank you
Gregory
Show Less