Learn how to optimise USB-C for your designs at 18 May's USB-C PD Webinar.
Click here to register.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Not applicable

I tried the cy3684 kit's example, when I test the vendor command I found a problem:


I use the large eeprom 24lc128 (128kbit or 16kbyte), I use vendor command "A9" "Out" mode to write "11 11 11 ....."(64 in total) to address started from 0x3FC0 (the xValue I put into the cy console software interface), it works.


But when I change the xValue to 0xFFFF and write another one "11" (only 1 byte), it works too after I recycled the power, the "11" content at 0xFFFF still exists!


the 24lc128 only has 0x0-0x3FFF address range, where does the xValue=0xFFFF locate at?


I am confused.

1 Reply
Not applicable

This should not happen with the vend_ax example code.


Maybe there is an older version of the code that is circling the address back to the nearest/next valid address.


Please create a support case on our website if this issue still exists.