• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 104 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Periodic tasks cannot be started in can_boot_mcu_rtos

june lee
Prodigy 220 points
Part Number: TDA4VM

Hello TI,

I use TDA4VM chip, J721E, PDK version 8.2 for development.

I want to execute some periodic tasks in can_boot_mcu_rtos. Use TaskP and SemaphoreP for Task creation and cycle control.

The following tests are currently performed:

1. When adding spi references to INCLUDE_INTERNAL_INTERFACES and COMP_LIST_COMMON in mcusw/mcuss_demos/boot_app_mcu_rtos/makefile, periodic tasks can run normally.

2. When the spi reference is removed from INCLUDE_INTERNAL_INTERFACES and COMP_LIST_COMMON in mcusw/mcuss_demos/boot_app_mcu_rtos/makefile, periodic tasks cannot run normally.

When spi is not referenced, it takes about 0.8s for can_boot to start other cores,

When spi is referenced, the time for can_boot to start other cores is significantly slower, taking about 4s, which is unacceptable.

Therefore, we need to remove the reference to spi in the makefile.

But this results in periodic tasks not running properly.

Does TI have any relevant information that can help us solve this problem?

  • 0
    TI__Guru**** 477425 points

    Hi June Lee,

    june lee said:
    2. When the spi reference is removed from INCLUDE_INTERNAL_INTERFACES and COMP_LIST_COMMON in mcusw/mcuss_demos/boot_app_mcu_rtos/makefile, periodic tasks cannot run normally.

    Did not get it. Why does periodic task have dependency on SPI? Could you please elaborate? Is your periodic task executed from SPI callback or something? or are you using timer ISR and semaphore to unblock task for periodic task? Also what is the periodic task that you are doing? 

    june lee said:
    When spi is referenced, the time for can_boot to start other cores is significantly slower, taking about 4s, which is unacceptable.

    Can you please provide some more information, as to what is the boot mode? Which SPI instance are you using? When do you load the other firmwares on the cores? 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Prodigy 220 points

    Hello Brijesh,

    I tested the TI original code, the periodic task can be executed, I modified my makefile to compare, and the problem has been solved.

    thank you.