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.

AM5728: Does PMIC TPS6590379ZWSR can causes boot failure for am5728 SOCs?

Part Number: AM5728
Other Parts Discussed in Thread: TMDSEVM572X, TPS659037, AM5729,

Dear Team,

We have design a custom board based on AM5728BABCXA SOC.

Our schematics were verified by TI members on via E2E forum.

The reference schematics were taken from TMDSEVM572x evaluation board.

As per observation we found that the PMIC part no for the evaluation kit is TPS6590376ZWSR

and we selected  TPS6590379ZWSR.

The problem is we are not able to bring board in u boot stage.

we select uart3 for the serial console same as evaluation board.

We have checked all the smps supply and oscillator clock and found that it works well.

Our main questions are:-

1. The selection of different part no PMIC can cause the problem?

2. The PMIC we selected TPS6590379ZWSR is also getting used in AM5729 devices, so any dependency to use that PMIC

for AM5728 device?

3. If PMIC not is an issue then how we diagnose to get board bring up successfully.

Note : The SDK version is 06.02.00.81

Regards

Krishna Vashistha

  • Have you verified all processor power rails are correct voltages (and powered up in the corrector sequence)?  Note the PMIC will control the sequence of many of the supplies.

    What frequency of clock source being supplied to OSC0 and has it been verified?

    Does the power-on reset input (PORz) stay asserted until all supplies are stable (per specification) ?  Is this signal go high releasing the processor from reset?

    What is the status of reset output (RSTOUTn)?  Is this signal go high after PORz is released?

    Do your design provide JTAG access to the processor and do you have emulator available?  Have you verified if the device can be connected via JTAG?

    What is your boot mode setting (SYSBOOT)?

    Do you see anything printed via UART3 console?

  • Dear Robert,

    thank you for the response.

    Have you verified all processor power rails are correct voltages (and powered up in the corrector sequence)?  Note the PMIC will control the sequence of many of the supplies.

    Please see the attached document regarding voltage rails we observed  in our custom board.

    power_check.pdf

    Does the power-on reset input (PORz) stay asserted until all supplies are stable (per specification) ?  Is this signal go high releasing the processor from reset?

    - Yes, the signal goes high and remains in high state @3.3V.

    What is the status of reset output (RSTOUTn)?  Is this signal go high after PORz is released?

    -Yes. always remain in high state after PORZ is high.

    Do your design provide JTAG access to the processor and do you have emulator available?  Have youverified if the device can be connected via JTAG?

    Yes, We will try with JTAG.

    Do you see anything printed via UART3 console?

    -No, only garbage character appeared on screen.

    Regards

    Krishna Vashistha

  • Dear Robert,

    We have performed analysis over CCS with JTAG debug mode.

    Please look into the screenshot.

    We did the following:-

    1. go to tools ->load memory->/spl/u-boot-spl.bin.

    2. set start address = 0x40300000 then finish.

    3. go to run-> load->load Symbols->/spl/u-boot-spl and then ok

    4. We saw a message regarding do_board_detect() and does not know why this occurred.

    5. After changing the PC value to 0x40300000.

    6. when clicked on resume F8.

    We expect that something should be appeared on uart 3

    but still not getting on the serial console.

    Please suggest how we would debug more to get our hardware run?

    Regards

    Krishna Vashistha

  • The processor seems functional.  Did your design change any other critical item related to processor - like oscillator frequency, pins used for UART3, etc?

  • The issue has been resolved by putting correct  value of .dmm_lisa_map_3 in board.c file.

    Thank you to be with us.