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.

TDA4VM: SOC_I2C2 devices and automation header

Part Number: TDA4VM
Other Parts Discussed in Thread: INA226

Hi,

I'm working on a custom design based on TDA4VM EVM. The idea is to get a minimal version of the EVM that works with the prebuilt FW/SW from the SDK.

My questions are:

1. Can I remove the ina226 current monitors without FW impact?

2. Is the io expander for bootmode pins used by SoC or only automation header? Can this io expander be removed without FW impact?

3. Also, will never boot from EEPROM. Can I remove the EEPROM without FW impact?

4. EVM has a board ID EEPROM. Is there any dependency to it? Can I remove it without FW impact? 

Thanks,

David

  • Hi David,

    Which SDK are you using or planning to use?


    1. Can I remove the ina226 current monitors without FW impact?

    Yes this could be removed but you might see error prints from ina22x drivers during Linux boot.

    3. Also, will never boot from EEPROM. Can I remove the EEPROM without FW impact?

    Should be okay as well.

    EVM has a board ID EEPROM. Is there any dependency to it? Can I remove it without FW impact? 

    It can boot without that. There might be some messages on the u-boot logs.

    Is the io expander for bootmode pins used by SoC or only automation header? Can this io expander be removed without FW impact?

    I will let my colleague Robert answer that.

    Best Regards,
    Keerthy

  • The IO expander for BOOTMODE is used by the automation header.  Yes - can be removed without impact to FW/SW.

  • Hi Keerthy, Robert,

    Thanks for the information. The SDK we are planning to use is PROCESSOR-SDK-RTOS-J721E_07.03.00.07 which seems to be the latest RTOS release for TDA4VM. We want to use the vision apps so it seems the RTOS SDK is what we need.

    • Please confirm if your previous comments apply to this SDK too.
    • Also, per the previous response the board should boot without board ID EEPROM , but would there be any misconfiguration on the system because of its absence?

    Thanks,

    David

  • David,

    Keerthy will need to help answer this.  I know SW reads the Board ID EEPROM and gets board name, revision, etc information and makes decisions based on that information.

  •  could you confirm on the last 2 questions please +  a new one:

    • Please confirm if your previous comments apply to this SDK too.
    • Also, per the previous response the board should boot without board ID EEPROM , but would there be any misconfiguration on the system because of its absence?

    To avoid impact or misconfiguration. Can I just put the same eeprom and put the contents that the SoC expects on an EVM? Where could I get these contents from, If I were going to do this.

  • Hi David,

    U-boot directory: board/ti/j721e/evm.c


    int checkboard(void)
    {
            struct ti_am6_eeprom *ep = TI_AM6_EEPROM_DATA;

            if (do_board_detect())
                    /* EEPROM not populated */
                    printf("Board: %s rev %s\n", "J721EX-PM1-SOM", "E2");
            else
                    printf("Board: %s rev %s\n", ep->name, ep->version);

            return 0;
    }

    So it is taking some default string if eeprom not populated. So that is why i mentioned it would boot.

    There could be mis-configuration due to that.

    Please confirm if your previous comments apply to this SDK too.

    Yes Robert's comments apply to this SDK too.

    My board EEPROM Contents read: J721EX-PM2-SOM  E6

    That is where u-boot picks it from.

    : Can you help David with contents of EEPROM?

    Best Regards,
    Keerthy

  • Below are EEPROM contents for J721EX SOM.  Version numbers might be different.