• Resolved

DS90UB941AS-Q1: DS90UB941AS-Q1 SPI use problem

Prodigy 100 points

Replies: 9

Views: 106

Part Number: DS90UB941AS-Q1

hi,TI

    We discovered this problem when testing the SPI communication of the NXP-941-948-MCU link. After NXP sent the SPI signal to 941, there was no signal output on the 948 SPI pin. How to improve so that 948 can send out SPI signal?

  • Hello,

    This can have different reasons including timing specs that needs to be maintained. Please send me your email adress, then I can send you an AppNote describing all these use cases and parameters!

    Regards,

    Hamzeh

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Training on FPD-Link Serializer Deserializer devices and system: https://training.ti.com/fpd-link-learning-center

    More information on IVI or ADAS FPD-Link products: http://www.ti.com/interface/fpd-link-serdes/overview.html

  • In reply to Hamzeh Jaradat:

    hi,Hamzeh

    My email address is as follows: lpf@vikeer.com
    Thanks for your help.

  • In reply to user6558634:

    Will send you the email now.

    Regards,

    Hamzeh

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Training on FPD-Link Serializer Deserializer devices and system: https://training.ti.com/fpd-link-learning-center

    More information on IVI or ADAS FPD-Link products: http://www.ti.com/interface/fpd-link-serdes/overview.html

  • In reply to Hamzeh Jaradat:

    hi,Hamzeh

    We modified the code. The CLK and SS pins have correct signal output, but the MISO and MOSI pins have no signal. Our configuration for 941 and 948 is as follows:
    write(941,0x03,0x9A); write(941,0x62,0x00); write(941,0x20,0x8F); write(941,0x21,0x06);
    write(941,0x1E,0x01); write(941,0x0D,0x33); write(941,0x0E,0x05); write(941,0x1E,0x02);
    write(941,0x0D,0x03); write(941,0x0E,0x00); write(941,0x1E,0x01);

    /*------------------------------------------------------------------------------------------------------------------*/

    write(948,0x43,0x16); write(948,0x23,0x60); write(948,0x34,0x41); write(948,0x1D,0x05);
    write(948,0x1E,0x03); write(948,0x34,0x42); write(948,0x1D,0x00); write(948,0x1E,0x00);
    write(948,0x1E,0x03); write(948,0x34,0x41);


    We have used some GPIO mapping, so we configured some registers about GPIO and D_GPIO.

  • In reply to user6558634:

    Remove the last write(948,0x1E,0x03), this is a copy error.

  • In reply to user6558634:

    Hello,

    are you using Dual lane mode? SPI is only available in dual lane mode!

    Are you using Forward channel SPI or reverse channel SPI? This is important to know, since you need to configure all the used pins/GPIOs in the correct direction, as per Table 2 in the provided AppNote.

    Regards,

    Hamzeh

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Training on FPD-Link Serializer Deserializer devices and system: https://training.ti.com/fpd-link-learning-center

    More information on IVI or ADAS FPD-Link products: http://www.ti.com/interface/fpd-link-serdes/overview.html

  • In reply to Hamzeh Jaradat:

    We are using Dual FPD-link tx mode, forward Channel mode. Regarding GPIO, we will reconfigure all of them for testing.Thanks for your help.

  • In reply to user6558634:

    Thanks for your reply.

    Please also make sure you configure reg 0x43 on the DES as per AppNote section 5. In this case you should not freeze DES capability on SER reg 0x20, so that reg 0x20 and 0x21 are set correctly by the DES via the back channel.

    Regards,

    Hamzeh

    ------------------------------------------------------------------------------------------------------------------------------------------------

    Training on FPD-Link Serializer Deserializer devices and system: https://training.ti.com/fpd-link-learning-center

    More information on IVI or ADAS FPD-Link products: http://www.ti.com/interface/fpd-link-serdes/overview.html

  • In reply to Hamzeh Jaradat:

    Thank you for your support. After repeatedly confirming the software configuration, we found that the problem occurred in the hardware link between MISO and MOSI. Now all SPI signals can be generated normally.
    Thanks for your help.