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.

TDA4VH-Q1: XJ784S45AALY-HS-SE-FS can not boot

Part Number: TDA4VH-Q1

Dear TI

Our latest PCBA use XJ784S45AALY-HS-SE-FS for eFuse programing,found several Soc cannot boot from ospi , there is no data and clk waveform about ospi when power on,
attempted to make some modifications as below。

MCU[9:8] 11 , can boot;
MCU[9:8] 01 , cannot boot;
MCU[9:8] 00 , can boot;

According to the specification,MCU[9:8] are the POST config pins,

What's the reason for the above.
Which POST  sequence we should use ,what determines the configuration of MCU[9:8]。

thanks

  • Add more information:

    Post config Pins

    When the set MCU[9:8] 01, it can't start up. The details of phenomenon show as follow:

    OSPI flash data and clock no signal

    1.We have already double confirmed BOOT MODE pins was set correct.

    2. Power supply for MCU domain was normally because MCU_PORZ in high level state.

    3. There are two chips that will definitely reproduce this problem. Two chips accidentally reproduced this problem. Most of the chips are in normal condition
  • Hi Kangjia,

    As you rightly pointed out, these pins are used to select different modes of POST settings. We will have to check with the HW team why BIST running in parallel is not working. Does it work fine in any other boot mode? Is it the issue only in ospi boot mode? 

    But I think setting it to 00 is working fine, which means BIST running in serial seems to be working fine, isn’t it? Any issue in running this setting?

    Regards,

    Brijesh

  • Brijesh,
    Yes, it nee HW team check why it can’t work normally with parallelly. Kindly please help loop HW expert to discuss and share conclusions to this link. Thanks~

  • Brijesh,
    Is there any update for this issue? 

  • Hi Kangjia,

    Unfortunately, not yet, i will update you, as soon as i get some information. 

    Regards,

    Brijesh

  • Hello,

    Can you summarize how many systems have been built/tested and how many are seeing this issue?  

    Can you read and report these register values:

    0x4300_0030

    CTRLMMR_WKUP_DEVSTAT

    0x4300_0038

    CTRLMMR_POST_SEL_STAT

    0x4300_003C

    CTRLMMR_POST_OPT

    0x4300_C000

    CTRLMMR_SMS_LBIST_CTRL

    0x4300_C004

    CTRLMMR_SMS_LBIST_PATCOUNT

    0x4300_C008

    CTRLMMR_SMS_LBIST_SEED0

    0x4300_C00C

    CTRLMMR_SMS_LBIST_SEED1

    0x4300_C018

    CTRLMMR_SMS_LBIST_STAT

    0x4300_C01C

    CTRLMMR_SMS_LBIST_MISR

    0x4300_C280

    CTRLMMR_SMS_LBIST_SIG

    0x40F0_C000

    CTRLMMR_MCU_LBIST_CTRL

    0x40F0_C004

    CTRLMMR_MCU_LBIST_PATCOUNT

    0x40F0_C008

    CTRLMMR_MCU_LBIST_SEED0

    0x40F0_C00C

    CTRLMMR_MCU_LBIST_SEED1

    0x40F0_C018

    CTRLMMR_MCU_LBIST_STAT

    0x40F0_C01C

    CTRLMMR_MCU_LBIST_MISR

    0x40F0_C280

    CTRLMMR_MCU_LBIST_SIG

    0x4300_C2C0

    CTRLMMR_WKUP_POST_STAT

    0x4300_C2C4

    CTRLMMR_WKUP_POST_CFG0

    0x4300_C2CC

    CTRLMMR_WKUP_POST_CFG1

    Thanks,

    Kyle

  • Kyle,

    update the register value show as following:

    CTRLMMR_WKUP_DEVSTAT:0x308

     

    CTRLMMR_POST_SEL_STAT:0x0

     

    CTRLMMRPOST_OPT:0xa0f0e

     

    CTRLMMR_SMS LBIST_CTRL:0x0

     

    CTRLMMR_SMSLBIST_PATCOUNT:0x0

     

    CTRLMMR_SMS LBISTSEEDO:0x0

     

    CTRLMMR_SMS LBIST SEED1:0x0

     

    CTRLMMR_SMS_LBIST_STAT:0x0

     

    CTRLMMR SMS LBIST_MISR:0x61400000

     

    CTRLMMR SMS LBISTSIG:0x0

     

    CTRLMMR_MCULBISTCTRL:0x0

     

    CTRLMMR_MCULBISTPATCOUNT:0x0

     

    CTRLMMRMCULBISTSEEDO:0x0

     

    CTRLMMR_MCU_LBIST_SEED1:0x0

     

    CTRLMMR_MCU_LBIST_STAT:0x0

     

    CTRLMMR_MCU_LBIST_MISR:0x61400000

     

    CTRLMMR_MCULBIST_SIG:0x0

     

    CTRLMMRWKUP POST STAT:0x0

     

    CTRLMMRWKUP POSTCFGO:0x3501005c

     

    CTRLMMRWKUP_POST_CFG1:0x3501006f

  • Kangjia,

    There are several register values that are questionable. Is this a very early sample??
    Please try with another device.

    I cannot explain why the part does not boot, but I can tell you that you are not really running a self-test.

    Kevin

  • Hi Kevin,

    It should be early sample. what's the details of register values that are questionable?

    In order to start up normally, customer close self-test and read register. It can't read register value if not close self-test.

    How to debug in next steps? Thanks~

  • There are a couple of things that are strange -- one is that the pattern count is 0.