Hi, 

 I am working hard for the communication between Microblaze and Cy7c67300(USB Host), and I have problems about the application code of Microblaze. Firstly, I want to pass data to cy7c67300, and then pass the data to Microblaze through HPI. I have succeed in the usb keyboadrd demo which Xilinx provided, and now the Host is PC and FPGA, the usb slave is cy7c67300.

What make me confused is the de2 firmware which is passed from Microblaze to cy7c67300 is not work! Because the usb driver is Cypress OTG-Host Design Example 2 Driver when the de2 firmware is downloaded directly to EEPROM of cy7c67300. And now, the usb driver is still Cypress USB EZ-OTG  Device VID=04B4, PID=7200 and it is not changed after download through HPI mode. I don' know why, please help me!

Thanks!    

 Hi,

  Are you downloading to EEPROM via HPI interface??? It's not possible to access EEPROM via HPI. Please go through http://www.cypress.com/?docID=27641 table.3 for more information. 

Thanks

Prajith

 Hi,

I downloaded the de2 firmware to the RAM of cy7c67300 through HPI. 

Thanks

Hi,

 Is there any another way for downloading the de2 firmware on the HPI mode? Please help me!

Thanks

 Sorry, I didnt understand your question. Please explain in detail. What is your requirement?. Why do you want to download firmware in another way?? Please explain your purpose.

In the cy7c67200_300_lcd.c, you will find a function lcd_init that downloads the code to the part. You will see that the function lcd_download_code actually calls the downloaded code. The code that is being downloaded is generated with a script. These scripts can be found in the subdirectory usbd/ dedev and end with a .sh. You will find here that Cypress uses a program called file2struct that converts the bin image to a struct that can then be downloaded. This file2struct.exe is located in C:\Cypress\USB\OTG-Host\Source\coprocessor\linux\drivers\usb\cy7c67300 once you have CY3663 tools installed on your machine.

 Hi,mnsb

I will find the function what you said, thanks very much!

 Hi,PRJI

I want to pass the data from PC to cy7c67300, and then pass the data to the Microblaze which is the soft core of FPGA. The communication mode between Microblaze and cy7c67300 what I selected is HPI mode. According to the reference design, the USB firmware should be downloaded though HPI to the RAM of cy7c67300. I do what it is said, but the result is that PC can't identify the Cypress OTG-Host Design Example 2 Driver! 

 Hi,

   What is the message being displayed in device manager? What is your OS (64 or 32 bit)? Which driver you used for binding the  device?

Thanks

Prajith

Please go through application note AN70973   http://www.cypress.com/?rID=53208 which contains step by step procedure for binding devices to driver. 

Hi,

I have watched the linked video carefully, and now I will describe the situations about my project. I can find the de2 design example driver when the cy7c67300 work on the stand-alone mode which it is said in the specified video. But now, I have changed the GPIO[30:31]  to 00, it seems that the cy7c67300 work on the HPI mode of 3 co-processor mode. And then, PC can't find the usb driver when the board power on, because the EEPROM is disabled. So I deliver the de2 firmware though HPI from FPGA to the RAM of cy7c67300. I can receive the ACK from the BIOS of cy7c67300 at FPGA side after the code download is finished, but the problem is that PC still can't identify the de2 design example driver. I am sure the application code for the delivering the de2 firmware is OK, because it is also used for another project - usbkeyboard demo. I have been trapped for some weeks and I really don't know why, please help me!

Thanks 

 Hi,

     Have you confirmed proper working of HPI interface? Please check it using the initialization code.

 Please add the following code to your processor's initialization code and let me know the behavior. This is to ensure proper working of HPI interface.

MailboxData = XIo_In16(USB_MAILBOX);>>>>>read from mailbox

XIo_Out16(USB_ADDRESS,0x0142);//HPI_IRQ_ROUTING_REG>>>>>select address
XIo_Out16(USB_DATA,0x0000);>>>>>>write data

MailboxData = XIo_In16(USB_MAILBOX);


Status = XIo_In16(USB_STATUS);

XIo_Out16(USB_ADDRESS,0x0144);
XIo_Out16(USB_DATA,0x0000);
Status = XIo_In16(0x0144);

XIo_Out16(USB_ADDRESS,0x0148);
XIo_Out16(USB_DATA,0x0000);
Status = XIo_In16(0x0148);

XIo_Out16(USB_ADDRESS,0xC090);
XIo_Out16(USB_DATA,0xFFFF);

XIo_Out16(USB_ADDRESS,0xC0B0);
XIo_Out16(USB_DATA,0xFFFF);

//usleep(10*1000);
for(i = 0;i<10000;i++)

XIo_Out16(USB_ADDRESS, 0x01C2);
XIo_Out16(USB_DATA, 0x0072);

XIo_Out16(USB_ADDRESS,0x01C4);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01C6);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01C8);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01CA);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01CC);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01CE);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01D0);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01D2);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01D4);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01D6);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01D8);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01DA);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01DC);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_ADDRESS,0x01DE);
XIo_Out16(USB_DATA,0x0000);

XIo_Out16(USB_MAILBOX, 0xFA50);

MailboxData = XIo_In16(USB_MAILBOX);

Status = XIo_In16(USB_STATUS);


//}
while (XIo_In16(USB_MAILBOX) != 0X0FED) {;}
 

Thanks

Prajith

Hi,

I added the post code to my processor initialization code, and I can read the mailbox's value 0xFED. But the PC still identify the de2 design example driver, or maybe you could tell me how can I ensure proper working of HPI interface.

Thanks

 Hi,

  Your HPI interface is fine, that’s why you received 0x0FED from mail box. The code in my previous post does all initialization required for HPI communication reads 0x0FED from mail box if HPI interface is correct.

Thanks

Prajith