Bulk Transfer with CYConsole

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

cross mob
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

Hi

   

I'm tried to perform a simple bulk transfer with CYconsole, device CY7C68013A.

   

I did this only with the Cyconsole without any firmware download. It Is correct?

   

The message from the console is "transfer failed".

   

Any suggest?

   

Another question..

   

When i download bulkloop.hex, after the download, Cyconcole do not detect the "new"  device after renumerating; have i to change some drivers or cyusb.sys is correct?

   

Thanks for the answer.

0 Likes
13 Replies
Anonymous
Not applicable

Even though FX2LP exposes endpoints without firmware loaded it does not have code to handle the bulk transfer or proper buffer allocation so bulk transfers are bound to fail.

   

When you download bulkloop.hex please go to device manager and check if you see any USB device at all. I assume you're using bulkloop.hex without any change from the version available in the DVK.

   

Regards,

   

Anand

0 Likes
Anonymous
Not applicable

Thank aasi

   

I you attach device manager before and after.

   

.

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable
0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable

excuse me

   

now i have "other devices" Ez-USB but does not work

   

see attach Altri dispositivi=other devices: i am italian

0 Likes
Anonymous
Not applicable

excuseme the last attach is After downloading and not Before

0 Likes
Anonymous
Not applicable

Timmons,

   

What OS are you using?

   

Please right click the device with the yellow bang (not properly working device) in device manager and go to properties. This will show you a error code as to why the device is not working. Please take a screenshot of that and attach here.

   

Regards,

   

Anand

0 Likes
Anonymous
Not applicable

Hi

   

Im using Windows 7, X64 platform, i did't modify .Hex

   

If can be useful to you, i downloaded an exemple found on internet and it works very fine

   

http://www-user.tu-chemnitz.de/~heha/bastelecke/Rund%20um%20den%20PC/fx2/index.html.en

   

 

   

i attach my screen shot. The translation is:

   

 

   

Type of device: other devices

   

Productor: Unknow

   

 

   

the driver of specified device was not installed (code 28)

   

Select driver for device or information for devices

   

to find a driver for this devices click to update

   

 

   

I tried to update adding cyusb.sys but i cannot because windows show me only its proper drivers

0 Likes
lock attach
Attachments are accessible only for community members.
Anonymous
Not applicable
0 Likes
Anonymous
Not applicable

Since you are using Win 7 x64, Have you disabled driver signature enforcement as suggested in http://www.cypress.com/?id=4&rID=51049 .

   

With regards to other device, (if a inf file which does not match the VID/PID information of the device is not found in the appropriate system folder the device will show up in other devices). The bulkloop.hex with the yellow bang is most probably due to unsigned driver.

   

Regards,

   

Anand

0 Likes
Anonymous
Not applicable

Hi Anand

   

to install the device for the first enumeration (without firmware) i had alrady disabled the signature.

   

This permitted me to use the device, without firmware, correctly.

   

So when i download the firmware, the windows control signature is disabled.

   

About the inf file: i set vendor 04B4 and product 8613

   

with this settages the FX works (always stand alone).

   

bulk loop what vendor and product uses?

   

 

   

Thanks again

0 Likes
Anonymous
Not applicable

VID/PID 04B4/1004

0 Likes
Anonymous
Not applicable

Hi Anand.

   

I solved the problem by changing VID/PID and addressing the new .inf file

   

Thanks for your help

0 Likes
Anonymous
Not applicable

I appreciate these posts.  I wanted to add that if anyone is trying to use app note AN56718 for USB on PSoC testing, the Product ID (PID) in the example must also be changed to 1004 for the Bulkloop application to see it.  This app note is being re-written (currently obsoleted).  The revision should be correct.

0 Likes