• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 506 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.

TDA3MD: TDA3x GEL error

KenF
Expert 7150 points
Part Number: TDA3MD

Hello Experts,

My customer is seeing the following error with TDA3xx_prcm_config.gel on their board (not TI EVM). From this error, I though it is because SYS_CLK2 is not fed correctly on their board. Is there any other possibility that they see this error?

Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Clock Configuration for OPP 0 is DONE! <<<---
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules in progress... <<<---
Cortex_M4_IPU1_C0: GEL Output: module_base:   0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000C8
Cortex_M4_IPU1_C0: GEL Output:             TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base:   0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000D0
Cortex_M4_IPU1_C0: GEL Output:             TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base:   0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x000000D8
Cortex_M4_IPU1_C0: GEL Output:             TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: module_base:   0x4A009700
Cortex_M4_IPU1_C0: GEL Output: module_offset: 0x00000130
Cortex_M4_IPU1_C0: GEL Output:             TIMEOUT
Cortex_M4_IPU1_C0: GEL Output: --->>> PRCM Configuration for all modules is DONE! <<<---

[Background]
Per the customer, when they use no boot, they see the above error. However when they use QSPI boot (that their application is in) with the identical board, they don't see the above error. SYS_CLK2 is not fed in both cases. I wonder why there is no error during QSPI boot.

Regards,
Ken

  • 0
    TI__Genius 14305 points

    Hi,

    >>As Per the customer, when they use no boot, they see the above error.

    Can I know which boot is this?

    Can you mention the steps you have followed?

    Thanks

    Gaviraju

  • 0 in reply to Gaviraju Doddabettahalli Bettegowda
    TI__Expert 7150 points

    Hello Gaviraju,

    >Can I know which boot is this?

    They use UART boot with no image load (so, it is same as no boot I think).

    [No error]

    1. Set QSPI boot.

    2. Board power on. (Customer application image is loaded here)

    3. Connect CCS with TDA3xx_prcm_config.gel.

    4. No error

    [Gel Error]

    1. Set UART boot.

    2. Board power on. (No image load)

    3. Connect CCS with TDA3xx_prcm_config.gel.

    4. GEL error (See previous post)

    Note that SYS_CLK2 is not fed in both cases.

    Regards,

    Ken

  • 0 in reply to KenF
    TI__Genius 14305 points

    Hi,

    The UART boot mode is used only to flash images to the QSPI memory using mflash tool & you should not suppose to connect CCS with UART boot mode.

    Refer to the below document for more information on mflash.

    File: ti_components/drivers/pdk_xx_xx_xx_xx/packages/ti/boot/sbl_auto/docs/AppNote_mflash.pdf.

    You can connect CCS with the following boot modes for debugging.

    Thanks

    Gaviraju

  • 0 in reply to Gaviraju Doddabettahalli Bettegowda
    TI__Expert 7150 points

    Hi Gaviraju,

    Thank you for your response. One more question. Why do you think they don't see any error when booting from QSPI_4 though there is no SYS_CLK2 in their system? Is there any possibility? Can another signal be the alternative signal?

    Best regards,

    Ken

  • 0 in reply to KenF
    TI__Genius 14305 points

    Hi,

    The step to connect target with CCS is

    1) Open the CCS

    2) Launch target configuration

    3) Remove gel file(This step is required only for SD, QSPI, NOR boot mode & gel file used only Debug mode(00111000 10000001). The gel files are used to initialize DDR, clock, etc. So this is required only Debug mode. In SD, QSPI boot mode this initialization will be done by the image)

    4) connect core

    Thanks

    Gaviraju 

  • 0 in reply to Gaviraju Doddabettahalli Bettegowda
    TI__Expert 7150 points

    Hi,

    I was not asking how to connect target with CCS. what I was asking was

    Why they don't see any error when booting from QSPI_4 though there is no SYS_CLK2 in their system?

    Regards,

    Ken

  • 0 in reply to KenF
    TI__Guru**** 477995 points

    Hi Ken,

    When you use QSPI boot mode, do you also flash SBL in QSPI?

    Do you also enable the modules that gel files are trying to enable? 

    Are there any changes in the board that you are using from the EVM? I mean does this board require any changes in the gel files?

    Can you also please go bit inside and see for which module PRCM is failing?

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    TI__Expert 7150 points

    Brijesh,

    >Are there any changes in the board that you are using from the EVM? I mean does this board require any changes in the gel files?

    Yes, there are lots of changes because they are using their own board. I believe the board requires changes in the gel files but we are not sure what changes are required.

    >Can you also please go bit inside and see for which module PRCM is failing?

    Regarding last question, the error shows when DCC1~4 is set.

    Regards,

    Ken

  • 0 in reply to KenF
    TI__Expert 7150 points

    Brijesh,

    Any comments or ideas would be appreciated.

    Regards,

    Ken

  • 0 in reply to KenF
    TI__Guru**** 477995 points

    Hi Ken,

    ok, since the errors are due to DCC module, can you try commenting out DCC specific initialization from gel files and try out?

    I think DCC would not be required for flashing to QSPI.

    Rgds,

    Brijesh