USB low-full-high speed peripherals Forum Discussions

USB low-full-high speed peripherals

How to use CY7C68013 output PWM waveform, can you provide routines

Solved

How to use CY7C68013 output PWM waveform, can you provide routines？

By user_4533981

Apr 2, 2020

521

USB low-full-high speed peripherals

FX2LP Bidirectional FIFO

Solved

Hi,I'm looking into using the CY7C68013 as an interface to provide 4 channels out, 8 channels in (4 of these channels are simply the output channels l... Show More

By DaLe_778646

Mar 29, 2020

940

USB low-full-high speed peripherals

CY7C68013A and external EEPROM

Solved

你好

想請教一下，FX2要在多少時間內讀到外部的EEPROM資料，否則視為外部沒有EEPROM。

By mama_1337366

Apr 1, 2020

837

USB low-full-high speed peripherals

How can I get the real powerstate or connection status of Cy68013/Cy3014...

Solved

How can I get the real powerstate or connection status of Cy68013/Cy3014 by CyAPI?I have calls CyAPI to connect the 68013 and 3014 device. When the de... Show More

By jato_4609826

Apr 1, 2020

715

USB low-full-high speed peripherals

How to receive the whole bytes in c#

Solved

Hi,I could send/read the data with C# (cyusb.dll) and every time I read 512 bytes.But my full data's size is not a multiple of 512.The function WaitFo... Show More

By YuWa_4674726

Apr 1, 2020

730

USB low-full-high speed peripherals

Failed to perform FX3 Debug through J-Link

Solved

Hello, I am trying to perform FX3 Debug through Segger J-Link module. I followed EzUsbSuite_UG.pdf recommandations and most of the process is OK. I th... Show More

By ChRO_4339966

Mar 30, 2020

1395

USB low-full-high speed peripherals

CY7C65211A I2C Bootloader host is requesting too many bytes from PSoC5LP...

Solved

I'm running into some strange issues with trying to develop an I2C Bootloader Host.The problem I'm having looks at least on the surface similar to thi... Show More

I'm running into some strange issues with trying to develop an I2C Bootloader Host.

The problem I'm having looks at least on the surface similar to this issue I was having about a year and a half ago, so this may end up being sort of a sequel to that thread:

I2C Bootloader Error: PSoC Bootloader sending extra bytes to host?

Basically, I have an I2C Bootloader Host program built in C#, using interop services for use of cyusbserial.dll and bootl_utils.dll.

cyusbserial.dll is the one found here that fixes ACKs being too long: Reduce Delay Observed During I2C Read Operations In USB-Serial – KBA227320

bootl_utils.dll is built from the source included with PSoC Creator 4.1. The only change I made to the bootl_utils source is described my previous thread at the top of this post. (it shouldn't have an effect on the current behavior, but who knows!)

I am interfacing with a CY7C65211A USB-Serial bridge in I2C Vendor mode.

Interfacing with the bridge appears to be no issue. I can send my "Enter Bootloader" command to the I2C slave device and it enters the loader as instructed.

The problem comes when I try and actually bootload the PSoC5.

When I attempt to bootload, the first command to enter the bootloader looks completely fine:

The problem arises with the first read, where the host keeps ACKing data well past the EoP byte (0x17). The packet looks good, the host app just keeps reading for some reason:

The read then hangs on an 0xFF byte, until eventually (5 seconds later, the configured read timeout) the host finally NAKs and sends the command to exit the bootloader (0x3B):

I have confirmed that this is definitely an issue with the host application. I am able to enter the bootloader with my application, then bootload successfully using the Bootloader Host included with Creator and the I2C Bridge in the MiniProg3. I'm just at a loss as to where this is going wrong. In my ReadData() function on the host, it is entering with the correct size parameter. I confirmed via debug breakpoint that length == 16, which is correct if we include the address byte. I have no idea why it is ACKing all these extra bytes?

The error code returned from CyBtldr_Program() is the CYRET_ERR_BTLDR_MASK (0x4000) with no error code, which I suppose makes sense, as the status byte from the target is 0x00 (SUCCESS).

I have attached the Bootloader Host Application project. Maybe someone can point something out that I'm missing? It's not the cleanest code (I've been messing with it quite a bit), but it shouldn't be too hard to navigate hopefully.

Show Less

By KyTr_1955226

Feb 25, 2020

2324

USB low-full-high speed peripherals

I2C Read/Write in FX2LP -Si570

Solved

How can i using EZUSB_WriteI2C() and EZUSB_ReadI2C() functions to read/write Data from Si570 - 570FAB000433DG such as image?I am using Keil C and mod... Show More

By TrVu_4335346

Mar 11, 2020

1419

USB low-full-high speed peripherals

Read/write start-up frequency by i2c

Solved

This is datasheet of Si570:https://www.silabs.com/documents/public/data-sheets/si570.pdfI want to read start-up frequency configuration (RFREQ, HS_DIV... Show More

By TrVu_4335346

Mar 16, 2020

692

USB low-full-high speed peripherals

cyusb_linux error opening device and error opening library

Solved

My system and setup:Ubuntu 18.04, USB 2.0. Device is a Commell MPX24794S card using a Cypress CY8C24794. The cyusb_linux_1.0.4 package was install... Show More

By ChRi_4661256

Mar 12, 2020

1228