PSoC™ 5, 3 & 1 Forum Discussions
I am sending the V_REF(1.024V) out through an analog pin buffered by an Opamp.
I am also measuring the output of the Opamp by the ADC_DelSig.
This works fine. But now I want to bypass the opamp to measure the V_REF directly. This is done because I want to know the Offset and Gain of the Opamp to do an error correction!
I want to do this on Run-Time because of temperature drift! Therefore I need an AMUX to switch between Opamp yes or not!
Is it possible to route PSoC's internal reference (1.024V) to AMUX?
There is always this error:
Voltage Reference Warning: Vref '' is connected to terminal 'AinTerm1' of 'AMux_1' but no direct hardware connection exists.
regards Willi
Show LessOne of our customers wanted to implement something unique. I thought of posting it here. He wanted to use a single firmware for two devices and on the basis of the value of an external pin, it would enumerate with either of two PIDs. Say if GPIOx is 0, it enumerates as PID 0xABCD and if GPIOx is 1, it enumerates as PID 0x1234.
There are multiple ways of implementing this:
1. Use of two set of device descriptors: This can be done by defining two sets of descriptors in the USBFS configuration window, and then start the USBFS component with either of the device descriptors. USBFS_Start(uint8 device, uint8 mode) , here device will be 0 for first device descriptors and 1 for second. This will use more memory. You will need to store the same set of descriptors, which only differ by a PID at two memory locations.
2. Define the descriptors in the Data memory (they are originally defined as constants) and change the PID in the descriptor in firmware: After the file USBFS_descr.c is created, one can copy all the descriptors in between the Custom Generated Descriptors comments and add "#define USER_SUPPLIED_DESCRIPTORS" before defining the descriptors . The keyword constant can be removed from the descriptor which we want to alter in firmware, in our case the device descriptors. For accessing the PID of the device, change USBFS_DEVICE0_DESCR[11] for LSB of PID and USBFS_DEVICE0_DESCR[12] for MSB of PID.
Stop the component and Start it again. The device this time comes up as a device with the changed PID.
Hello,
I created a USB device using the USBFS feature of the PSoC Designer, and now I want Windows to show it connected (in the device manager) with a custom name instead of the "USB Input Device" is currently listed as.
How can I do it?
Right after connecting the device, it shows the name I defined in the USBFS wizard, but after that, the name changes.
Thanks,
Lior
Show Lessevery one happy new year:
yesterday I update the PSOC Creator cause problems. my PSOC Creator Originally can use.
CYpress Update Manage cause problems. the question is that:
Log file for this session is located at: C:\Documents and Settings\Administrator\Local Settings\Temp\PSoC Creator-001.log
Show LessHi all
Is possible make analog (no dds lut) sine and saw or triangle waveform from internal blocks and few passive component ? (CY8C29466)
Many thanks help
Kamil
Show LessI want to port an application already developed that uses a high-level USB API. Converting to a Cypress 3271 based system will provide for expansion that the current embedded MCU is not capable of supporting.
I want to avoid having to code a low-level kernel based USB Driver. Show Less