• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 97 subscribers
  • Views 556 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.

AM3874: CPU stucks due to access to register

Chris haaf92
Prodigy 190 points

Part Number: AM3874

Hello,

we are having serveal problems to start the pcie subsystem.

In the uboot we want to analyse the PCIe configuration registers and the cpu stucks. We didn't get a virtual adress from the MMU, so I think the pciess is not accessible.

Although it is not possible to start it with the Initialization Sequence of PCIe Root Complex (sprugz7e 19.3.1.1.1).

Is there something missing in this sequence or is it not possible to start PCIe without an running OS?

Regards

  • 0
    TI__Mastermind 23125 points

    Chris, 

    can you clarify which register hangs the uboot? typically hanging on a hardware register is due to domain not enabled. 

    so were you able to confirm the second step:

      "Bring PCIESS out of reset through the device level reset controller"

    was done by the uboot code correclty? i.e., check reset controller registers. 

    regards

    Jian

  • 0 in reply to jian35385
    Prodigy 190 points

    Hello Jian,

    the system stucks on any register of the pciess-subsystem. The first read is on the register of LTSSM-Debug (0x5100_1728), but all other register in the 0x5100_* are also not accessible.

    An imporant information, we are having some boards where the access stucks and other board there the system starts, same hardware-revision, same firmware/software.

    I dumped the register RM_DEFAULT_RSTCTRL and RM_DEFAULT_RSTST.

    There seems to be OK.

    **** OUTREG32(OALPAtoUA(0x48180B10),0xE3);

      Adr 0x48180B10 Value 0x000000E3

      Adr 0x48180B14 Value 0x0000001C

      **** OUTREG32(OALPAtoUA(0x48180B10),0x63);

       Adr 0x48180B10 Value 0x00000063

      Adr 0x48180B14 Value 0x0000009C

    So the system indicates, that the reset occured.

    Regards

    Chris

  • 0 in reply to Chris haaf92
    TI__Mastermind 23125 points

    Chris, 

    I was out of office for two weeks, and just saw your notes. Can you also check 0x48100B73?

    Jian 

  • 0 in reply to jian35385
    Prodigy 190 points

    Hello Jian,

    I was also out of office.

    What register is the 0x48100B73? I don´t find it in the specification.

    Regards

    Chris

  • 0 in reply to Chris haaf92
    TI__Mastermind 23125 points

    Chris, 

    I will recheck the register address. should not be 0x48100B73. 

    Jian