This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS90UB638-Q1: DS90UB638 support with Analog Launch Pad

Part Number: DS90UB638-Q1
Other Parts Discussed in Thread: DS90UB954-Q1, ALP, USB2ANY

We replaced the DS90UB954-Q1, on one of our EVMs, with a DS90UB638. I connected it to the DS90UB953 serializer EVM and the lock and pass LEDs come on. It seems to be working. 

However, i was not able to select it in the list on your Analog Launch Pad utility. 

  • Hi Doug,

    Do you mean you cannot find the DS90UB638 ALP profile when you go to USB2ANY/Aardvark setup? Have you installed the ALP Profile Update?

    Also note that DS90UB638 is only compatible with DS90UB635 and DS90UB633A as mentioned in the datasheet. However, you can replace the 954 with 638 and the 953 with 635 on the 954/953 EVMs.

    Regards,

    Cindy

  • Cindy,

    Our product will use the 635 serializer and the 638 deserializer. We had to start with the 954/953 EVMs as there were no 638/635 EVMs available.

    I had not installed the ALP Profile Update. Just installed it. It still does not show up. I figured i did something wrong but looking at the list of supported devices, for the profile update, it doesn't show the 638?

    Thanks,
    Doug

  • Hi Doug,

    The list does not include 635 or 638, but they are supported. I tried downloading the profile update and I see the two profiles populate in my folder. 

    After you download the profile update on https://www.ti.com/tool/download/ALP-PROFILE-UPDATE/01.00.00.0L, run the .exe file on your computer. After it is done running, you should be able to see the profiles in C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\Profiles. 

    Can you check that folder to see if the two folders for DS90UB635 and DS90UB638 show up? 

    If it does, open ALP with the 638 EVM connected and on. Click on "USB2ANY/Aardvark Setup" under Tools. The 638 profile should appear under the "Select a Daughter Board" section. 

    Regards,

    Cindy 

  • Cindy,
    Thanks for he help. It turned out that the update was not properly installed. I am now able to select the 638 as the deserializer.

    We modified our serializer EVM with a 635 device and connected it to the 954 EVM (with the 638 installed). The lock and pass LEDs are on. I connected the ALP to the USB port of the 638 Deserializer EVM, selected the 638 device, and i can now read all of its registers. However, i am not able to read the remote I2C (635) registers. It shows 00 for all I2C registers.

    If i plug the ALP USB port into the Serializer (635) EVM, i am able to read all of the I2C registers.

    I recall that, when originally testing the 954 to 953 EVMs, i was not able to read the remote serializer registers until i selected the RX0 port. Since the 638 deserializer has only one RX port, it defaults to this port.

    Thanks,
    Doug

  • Hi Doug,

    In the 954 ALP Information tab, do you see that the 638 is linked, and do you see the IDX address of the remote 635?  

    It is normal to have to select the RX port in the Remote Registers tab of ALP in order to read them. 

    Just to make sure, can you go to the "Scripting" tab and read the IDX address of the remote serializer using the following command: 

    board.ReadI2C(serAddress, 0x00) - replace serAddress with the address of the serializer 

    If you are able to read the IDX value, it may be due to the ALP profile. If so, can you try using the 954 profile on ALP to see it works there?  

    Regards,

    Cindy 

  • Cindy,

    I see the serializer ...

    When i run the script, i sometimes get a 48 back. Sometimes 0?

  • I tried changing the Deserializer to the 954. At first, i got the same results. I then i switched to RS1, and back to RS0. I can now read the GPIO from the 

    serializer, along with the other registers. They were all previously reading 0x00

  • Hi Doug,

    If you are only able to get it to work with 954 using that method, you can continue to use the 954 profile. It sounds like the devices are locking and working as expected. We will work on investigating the 638 profile internally to see if there is a bug with the remote registers tab. 

    Regards,

    Cindy 

  • Cindy,

    Thanks for confirming our findings. We will continue to use the 954 profile until there is a fix for the 638.

    My fear is that some things will be enough different, between the 954 and the 638, that we will see problems when we try to do real stuff, like transferring video from the serializer to the deserializer. We should be starting this next week, as we are building proto boards to adapt the serializer EVM with the camera we plan on using and to output the deserializer output to our processor EVK.

    What issues should we expect, due to differences between the 600 series parts vs the 900 series parts?

    Thanks,
    Doug

  • Hello Doug,

    Cindy is OoO and will get back to you on Monday.

  • Hi Doug,

    You can still use the 638 ALP profile. If you are unable to read the indirect registers from the Indirect Registers tab, you can always read the register values in the Scripting tab. You will need to select the indirect page using register 0xB0 and select the indirect register you want to read using register 0xB1. 

    For example, to read register 0x01 from indirect page 0x00, you would write: 

    board.WriteI2C(devAddr, 0xB0, 0x00) 

    board.ReadI2C(devAddr, 0xB1, 0x01)

    The ALP profile itself will not cause any issues, but the registers in the two profiles will differ since 954 has dual RX ports. I recommend using the 638 profile and making use of the Scripting tab to read indirect registers rather than the tab itself if it is not working. 

    Regards,

    Cindy