DS90UB928QEVM: NSC USB NANO for Windows 10

Hello Again,

I have ALP SW and USB2ANY SDK now. I have tried to update DS90UB928QEVM board by "USB2ANY Firmware Loader.exe". You can see following pictures below. And, we think that the update process is complated successfully. 

After this procedure, I have tried to open Analog LaunchPAD SW in my computer. And, I have following screens below. Could you please check them that why we could not connect the board? 

P.S: We only have DS90UB928QEVM and DS90UB927QEVM development boards. We do not have "USB2ANY Interface Adapter" device in our office. Is it OK? Is USB2ANY procedures compatible with our development kits?

Best regards

Hello Vishy,

After following instructions, we successfully updated the driver. We can see the DS90UB927 device in the ALP SW. But, the DS90UB928 device could not be seen. You can see our situation from following pictures.

I think firmware of the DS90UB928QEVM is broken because of the USB2ANY process. Can we return correct firmware for DS90UB928? What do you think? 

Best regards

Additionally, as you can see from following picture, the serializer could not connect with the deserializer. The DS90UB927 serializer device is linked to the video source.

Best regards

Hello,

I explained our USB2ANY situation 4 messages before. I can update the firmware but the ALP sw still have some problems. For example, when I go to "EEPROM Setup" and choose "DS90UB928" instead of "DS90UB925", the following screen is coming.

Additionally, we are using HSD connector for connection. Our 928EVM kit is different than the module that in the ti.com. The schematic of the module is different too. In the "DS90UB928QEVM: New user guide" topic the new schematic of the 928EVM can be seen. We think that the module is working after connecting J18 and J12 jumpers. Could you please check the new schematic? Should we do anything in the module? 

Best regards

Hi Vishy,

Thank you. We have changed the profile. It is 928 now. But, still we have some questions. Could you please check them?

1. Every time when powered up the 928EVM module, we need to update firmware of the 928EVM. Is it normal? 

2. After opening ALP SW, the profile name is DS90UB928. But, in the "Device Information" section the device name is DS90UH926. And, we could not change the "I2C Address" of the 928 IC. We have tried different values by IDX swithes ın the EVM board. The "I2C Address" is always 0x58. Additionally, we can easly change I2C address of the 927 IC. How can we sure that we can properly powered up and connect the 928 IC?    

Thank you

>>>> 1. Every time when powered up the 928EVM module, we need to update firmware of the 928EVM. Is it normal? 

No.Once you have updated to latest firmware using USB2ANY SDK software , you can quit it. The firmware is burnt into MSP430 flash and so you it should stay through power cycles.  You don't need USB2ANY SDK after this.

>>>>>2. After opening ALP SW, the profile name is DS90UB928. But, in the "Device Information" section the device name is DS90UH926. And, we could not change the "I2C Address" of the 928 IC. We have tried different values by IDX swithes ın the EVM board. The "I2C Address" is always 0x58. Additionally, we can easly change I2C address of the 927 IC. How can we sure that we can properly powered up and connect the 928 IC?    

I see in your screen shot, you have ALP connected to both boards. I suggest you remove USB cable between 927EVM and PC. Only connect 928EVM USB port to PC. You can access 927 registers from remote registers window of ALP. You can also do registers r/w access (of both 928 and 927) from scripting tab using their i2c address With only connecting to 928 by USB (and 927 connected over the FPD link) you should see "Linked to Serializer: Yes". 

Thanks,

Vishy

>>>> 1. Every time when powered up the 928EVM module, we need to update firmware of the 928EVM. Is it normal? 

No.Once you have updated to latest firmware using USB2ANY SDK software , you can quit it. The firmware is burnt into MSP430 flash and so you it should stay through power cycles.  You don't need USB2ANY SDK after this.

[S.A.]: Every time when powered up the 928EVM module, we have to update firmware of the 928EVM as I explained in my last post. If we say "No" to update firmware massage, the ALP SW crashes and closes.

>>>>>2. After opening ALP SW, the profile name is DS90UB928. But, in the "Device Information" section the device name is DS90UH926. And, we could not change the "I2C Address" of the 928 IC. We have tried different values by IDX swithes ın the EVM board. The "I2C Address" is always 0x58. Additionally, we can easly change I2C address of the 927 IC. How can we sure that we can properly powered up and connect the 928 IC?    

I see in your screen shot, you have ALP connected to both boards. I suggest you remove USB cable between 927EVM and PC. Only connect 928EVM USB port to PC. You can access 927 registers from remote registers window of ALP. You can also do registers r/w access (of both 928 and 927) from scripting tab using their i2c address With only connecting to 928 by USB (and 927 connected over the FPD link) you should see "Linked to Serializer: Yes". 

[S.A.]: In this step, we have only connected 928EVM board, the USB cable between 927EVM and PC is removed. Both boards are powered and you can see the ALP SW screen below.

[S.A.]: Who can help us for deeper investigation? We can send boards and cables to a FAE or a technical responsible for cheking our problem? May be a FAE in our country, Turkey, can help us in our R&D office?

Thank you

Thank you Vishy,

We will be waiting your help.

Hi Vishy,

Thank you for your kind support. I have reconfigured board settings and rechecked dll files. Now I have picture on the screen. The system is working now. LVDS section is complated and I will continue with I2C and gpio feature.

 Thank you