- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI,
I use USB Control Center to wite to EEPROM as shown in Figure 7-17 in CY3674/CY3684 EZ-USB Development Kit User Guide. But I found I can not write an image file larger than 512 bytes. Could you help? Thanks.
Regards
yakgg
- Labels:
-
ispn:39475:1:0
-
l1:314:1:0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
May I know if you tried to write and couldn't do so?
In the App Note, both the endpoints are configured for 512-byte FIFOs, as an example. Hence, control center requests 512 bytes. The packet size will be 512 bytes.
However, more bytes can also be sent.
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Yes. I tried to write and couldn't do so.
It has Req type: Vendor and Req Code: 0xA9. This EEProm writing request is done through EP0. I am following the example of Testing the vend_ax Example on the <CY3674_CY3684_EZ_USB_Development_Kit_User_Guide-UserManual>. It fails when I send more than 513 bytes.
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I tried this at my end and was able to successfully transfer 513 bytes.
Please let me know if you are using Cypress DVK or custom hardware.
Also, kindly share a screenshot from the control center showing the error.
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I uninstalled everything and reinstalled again for my cy3674 DVK. I run my test procedure immediately after installation.
Here is the link I got my installation
Test procedure:
step 1. Program FX2-->RAM-->load Vend_ax.hex
step 2. Toggle SW1 and SW2 to large EEPROM
step3. Configuration 1-->Control endpoint(0x00)->Transfer File-->select hid_kb.iic(one of cypress example)
I repeat the test procedure again. This time I can transfer 2304 bytes(0x900), but fail at transferring 2305 bytes(0x901).
Please help. Thanks.
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Since you are specifically selecting a file (hid_kb.iic), the bytes to transfer are automatically updated since there is pre-defined data.
Instead, if you select Transfer Data in place of Transfer File, you will be able to transfer 2305 bytes. Kindly refer to the attached screenshot of a successful transfer.
Please let me know if you have queries about this.
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You tested “In" at the "Direction" setting which is not what I asked. Could you try "Out" direction? This is the problem I encountered.
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
As per my understanding, you are able to transfer 512 bytes and 2304 bytes. Please correct if this is wrong.
However, you were not able to write 2305 bytes. Is this correct?
Please also check if you are able to write 513 bytes at your end.
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI,
As per my understanding, you are able to transfer 512 bytes and 2304 bytes. Please correct if this is wrong.
Correct
However, you were not able to write 2305 bytes. Is this correct?
Correct
Please also check if you are able to write 513 bytes at your end.
I can write 513 bytes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,
Any new findings about this bug? Thanks.
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Can you please share the I2C traces and USB logs when you are attempting to write 2305 bytes?
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
any update?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi,
Is this the log you are talking about?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
No, I'm talking about the I2C logs and the USB logs.
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI,
I looked into the DVK software package and couldn't find a place to turn the i2c and usb log. Could you give me some instruction? Thanks.
Guang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI,
This problem happened on Both cy3674 and cy3684 evaluation board. I follow the tutorial in the software package downloaded from your website. Could you point to me where is the I2c and USB logs you mentioned? I looked through your software package and couldn't find it. Thanks.
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
For I2C logs and USB logs, you need logic analyzers. Do you have it?
Regards,
Mallika
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't have logic analyzer. We newly purchased two cy3684 evaluation boards and both show same problem. Could you verify it in your side?
yakgg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems this is a bug. One of my friend in other company also observed similar problem with same setup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Apologies for the delay in the response.
Could you please try increasing the control endpoint timeout in the control center application and check?
Regards,
Mallika