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.

TDA2P-ACD: when SD CARD BOOT TEST, ERR_DEISOLATE_IO

Part Number: TDA2P-ACD

Dear Sir.

My customer is testing EVM & their Board. 

for EVM, good operating for Boot test using SD CARD

for customer's board, happened ERROR as DEISOLATIE_IO.

It seems H/W error.

I found about ISOLATION requirements sequence.

it seems happened error for PRM_IO_PMCTRL[1] ISOCLK_STATUS bit not set to "1".

1) Boot test method
  -SD CARD boot progress
  -Basic GPIO setting and PMIC (I2C) setting completed
  -Error occurred during DRAM (DDR3L) test
   > DQM signal remains Hgh and does not work
   > Other functions (command, address, data) except DQM work normally

----------------------------- In dra7xx_iodelay.c ----------------------------
static int isolate_io(u32 isolate)
{
if (isolate) {
clrsetbits_le32((*ctrl)->control_pbias, SDCARD_PWRDNZ,
SDCARD_PWRDNZ);
clrsetbits_le32((*ctrl)->control_pbias, SDCARD_BIAS_PWRDNZ,
SDCARD_BIAS_PWRDNZ);
}

/* Override control on ISOCLKIN signal to IO pad ring. */
clrsetbits_le32((*prcm)->prm_io_pmctrl, PMCTRL_ISOCLK_OVERRIDE_MASK,
PMCTRL_ISOCLK_OVERRIDE_CTRL);
if (!wait_on_value(PMCTRL_ISOCLK_STATUS_MASK, PMCTRL_ISOCLK_STATUS_MASK,
(u32 *)(*prcm)->prm_io_pmctrl, LDELAY)) {
return ERR_DEISOLATE_IO << isolate; <-----------------
}
------------------------------------------------------------------------------

  • Dexter,

    Can you confirm this is related to this previous thread:

    Have you updated the SDK to the latest as suggested by Keerthy:

    Also, can you summarize the DQM observations?  What if you don't do the isolate and desolate steps - does DDR work?

    Thanks,

    Kyle

  • Dexter,  (I accidentally clicked "TI thinks resolved" ... please reject that)

    Can you also confirm ... how many systems are being tested?  Can you try on 3 to 5 different PCBs?

    Thanks,

    Kyle

  • Can you confirm this is related to this previous thread: YES!!

    TDA2P-ACD: U-Boot isolate_io function is failed

    TI E2E support forums
    Part Number: TDA2P-ACD Hello. We made the custom board with TDA2P-ACD chip. And I tried to boot using SD CARD with MLO and u-boot.img in it. But it didn't boot. TDA2P EVM board with the same firmware boot well. When I checked the log by quickly...

    Also, can you summarize the DQM observations?  What if you don't do the isolate and desolate steps - does DDR work?

    =>DQM is good working. if not use Isolate and deisolate steps. DDR is good working.

    Can you also confirm ... how many systems are being tested?  Can you try on 3 to 5 different PCBs?

    =>They Have 3~5 deferent PCBs. not test yet another PCB.

    could you let me know why don't work 3rd step of Isolation sequence as below picture.

    please advise any comment me about  Isolation sequence...

  • =>They Have 3~5 deferent PCBs. not test yet another PCB.

    Are you saying they have tested on a single PCB / SoC?  In that case they may be battling a PCB mounting issue (bad solder?) or even potentially a defective SoC.

    Can you test on additional units?

    Can you share the DIE_ID of the failing unit?

    Thanks,
    Kyle

  • Dear Kyle,

    I had tested on other PCBs but it work same operation.

    how to check DIE_ID of the failing unit?

    Could you let me know another check point?

  • You can read the DIE_ID from the registers mapped as follows:

    Regards,

    Kyle

  • It looks like the image didn't come through.  Refer to 

    Table 1-2. Device Identification Register Fields

    Regards,

    Kyle

  • Hi Kyle,

    please refer to the below DIE_ID.

    0x4A002134 = 0x000000F0

    0x4AE0C200 = 0x15015017

    0x4AE0C204 = 0x0BB5002F

    0x4AE0C208 = 0x013765C1

    0x4AE0C20C = 0x29A7110D

    0x4AE0C210 = 0x1DA00000

    0x4AE0C214 = 0x2ED400F0

  • Hi Kyle,

    Is there any update?

    sorry for pushing you. my customer takes long time for development schedule.

    please check it..

  • Dexter,

    How many PCBs are tested now?  Are they all the same exact observations?  

    Have you updated the SDK as suggested by Keerthy?

    Are the DQM observations the same?

    Thanks,

    Kyle

  • Hi Kyle,

    They had tested 5 PCBs. it is same issue. and DQM issue is clear for EVM and Their PCB.

    Now they want to check Isolation sequence why stop at 3rd step.

    please advise me any comment. then I will check it.

    Thanks.

  • Dexter,

    Can you clarify what this means:

    >  DQM issue is clear for EVM and Their PCB.

    Is the same exact software sequence working correctly on the EVM?  I believe you indicated previously that the EVM is working properly.

    For this to fail consistently on five boards ... there is either a fundamental software problem, or a fundamental hardware problem.

    1) Can you test with the latest SDK?

    2) Can you investigate possible hardware problems - starting with checking that all power supply inputs to the SoC are correct.  

    Are you using the recommended PMIC solution?  

    Is power sequencing correct?

    Regards,

    Kyle

  • Hi Kyle,

    You think this problem is H/W side?

    Could you help let me know another check point?

    1) Can you test with the latest SDK?

    Yes, SDK is latest version.

    2) Can you investigate possible hardware problems - starting with checking that all power supply inputs to the SoC are correct.  

    Are you using the recommended PMIC solution? 

    Yes, They designed similar with SDK.

    Is power sequencing correct?

    looks like correct.

  • Dexter,

    If you're really using the latest SDK, and can use the same exact SW on the EVM (and it works) and on the customer's PCB (and it doesn't work) then it must be the customer's hardware.

    Regards,

    Kyle