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: TDA4VM demo OSPI startup

Part Number: TDA4VM
Other Parts Discussed in Thread: UNIFLASH

Hello:

    I encountered the following two problems when using TDA4VM demo board to verify OSPI startup.

    The document that I refer to is CAN Response and Bootloader Demo Application.

    1. Under the mcusw / build path, execute the following command, can_ boot_ app_ mcu_ RTOS firmware is not generated.I want to know why?

     make -s -j can_boot_app_mcu_rtos BOARD=j721e_evm SOC=j721e BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=tirtos

    2. How do I write needed binaries to OSPI?

    >>
    coresdk_rtos_jacinto_xx_yy_xx_bb/pdk_jacinto_07.x.x/packages/ti/boot/sbl/binary/j721e_evm/cust/bin/sbl_cust_img_mcu1_0_release.tiimage @ 0
    coresdk_rtos_jacinto_xx_yy_xx_bb/pdk_jacinto_07.x.x/packages/ti/drv/sciclient/soc/V1/tifs.bin @ 80000
    coresdk_rtos_jacinto_xx_yy_xx_bb/mcusw/binary/can_boot_app_mcu_rtos/bin/j721e_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage @ 100000
    coresdk_rtos_jacinto_xx_yy_xx_bb/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/binary/bin/j721e_evm/multicore_MCU2_0_MCU2_1_stage1.appimage @ 1fc0000
    coresdk_rtos_jacinto_xx_yy_xx_bb/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/binary/bin/j721e_evm/multicore_DSPs_MCU3_0_MCU3_1_stage2.appimage @ 27c0000
    coresdk_rtos_jacinto_xx_yy_xx_bb/mcusw/mcuss_demos/boot_app_mcu_rtos/main_domain_apps/binary/bin/j721e_evm/multicore_MPU1_0_stage3.appimage @ 37c0000

    It's urgent. I need your help. Thank you!

     

  • Hi,

    1. Did the compilation finish successfully? From the documentation, the output should have been placed in the following directory:

    "The output appimage "can_boot_app_mcu_rtos_mcu1_0_release.appimage" will be placed in coresdk_rtos_jacinto_xx_yy_xx_bb/mcusw/binary/can_boot_app_mcu_rtos/bin/$board directory."

    2. There is an FAQ on how to flash OSPI on TDA4VM board here:

    e2e.ti.com/.../faq-how-to-flash-ospi-using-ccs-on-tda4x-dra82-evm

    Regards,

    Erick

  • Hi,

    You can use the UNIFLASH too, documented here - https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/pdk_jacinto_07_03_00_29/docs/userguide/jacinto/board/uniflash.html to flash to OSPI.

    Run the below commands from the uniflash directory: (modify paths as per your local machine)

    dslite.bat –-mode processors -c COM7 -f C:\ti\uniflash_6.2.0\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\pdk\packages\ti\boot\sbl\binary\j721e_evm\cust\bin\sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\pdk\packages\ti\drv\sciclient\soc\V1\tifs.bin -d 3 -o 80000
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\mcusw\binary\can_boot_app_mcu_rtos\bin\j721e_evm\can_boot_app_mcu_rtos_mcu1_0_release.appimage -d 3 -o 100000
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\mcusw\mcuss_demos\boot_app_mcu_rtos\main_domain_apps\binary\bin\j721e_evm\multicore_MCU2_0_MCU2_1_stage1.appimage -d 3 -o 1fc0000
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\mcusw\mcuss_demos\boot_app_mcu_rtos\main_domain_apps\binary\bin\j721e_evm\multicore_DSPs_MCU3_0_MCU3_1_stage2.appimage -d 3 -o 27c0000
    dslite.bat –-mode processors -c COM7 -f X:\processor-sdk-rtos\mcusw\mcuss_demos\boot_app_mcu_rtos\main_domain_apps\binary\bin\j721e_evm\multicore_MPU1_0_stage3.appimage -d 3 -o 37c0000

    Regards

    Karan

  • Hi,Erick

        The first step in the e2e.ti.com/.../faq-how-to-flash-ospi-using-ccs-on-tda4x-dra82-evm document, in pdk/packages/ti/board/utils/uniflash/target/build/uart_make.mk file,do not have USE_CCS flag,so can't flash OSPI using CCS.

    Is there any other way in the Ubuntu environment?

    Regards,

    Ming fei

  • Hi

    I need to flash OSPI in Ubuntu environment. Can I use uniflash? If yes, how can I get the installation package of uniflash

    Regards

    Ming fei

  • Hi Ming fei,

    You can use UNIFLASH on linux as well. The dslite.bat now replaces with dslite.sh and the COM7 replaces with the /dev/ttyUSBx corresponding to the MCU UART. (2nd UART when you connect to J43)

    Regards

    Karan

  • Hi Karan,

    I have installed UNIFLASH_6.4.0 on Linux.But when I tried to open it, the following error occurred,Untrusted application initiator.

    Is there any way to solve it?

    Regards

    Ming fei

  • Hi,Erick

    Thank you for your answer.I have another question.

    sbl_ cust_ img firmware could not be generated.When I compile it, an error will be reported during linking,and don't exist SBL_ cust_ img_ mcu1_ 0_ Release.xer5f, under the following path:

    /PSDKRA/pdk_jacinto_07_03_00_29/packages/ti/boot/sbl/binary/j721e_evm/cust/bin/sbl_cust_img_mcu1_0_release.xer5f.

    Do I have any extra work to do before compiling it ?

    Regards,

    Ming fei

  • Hi,Karan

    Thank you for your answer.I have another question.

    sbl_ cust_ img firmware could not be generated.When I compile it, an error will be reported during linking,and don't exist SBL_ cust_ img_ mcu1_ 0_ Release.xer5f, under the following path:

    /PSDKRA/pdk_jacinto_07_03_00_29/packages/ti/boot/sbl/binary/j721e_evm/cust/bin/sbl_cust_img_mcu1_0_release.xer5f.

    Do I have any extra work to do before compiling it ?

    Regards,

    Ming fei

  • Hi,Karan

    When I use uniflash, which device name should I choose? There is no TDA4 in the list.

    Regards

    Ming fei

  • Hi Ming fei,

    You can use the command as I mentioned before, are you seeing issues with that? UNIFLASH supports TDA4 flashing of eMMC boot0 and OSPI flashes.

    Please see https://www.ti.com/lit/an/spracy5/spracy5.pdf .

    Regards

    Karan

  • Hi Karan

    I have burned the following firmware into OSPI according to the method you said before.But the board still didn't start, only the current value increased from 0.46 to 0.63. And there is no log output.What's the problem?

    1. dslite.bat –-mode processors -c COM11 -f C:\ti\uniflash_6.4.\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0

    2. dslite.bat –-mode processors -c COM11 -f C:\OSPI\sbl_cust_img\sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0
    3. dslite.bat –-mode processors -c COM11 -f C:\OSPI\tifs\tifs.bin -d 3 -o 80000    4. dslite.bat –-mode processors -c COM11 -f C:\OSPI\can_boot_app_mcu_rtos\can_boot_app_mcu_rtos_mcu1_0_release.appimage -d 3 -o 100000
    5. dslite.bat –-mode processors -c COM11 -f C:\OSPI\stage\multicore_MCU2_0_MCU2_1_stage1.appimage -d 3 -o 1fc0000
    6. dslite.bat –-mode processors -c COM11 -f C:\OSPI\stage\multicore_DSPs_MCU3_0_MCU3_1_stage2.appimage -d 3 -o 27c0000    7. dslite.bat –-mode processors -c COM11 -f C:\OSPI\stage\multicore_MPU1_0_stage3.appimage -d 3 -o 37c0000  

    Regards

    Ming fei

  • Hi Karan

    Please help me see what's going on, thank you!

    Regards

    Ming fei

  • Hi Ming fei,

    1. Can you please tell me which UART are you trying to look at the logs on? It should be the MCU UART (2nd instance when you connect to J43 connector on the EVM).

    2. Also, can you send the output logs of the uniflash commands?

    3. Just to make sure, you are doing this experiment on the TDA4 EVM and NOT a custom board?

    Regards

    Karan

  • Hi Ming fei,

    1. Can you please tell me which UART are you trying to look at the logs on? It should be the MCU UART (2nd instance when you connect to J43 connector on the EVM).

    2. Also, can you send the output logs of the uniflash commands?

    3. Just to make sure, you are doing this experiment on the TDA4 EVM and NOT a custom board?

    Regards

    Karan

  • Hi Karan

    1. Yes, I use MCU UART.

    2.

    C:\ti>cd uniflash_6.4.0

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\ti\uniflash_6.4.0\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\ti\uniflash_6.4.0\processors\FlashWriter\j721e_evm\uart_j721e_evm_flash_programmer_release.tiimage -i 0

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .tiimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Downloading Flash Programmer..

    Transferring File of size 318807 bytes
    File Transfer complete!

    Enabling System firmware transfer!!!
    Header Transfer complete
    Transferring System Firmware..
    Transferring File of size 263072 bytes
    File Transfer complete!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\sbl_cust_img\sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\sbl_cust_img\sbl_cust_img_mcu1_0_release.tiimage -d 3 -o 0

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .tiimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 264463 bytes
    Flash Programming Success!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\tifs\tifs.bin -d 3 -o 80000
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\tifs\tifs.bin -d 3 -o 80000

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .bin

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 263072 bytes
    Flash Programming Success!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\can_boot_app_mcu_rtos\can_boot_app_mcu_rtos_mcu1_0_release.appimage -d 3 -o 100000
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\can_boot_app_mcu_rtos\can_boot_app_mcu_rtos_mcu1_0_release.appimage -d 3 -o 100000

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .appimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 258720 bytes
    Flash Programming Success!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\stage\multicore_MCU2_0_MCU2_1_stage1.appimage -d 3 -o 1fc0000
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\stage\multicore_MCU2_0_MCU2_1_stage1.appimage -d 3 -o 1fc0000

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .appimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 91664 bytes
    Flash Programming Success!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\stage\multicore_DSPs_MCU3_0_MCU3_1_stage2.appimage -d 3 -o 27c0000
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\stage\multicore_DSPs_MCU3_0_MCU3_1_stage2.appimage -d 3 -o 27c0000

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .appimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 524840 bytes
    Flash Programming Success!

    C:\ti\uniflash_6.4.0>dslite.bat --mode processors -c COM17 -f C:\OSPI\stage\multicore_MPU1_0_stage3.appimage -d 3 -o 37c0000
    Executing the following command:
    > C:\ti\uniflash_6.4.0\processors\ProcessorSDKSerialFlash.exe -c COM17 -f C:\OSPI\stage\multicore_MPU1_0_stage3.appimage -d 3 -o 37c0000

    For more details and examples, please refer to the UniFlash Quick Start guide.

    The file extension is .appimage

    ----------------------------------------------------------------------------
    ProcessorSDKSerialFlash CLI Tool
    Copyright (C) 2017-2021 Texas Instruments Incorporated - http://www.ti.com/
    Version 1.5.0.0
    ----------------------------------------------------------------------------
    Transferring the Image to Flash Programmer..

    Transferring Header Information..
    Header Transfer Complete!

    Flashing Image of size 231024 bytes
    Flash Programming Success!

    3. I'm sure I'm using tda4 EVM.

    Regards

    Ming fei

  • Hi Ming fei,

    I see your commands before using COM11 and now using COM17. Which are the two UART instances which come up when you connect to just the MCU UART?

    Based on your Uniflash logs, the flashing is successful. Can you send the me the diff on top of the SDK you have and the build commands you use to build the can_boot_app_mcu_rtos?

    Regards

    Karan

  • Hi Karan,

    1. Every time I connect to MCU UART, because it is at different times, the virtual UART number is different.

    2. Compile can_ boot_ app_ mcu_ RTOS the command I use is :

    make -s -j can_boot_app_mcu_rtos BOARD=$board SOC=$soc BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=tirtos

    Regards

    Ming fei

  • Hi Karan

    Now I have a new problem , execute this command . / makemulticore.sh j721e_ EVM, unable to generate the following three firmware: multicores_ MCU2_ 0_ MCU2_ 1_ stage1.appimage,multicore_ DSPs_ MCU3_ 0_ MCU3_ 1_ stage2.appimage,multicore_ MPU1_ 0_ Stage3.appimage, I don't know why?These three firmware are required.

    I refer to this document:

    file:///home/tda4/Code/PSDKRA/mcusw/mcal_drv/docs/drv_docs/demo_boot_app_mcu_rtos_top.html#demo_boot_app_mcu_rtos_building_can_boot_app_mcu_rtos

    Creating RTOS appimage for main domain cores

    Regards

    Ming fei

  • Hi Karan

    Please help me see what's going on, thank you!

    Regards

    Ming fei

  • Hi Ming fei

    Now I have a new problem , execute this command . / makemulticore.sh j721e_ EVM, unable to generate the following three firmware: multicores_ MCU2_ 0_ MCU2_ 1_ stage1.appimage,multicore_ DSPs_ MCU3_ 0_ MCU3_ 1_ stage2.appimage,multicore_ MPU1_ 0_ Stage3.appimage, I don't know why?These three firmware are required.

    What is the error you are seeing when running the makemulticore.sh script? Is there some dependency which is not built and hence you are not able to create the final appimages?

    Regards

    Karan