PSoC™ 5, 3 & 1 Forum Discussions

Hi.

I want to make my PSoC 5LP USB device to be recognized as WinUSB, in order to save time on Windows drivers development.

I saw the article on Microsoft's website about setting descriptor strings on 0xEE offset (didn't quite understand it...). The question is how can this be done on PSoC 5 (with the PSoC Creator)?

I saw a thread here with similar question, but for FX3...

Thanks in advance.

I spent better part of 4 hours trying to figure out why I couldn't communicate with my OLED lcd.  Worked fine on atmel, could see it under BusPirate but with a basic setup on the POSC it kept getting NACK's and freezing on MasterSendStop.  THEN I found out it was sending the wrong address?

I finally came across this line here:

I2C_1_DATA_REG = (uint8) (slaveAddress << I2C_1_SLAVE_ADDR_SHIFT);

Why is it shifting left the address?  I went ahead and change my address to shift left first and now everything is peachy.  Could there be an option in the component to turn this off and just check if the address is even?

PS - For the record I know the LSB is the read/write bit, but  I have yet to come across a device that is pre sifted liike that.

Analog DAC output voltage swing is not raising above 4V. I used voltage DAC and PGA with gain of 4. I set 1V from DAC output to PGA input I am getting 4V. When I increase the PGA input to 1.2V I am still getting 4V. Do I need to add a pull down resistor is 10k at the  analog output pin driven by PGA

Independent of current requirements, what output modes are best to protect the PSoC from a short on a digital output pin?

--

Dario

I'm confused on why the verify checksum command for flashing the bootloadable application onto flash isn't working, primarily because all the row checksums are correct. After going through the source code in creator, it seems that the bootloader computes a value for the checksum of the entire application but through the process of comparing the checksum value to what is hard coded value into flash the calculated checksum is set to 0x00. I also tried just setting the bootloader to skip the application checksum and just to end the program, however the program still goes through and runs the application checksum code which halts the operation and stops the device from resetting and allowing the bootloadable application from taking control. Attached is my C# forms app for reference.

Dear All;

Both in the device manager and in the psoc creator 4.1 I can see the that my VID is 4B4 and PID is 10.

However when I execute the following code

InitializeComponent(); CCyUSBDevice *USBDevice = new CCyUSBDevice(NULL); int devices = USBDevice->DeviceCount(); textBox1->Text = textBox1->Text + "\r\nnumber of devices : \r"; textBox1->Text = textBox1->Text + System::Convert::ToString(devices); int vID{ 0 }, pID{ 0 }; int d = 0; if (USBDevice->IsOpen()) { textBox1->Text = textBox1->Text + "\r\ndevice is open \r"; //USBDevice->Reset(); //USBDevice->Open(0); vID = USBDevice->VendorID; } textBox1->Text = textBox1->Text + "\r\nVID : \r"; textBox1->Text = textBox1->Text + System::Convert::ToString(vID);

I see that

number of devices : 1

device is open

VID : 32769

So how can I get the true VID and PID?

Thanks in advance for your help...

I feel as though I am missing something very obvious. I would really like a 32-bit up/down counter with the count "exposed" as a 32 bit bus that rolls over from 32'hFFFFFFFF -> 32'h00000000 and also from 32'h00000000 ->32'hFFFFFFFF.

The closest thing I can find is the BasicCounter Component, but there is no up-down option for this component.

I have tried coding my own in Verilog and it takes a huge amount of P-terms, so I am trying different work-arounds.

I think I can create a custom UDB component that will exhibit the correct rollover behavior, but I don't think I can "expose" the Accumulator as a digital output. Is this assumption correct?

Is there an easy option on the Counter Component that I am missing or misunderstanding?