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.

TDA4VH-Q1: BOOT capabilities

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: 66AK2H14

Tool/software:

Hi,

I read the SPRSP79B datasheet document and SPRUJ52C TRM document.

I have several questions about BOOTMODE and MCU_BOOTMODE :

  • Table 4-5 refers to POST capabilities but I could not find description of what each capability involves
    • what are the delay introduced by the POST ?
    • How are exploited the POST results ? is there a default "output console" giving results (e.g UART ? ) . Are they only visible through JTAG ? 

  • We can find some QSPI boot configuration described in table 4-10 when MCU_ONLY=0 : "PRIMAY BOOT MODE CONFIG(6..4)" being explained as  "PORT / RSVD / Csel" and Table 4-17 details PORT and Csel but we don't know what should be the value of RSVD. is it "dont'care" ? or should we force pin to '0' ? or '1' ?

  • when considering SPI boot (therefore with MCU_ONLY=0 and Primary_boot_mode_B_pin=1) we can refer to table 4-11 but the required value of "BACKUP_BOOT_MODE_CONFIG" is not given

==> is it "dont'care" ? or should we force pin to '0' ? or '1' ?

  • When considering SPI boot table 4-22 gives possible selection between mode 0 and mode 3 but I could not find any chrono-diagram explaining for each mode
    • which is the SPI clock edge activating Data output : rising ? or falling ?
    • which is the SPI clock edge capturing Data input : rising ? or falling ?

The datasheet gives some switching characteristics (figure 6-98 to 6-103) but t is not very clear which apply to mode 0, which apply to mode 3. ==> Can you explain more ?

  • When considering SPI boot we can see in table 4-1 that the only mentioned SOC peripheral is MCU_FSS0_OSPI0. However we can find in table 4-22 that either PORT0 or PORT1 can be chosen. Do you confirm that PORT1 does correspond to MCU_FSS0_OSPI1 ? which therefore should have been mentioned in table 4-1 ? or Am I mixing things ?

  • When considering PCIe boot table 4-10 and table 4-46 give some possible configuration such as RESERVED / Ssc / Clocking
    • Can you explain what should be the RESERVED value : don"t care ? 0 ? or 1 ?
    • there is no explanation at all about "Ssc" in table 4-46. What should we conclude in that situation ? Ssc is always activated by default when booting through PCIE ? or always de-activated ?
    • about "clocking" : 
      • what is the meaning of external pin ? do you confirm it refers to SERDESx_REFCLK (typical 100 MHz frequency )where "x" is number of the SERDES ?
      • what is the meaning of internal clock ? do you suggest that PCIe clock can be elaborated from internal PLL ? in that case may be only for the Root port since other PCIe endpoint should receive external clock ? isnt'it ?

Thank you for your help

With best regards,

