The TI E2E™ design support forums will undergo maintenance from July 11 to July 13. If you need design support during this time, open a new support request with our customer support center.

  • State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 313 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

TDA4VM: Execute external binary using SBL

PROCESSOR-SDK-J721E: MCU1_0 Application Development with SYSFW components

JK
Mastermind 8883 points
Part Number: PROCESSOR-SDK-J721E

Hi 

I have a question that customer is still facing.

I have looked into the Develop Notes, 8.3 MCU1_0_Application Development with SYSFW chapter.
(https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/developer_notes_mcu1_0_sysfw.html)

Regarding the requirement of Application running on MCU1_0, the following SYSDW components need to run from MCU1_0 side instead of DMSC.

  • SCISERVER
  • Resource Management(RM) Service
  • Power Management(PM) Service

Could you please let me know where to check those components' libraries are properly linked into MCU1_0 binary? for both SDK7.0 and SDK7.1-SDK7.3.

And also let me know the associated initialization function to start these services in the example code if available.

Thanks.

  • 0
    Mastermind 8883 points

    If possible, please also let me know where to find the relevant code from PROCESSOR-SDK Version 7.0 since Customer reported MCU1_0 Boot Failure issue both 7.0 and 7.1. Their official development version is based on 7.0. 

    And I could not find SCISERVER on SDK7.0. I supposed the same components need to be exist under SDK7.0 as well. Also appropriate service init code should be called before sciclient API is used. 

    Please do helpful even the original reported issue is still reproducible.

    If TI recommends for Customer to use SDK 7.1, They have to discuss with their client to move the baseline to 7.1.

    Hence TI's prompt feedback is required. 

    Thanks.

  • 0 in reply to JK
    TI__Guru* 77574 points

    Hi Jack,

    JK said:

    If possible, please also let me know where to find the relevant code from PROCESSOR-SDK Version 7.0 since Customer reported MCU1_0 Boot Failure issue both 7.0 and 7.1. Their official development version is based on 7.0. 

    And I could not find SCISERVER on SDK7.0. I supposed the same components need to be exist under SDK7.0 as well. Also appropriate service init code should be called before sciclient API is used. 

    The concept of SciServer is there only from SDK7.1 and onwards. You will not find it in SDK7.0.

    JK said:
    Could you please let me know where to check those components' libraries are properly linked into MCU1_0 binary? for both SDK7.0 and SDK7.1-SDK7.3.

    For SDK7.1 and onwards you can find the libraries path in the PDK sciclient user guide - 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/family_cfg/jacinto/index_modules_sciclient_jacinto.html slightly below Fig 4.3.

    JK said:
    And also let me know the associated initialization function to start these services in the example code if available.

    You can refer any SDK7.1 (or later) example for MCU1_0. 

    Call & definition: <SDK_PATH>/pdk*/packages/ti/drv/ipc/examples/common/src/main_tirtos.c :: Ipc_setupSciServer()

    Call: <SDK_PATH>/vision_apps/apps/basic_demos/app_tirtos/tirtos_linux/mcu1_0/main.c :: appSciserverInit()

    Definition: <SDK_PATH>/vision_apps/utils/sciserver/src/app_sciserver.c :: appSciserverInit()

    This sequence is also documented in https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos/docs/user_guide/developer_notes_mcu1_0_sysfw.html#functions-to-call 

    Regards,

    Karan