TDA4VE-Q1: program efuse through external SD card

Part Number: TDA4VE-Q1

Tool/software:

Dear Customer,

We are booting from an external SD card to program internal Fuse. We have some questions, please help check. 

We see log from MCU_UART0_TX pin, the log is " OPT Keywriter Version: 02.00.00.00 (Apr 18 2025 - 10:22:16)"

After we get this log, there is still signal output from MMC1_CLK pin, the MMC1_CMD pin keeps high, no extra CMD. 

Does the programming process finished or meet any issue, what could be the reason for such issue?

What is the full log if program success? Thanks.

  • Hi Grace,

    full log would be as below.  

    First, can you confirm if VPP (#H22) is supplied to 1.8V?

    regards,

    Lloyd

  • VPP (#H22) is supplied to 1.8V, but H22 and V22 are connect together with VDDA_xx signals. Will this cause any issue? 

    At which stage shall we power up 1.8v? Our current sequence is 3.3V -> 1.8V -> 0.8V -> 0.85V -> 1.1V -> release RST. Thanks.

  • HI Zhang,

    First we need to understand why TIFS version logs are not coming. I assume you are using wrong TIFS binary.

    Can you help me with couple of question :

    • What is device type , You can use this FAQ to get the device type.
    • Please share complete steps , which you followed for building keywriter application.

    Regards
    Diwakar

  • Hello Diwakar, The device type is HS-FS. I am still waiting for the confirm about the SD create steps. I have read back the SD card content. Can I confirm the TIFS by the read back content of the SD card? Thanks.

  • HI Zhang,

    I am still suspecting TIFS key writer binary which they have used. Once we have the information on steps followed to build keywriter image we can debug further.

    Also can you add a dummy loop in the main function and then use JTAG to see where exactly is getting stuck.

    Regards
    Diwakar

  • They confirmed that there is no problem with the SD card they are using.
    I used the same SD card on a customer board and got the following UART logs.
    Could you please check what else could be causing the issue?

    [First attempt - success]


    OTP Keywriter Version: 02.00.00.00 (Apr 18 2025 - 10:22:16)

    OTP Keywriter ver: 8.4.6-v08.04_keywriter (Jolly J
    OTP_SciClientInit
    READ BOARD_MCU_GPIO12_PINMUX_ADDR: 0x00050007
    VPP enable
    Key programming sequence initialted
    Taking OTP certificate from 0x41c7f004
    Debug response: 0x0
    Key programming sequence completed

    [retry]

    OTP Keywriter Version: 02.00.00.00 (Apr 18 2025 - 10:22:16)

  • HI 

    [First attempt - success]

    In the first attempt as you are getting a debug response as 0x0, that means fusing of the keys is successful and the device got converted to HS-SE.

    If you re run the keywriter on the same device again it will not work. Keywirter is intended to use on HS-FS device only.

    Key programming sequence initialted
    Taking OTP certificate from 0x41c7f004
    Debug response: 0x0
    Key programming sequence completed

    That is the reason my first question was what is the device type.You can follow the FAQ to get the device type.

    • What is device type , You can use this FAQ to get the device type.

    Regards
    Diwakar

  • Hello Diwakar,

    I can get below log, does it mean program failed? Thanks.

    [16:23:15.461]IN←◆OTP Keywriter Version: 02.00.00.00 (Apr 18 2025 - 10:22:16)

    OTP Keywriter ver: 8.4.6-v08.04_keywriter (Jolly J
    OTP_SciClientInit
    READ BOARD_MCU_GPIO12_PINMUX_ADDR: 0x00050007
    VPP enable
    Key programming sequence initialted
    Taking OTP certificate from 0x41c7f004

    [16:23:15.912]IN←◆Sciclient_otpProcessKeyCfg returns: -1
    Debug response: 0x10000
    Key programming sequence completed

    [16:24:26.363]IN←◆\0

     

  • To get this log by changed VDD_MCU = VDD_CORE = 0.8V, VDDAR_MCU = VDDAR_CORE = 0.85V, what could be the reason for the program failure? Thanks.

  • HI Zhang,

    I am not the hardware expert , but just want to understand why we have made above changes as we already have working case here :  RE: TDA4VE-Q1: program efuse through external SD card 

    Regards
    Diwakar