Bruno

  • Hi Bruno,

    Table 4-17 details PORT and Csel but we don't know what should be the value of RSVD.

    RSVD is reserved. It is don't care for you.

    • when considering SPI boot (therefore with MCU_ONLY=0 and Primary_boot_mode_B_pin=1) we can refer to table 4-11 but the required value of "BACKUP_BOOT_MODE_CONFIG" is not given

    ==> is it "dont'care" ? or should we force pin to '0' ? or '1' ?

    I think the table should mention port for the back-up SPI config. I will confirm this and get back to you.

    The datasheet gives some switching characteristics (figure 6-98 to 6-103) but t is not very clear which apply to mode 0, which apply to mode 3. ==> Can you explain more ?

    Can you give me the version and section of the datasheet where this is.

    For the rest of the questions, I'll respond in a couple of days.

    Regards,
    Tanmay

  • Thank you Tanmay for this preliminary reply

    As mentioned in my POST I am referring to SPRSP79B (Feb 2023) datasheet document and SPRUJ52C TRM document.

    Figure 6-98 to 6-103 of the datasheet start from section 6.10.5.19.1.2.1

    With best regards,

    Bruno

  • Hi Bruno,

    I think the table should mention port for the back-up SPI config. I will confirm this and get back to you.

    What I mentioned is correct. The pin 7 will control the port when in Back-up SPI mode. 0 corresponds to port 0 and 1 corresponds to port 1.

    Please see footnote in this :

    • When considering SPI boot table 4-22 gives possible selection between mode 0 and mode 3 but I could not find any chrono-diagram explaining for each mode
      • which is the SPI clock edge activating Data output : rising ? or falling ?
      • which is the SPI clock edge capturing Data input : rising ? or falling ?

    The datasheet gives some switching characteristics (figure 6-98 to 6-103) but t is not very clear which apply to mode 0, which apply to mode 3. ==> Can you explain more ?

    Mode 0 vs Mode 3 only corresponds to data sampling at the controller side and idle clock level. In Mode 0, data is sampled on leading edge and idle clock is low. In Mode 3, data is sampled on trailing edge and idle clock is high. I don't think there are any timing diagrams for this specifically in data sheet.

    You can take a look at the diagram here instead : https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/772490/faq-ads129x-what-are-the-correct-polarity-and-phase-cpol-cpha-spi-settings

    When considering SPI boot we can see in table 4-1 that the only mentioned SOC peripheral is MCU_FSS0_OSPI0. However we can find in table 4-22 that either PORT0 or PORT1 can be chosen. Do you confirm that PORT1 does correspond to MCU_FSS0_OSPI1 ? which therefore should have been mentioned in table 4-1 ? or Am I mixing things ?

    You are correct, Port 1 correspond to MCU_FSS0_OSPI1. It is missing from table 4-1. I will let the team know about this so that it could be corrected in future releases.

    Regards,
    Tanmay

  • Hi Tanmay,

    I am a bit puzzled since the chrono diagrams you are referring to are from a slave perspective. this does not give idea of when is output the data from the MCU master , nor when the MCU_master samples the data.

    precise timing characteristics are necessary to calculate the maximum possible frequency, as well as the margins for a given frequency (for both MASTER writes and MASTER read)

    As an example the datasheet of the 66AK2H14 from T.I (that we used recently) precisely specifies the following :

    Best regards,

    Bruno

  • Hi Bruno,

    To comment on the PCIe portion of your question, currently we do not support booting from PCIe. As TRM mentions, hardware has capability to PCIe boot, but there is no software support whatsoever.

    Regards,

    Takuma

  • Hi Bruno,

    Let me look if we have more detailed diagram for this.

    Regards,
    Tanmay

  • Hi Bruno,

    what are the delay introduced by the POST ?

    The following is the internal measurement data that we have w.r.t HWPOST.

    Setting

    MCU_PORz (rising) to MCU_RESETSTATz (rising)

    POST 00

    44.2ms

    POST 01

    23.8ms

    POST 10

    23.8ms

    POST 11

    576us

    This data is based on measurements using an oscilloscope, since HWPOST runs even before ROM gets to run. 

    How are exploited the POST results ? is there a default "output console" giving results (e.g UART ? ) . Are they only visible through JTAG ? 

    The CTRLMMR_WKUP_POST_STAT (0x4300_C2C0) in general should read 0x103 on a successful completion with no other TimeOut or Error Bits set. This atleast indicates the completion of POST. This register will read 0 if you bypass the POST. The LBIST_TIMEOUT/FAIL bits do indicate a failure, these are expected to be 0 on success cases. The LBIST_MISR register will hold the computed value, and the LBIST_SIG registers have the expected values. The LBIST computed MISR values are then matched against the expected MISR values to really indicate a LBIST success.

    You can use the SDL_LBIST_getPOSTStatus() API to get the results of HWPOST from SW - https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/08_06_00_14/exports/docs/sdl/sdl_docs/userguide/j784s4/modules/lbist.html#example-usage

    Regards,

    Josiitaa