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.
Tool/software:
Hi,Ti expert
I want to accurately measure the time from power on to SBL and then to app startup. How should I do this?
I refer to this link: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1396841/tda4vm-sbl-boot-time-measurement
But I don’t quite understand how to test it.
MCU_PROZ_OUT to MCU_RESETSTATz it take 0.63ms. how to test it?
ROM: init + SBL load from OSPI it take 12.36ms . how to test it?
Is there any document?Which test point i can use on tda4vm board?
Best Regard
Eason
Hi,
Now I have a test, but the data is different from the official data, and there is a lot of difference:
The reset pin:
Test result:
From Reset to the frist line code in sbl_main.c, It take 54ms. This is obviously abnormal. Is there any way to reduce the time it takes for the reset signal to reach the first line of sbl code?
Best Regards
Eason
Hi,
MCU_PROZ_OUT to MCU_RESETSTATz it take 0.63ms. how to test it?
Please refer to the steps below.let us know If this helps.
******************************Boot Performance test procedure************************ step 1: Build sbl_boot_perf_cust_img_mcu1_0_release.tiimage by using the following command. make BOARD=<board_name> sbl_boot_perf_cust_img -sj you can find the image in <pdk install path>/pdk/packages/ti/boot/sbl/binary/<board_name>/cust/bin/ step 2: Build sbl_baremetal_boot_perf_<board_name>_mcu1_0TestApp_release.appimage by using the following command make BOARD=<board_name> CORE=mcu1_0 sbl_boot_perf_test -sj you can find the image in <pdk install path>/pdk/packages/ti/boot/sbl/example/k3MulticoreApp/binary/<soc_name>/ step 3: Change the boot switch settings to UART bootmode. step 4: Flash uart flash programmer (below commands are suitable for linux PC) sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <path to uniflash tool>/uniflash_8.0.0/processors/FlashWriter/<board_name>/uart_<board_name>_flash_programmer_release.tiimage -i 0 example: sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f <path to uniflash tool>/uniflash_8.7.0/processors/FlashWriter/j721e_evm/uart_j721e_evm_flash_programmer_release.tiimage -i 0 step 5: Flash sbl_boot_perf_cust_img_mcu1_0_release.tiimage at 0x0 sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/boot/sbl/binary/<board_name>/cust/bin/sbl_boot_perf_cust_img_mcu1_0_release.tiimage -d 3 -o 0 example: sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f <pdk>/packages/ti/boot/sbl/binary/j721e_evm/cust/bin/sbl_boot_perf_cust_img_mcu1_0_release.tiimage -d 3 -o 0 step 6: Flash tifs.bin at 0x80000 for j721e : sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/drv/sciclient/soc/V1/tifs.bin -d 3 -o 80000 example: sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f <pdk>/packages/ti/drv/sciclient/soc/V1/tifs.bin -d 3 -o 0x80000 step 7: Flash sbl_baremetal_boot_perf_<board_name>_mcu1_0TestApp_release.appimage at 0x100000 sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/boot/sbl/example/k3MulticoreApp/binary/<SOC>/sbl_baremetal_boot_perf_test_<board_name>_mcu1_0TestApp_release.appimage -d 3 -o 100000 example: sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f <pdk>/packages/ti/boot/sbl/example/k3MulticoreApp/binary/j721e/sbl_baremetal_boot_perf_j721e_evm_mcu1_0TestApp_release.appimage -d 3 -o 0x100000 step 8: Flash NOR spi pattern for j721e : sudo <path to uniflash tool>/uniflash_8.0.0/dslite.sh --mode processors -c /dev/ttyUSB* -f <pdk install path>/pdk/packages/ti/board/src/flash/nor/ospi/nor_spi_patterns.bin -d 3 -o 3FE0000 example: sudo ./dslite.sh --mode processors -c /dev/ttyUSB1 -f <pdk>/packages/ti/board/src/flash/nor/ospi/nor_spi_patterns.bin -d 3 -o 3FE0000 step 9: /dev/ttyUSB* will be the second instance of MCU uart. step 10: Change the boot switch settings to OSPI boot. step 11: Power ON the board step 12: If you get some logs and All tests passed at the end on MCU uart then you can mark this test as passed. step 13: PASS string : Boot Performance test has passed
Regards,
Karthik
Hi,Karthik
It take 37.55ms。
But in fact, I need to test by pulling IO on the evm board. Is there any way to do this?
Best Regards
Eason
Hi, Karthik
which test point on tda4vm evm board is MCU_PROZ_OUT ?
which test point on tda4vm emv is MCU_RESETSTATz ?
I will use Oscilloscope and test by myself.
Best Regards
Eason
Hi, expert:
Can Ti expert give some suggestions which I can accurately measure the startup time from power on to sbl from an oscilloscope?
Best Regards
Eason
Hi,
Can Ti expert give some suggestions which I can accurately measure the startup time from power on to sbl from an oscilloscope?
I'll look into this more closely and get back to you.
Regards,
Karthik
Hi, Karthik
I'll look into this more closely and get back to you.
Thanks
Best Regards
Eason
Hi Eason,
which test point on tda4vm evm board is MCU_PROZ_OUT ?
which test point on tda4vm emv is MCU_RESETSTATz ?
Please refer to the following TI EVM Testing Point.
MCU_RESETSTATz ----- TP116 MCU_PORZ_OUT ----- TP117
Regards,
Karthik
Hi, Karthik
Please refer to the following TI EVM Testing Point.
Fullscreen123MCU_RESETSTATz ----- TP116MCU_PORZ_OUT ----- TP117XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXFullscreen123MCU_RESETSTATz ----- TP116MCU_PORZ_OUT ----- TP117XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXMCU_RESETSTATz ----- TP116 MCU_PORZ_OUT ----- TP117
Regards,
Ok,Thanks
Best Regard
Eason