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.

SK-TDA4VM: Programmed power supply fails to start SK-TDA4VM

Part Number: SK-TDA4VM
Other Parts Discussed in Thread: TDA4VM

Dear TI Support !

  We wanted to build a remote device environment and power the SK-TDA4VM through a programmable power supply(Keysight E3648A, Setting to 5V=3A), but we found that the development board could not start and kept restarting. The log and hardware connections are as follows: How should we set up this HW environment?

0246.reboot_log.txt
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
U-Boot SPL 2023.04-gbd74e615a6 (Sep 06 2023 - 10:09:25 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image d
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image d
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image d
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image d
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image d
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...
NOTICE: BL31: v2.9(release):v2.9.0-dirty
NOTICE: BL31: Built : 14:12:59, May 22 2023
I/TC:
I/TC: OP-TEE version: 3.20.0 (gcc version 11.3.0 (GCC)) #1 Fri Jan 20 15:42:54 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • ,

    What is the total "Watts" power you supplied ?

    Because, the tda4VM-SK board requires "60W of power (20VDC at 3A)". The minimum supply required is 15W supply (5VDC at 3A). However, a 5 V supply may limit available processing with TDA4VM as well as limit some of the available peripherals

    ---

    I understand that you are planning for a remote environment.

    But however for other users, we can order the power supply adaptors from the recommended manufacturers given below:

    --

    Please refer this user guide:- page no: 5 - https://www.ti.com/lit/ug/spruj21c/spruj21c.pdf

    Regards

    Shankari G

  • Yes, we have purchased the QADC-65-20-08CB and it does boot. But we still want to use a programmable power supply to build a remote environment, and we tried 5VDC==3A/5VDC==5A/20VDC==3A/20VDC==5A but it couldn't start normally. Is there any way to solve this problem?

  • Daiwang,

    Your query will get notified to hardware engineers.

    Thanks for your patience.

    Regards

    Shankari G

  • Yes, we have purchased the QADC-65-20-08CB and it does boot.

    You said, it boots with " QADC-65-20-08CB"....

    Meanwhile, would you post your successful boot logs when you used " QADC-65-20-08CB", power supply adaptor.

    Regards

    Shankari G

  • The board did not boot with 20V/3A supply connected?  The board is designed to work with a USB-C supply.  You are providing voltage, but may not be sufficient for the USB controller to enable the on-board supplies.  Can you measure on-board supplies to see if USB controller is enabling power?  Maybe measure power net VMAIN - it should have the same voltage (or near same) as the supplied VBUS.  Or you can measure any of the other on-board regulators.

  • Yes, Normal boot log (use QADC-65-20-08CB) as follow:

    QADC-65-20-08CB-boot.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    U-Boot SPL 2023.04-gbd74e615a6 (Sep 06 2023 - 10:09:25 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
    Trying to boot from MMC2
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Loading Environment from nowhere... OK
    Starting ATF on ARM64 core...
    NOTICE: BL31: v2.9(release):v2.9.0-dirty
    NOTICE: BL31: Built : 14:12:59, May 22 2023
    I/TC:
    I/TC: OP-TEE version: 3.20.0 (gcc version 11.3.0 (GCC)) #1 Fri Jan 20 15:42:54 UTC 2023 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
    I/TC: Primary CPU initializing
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.6--v09.00.06 (Kool Koala)')
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • I'm sorry I don't understand the response.  You provided boot log (showing board is working).  That is using which supply?  If the lab bench supply is NOT working - you can power the board using USB supply and connect the lab bench supply to the power control header.  Pulling Pin 1 to GND will disable the board supply.  

  • Robert,

    To make sure the board is in working condition, I asked Daiwang to post the successful boot logs using the Qualtek USB-C power supply - QADC-65-20-08CB.

    That is what he did. He replied for my post saying, the board works with standard power supply....

    Daiwang,

    Would you please reply to Robert about the "onboard-supplies " I.e., Robert's post above --- >

    Can you measure on-board supplies to see if USB controller is enabling power?Maybe measure power net VMAIN - it should have the same voltage (or near same) as the supplied VBUS.  Or you can measure any of the other on-board regulators.

    Regards

    Shankari G

  • @Rober Can you specify where the measurement points are located?

  • @ Yes, manually pulling J17 PIN1 to GND allows the development board to hard reboot, but the lab's programmable voltages don't have a GND connector, so how can I program remotely to pull PIN1 to GND?

  • Measurement probe point is C263.  When you supply 20V, do you measure 20V across the capacitor?

  • Reply for:

    Measurement probe point is C263....

    -------------------------------------------------

    Hi @Robert

    I measured the voltage across C263 with VDC=20 as follows:
    QADC-65-20-08CB: Vc623=1.9V
    Lab voltage: Vc623=1.3V

  • Not sure I understand the measurements, and I expected 20VDC (or close to 20V) from approved USB supply.  Are you measuring correct location?  I expect the USB power detection circuitry is not detecting the bench 20V power supply as a valid USB supply and is not enable power to the EVM.

  • Since board operates correctly from approved USB supply, can lab bench drive a voltage (say 5V) to J17 pin 1 to turn on and drive 0V to J17 pin 1 to turn off?

  • Sorry for my mistake, the correct measurements are as follows:

    QADC-65-20-08CB: Vc623=19.1V
    Lab voltage: Vc623=1.3V

  • Reply for:

    Since board operates correctly from approved USB supply....

    -----------------------------

    Hi Rober

        OK, according to this operation to realize "programmable power supply remote control equipment hard start" is wok.

    However, if the device is not started for a long time (i.e., the USB power is on and J17 PIN1 is connected to 0V), will it affect the life of the device?

  • EVM Lifetime should NOT be impacted by leaving USB power enabled but EVM powered off using J17.