• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 99 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM2634: report fail while run both STC and PBIST by sequence

Terry Deng
Expert 3015 points
Part Number: AM2634


Tool/software:

Dear expert

My customer report fail while run both STC and PBIST by sequence on AM2634 SBL, the device will enter Hwip_user_data_abort_hander_c. However it is ok for running either STC or PBIST by independent. May we get advice if it need special configuration after STC and then before PBIST? 

  • 0
    TI__Guru 73741 points

    Hi Terry,

    I want to know the exact sequence that customer is using, because if customer is running STC after PBIST without any warm reset between them then there is one known issue which is currently Design team is looking into.

    If they want to do in above sequence (STC after PBIST), then customer should do as per below sequence:

    Successful Steps:

    • PBIST runs
      • Runs up to 3 times if there is a failure
    • PBIST performs warm reset
    • On 2nd boot, PBIST is skipped because results show passing results
    • STC self test runs
      • Up to 3 times
    • STC module automatically resets, does not require warm reset call
    • 3rd boot,
      • PBIST + STC both are passing

    If customer running PBIST after STC then there should not be any issues.

    --

    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    TI__Guru 73741 points

    Hi Terry,

    We found one problem in PBIST and provided workaround as well:

    The root cause for this issue is that the exit sequence does not happen properly for PBIST testing.

    I mean we should make sure to have below MMR values should be zero after PBIST test:

    TOP_PBIST_Ptr->PBIST_PACT_UN.PBIST_PACT_ST.PBIST_PACT=0x0;

    MSS_CTRL_Ptr->MSS_PBIST_KEY_RST_UN.MSS_PBIST_KEY_RST_ST.MSS_PBIST_KEY_RST_PBIST_ST_KEY = 0x0;

    If this happens properly then there won't be any issue in executing STC test.

    We raised a JIRA internally to rectify this issue in next SDK release:

    [PROC_SDL-9297] STC failures were occurring if a warm reset did not occur after PBIST - Texas Instruments JIRA

    As a work around you can include below highlighted code in your project:

    This will reset the PBIST after testing: 

    MSS_CTRL_Ptr->MSS_PBIST_KEY_RST_UN.MSS_PBIST_KEY_RST_ST.MSS_PBIST_KEY_RST_PBIST_ST_KEY = 0x0;

    If we did this then STC will going to execute successfully:

    --
    Thanks & regards,
    Jagadish.