• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 308 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: ethfw hangs after BIOS_start

Jing He
Prodigy 10 points

Part Number: TDA4VM

Hi master,

       I used SDK 07_01_00

      First, when i use prebuild image in sdk to make SD card. I can see ethfw log in ttyUSB2 after boot;

      Then, I compiled a new ethfw, without any change, Then i copy   debug/app_remoteswitchcfg_server_strip.xer5f  to  /lib/firware/ethfw;

      After boot, I can't see any ethfw log in ttyUSB2;

      So I add same log in ethfw main function, I found the log is correct before BIOS_start, and after BIOS_start is called,  no more log will output;

     Can you give me some advice?

Thanks.

  • +1
    TI__Mastermind 37435 points

    Hi,

    Please refer to this FAQ

    You need to build the EthFW application under vision_apps in SDK. Refer to this user guide and then copy that application in lib/firmware

    You can also use the command make vx_app_tirtos_linux_mcu2_0 in <SDK_INSTALL_DIR>/vision_apps , it will generate the binary under vision_apps/out folder.

    Regards

    Vineet

  • +1 in reply to Vineet Roy
    Prodigy 10 points

    Hi Vineet

        Thanks for your reply；

        I have tried enable ethfw in vision_apps, follow the user guide; 

        But when I power on the EVM, and let the OS come up; I still can't find eth1;

        So I trace the driver code, found that the driver is waiting for the response  of RPMSG_KDRV_TP_ETHSWITCH_ATTACH_EXT;

        I can see just one log in ttyUSB2

           

     [NIMU_NDK] ENET has been started successfully

        

         After OS come up, I also run the ./vision_apps_init.sh script.  linux log is 

         

    [MCU2_0]     18.633945 s: REMOTE_SERVICE: Init ... !!!
[MCU2_0]     18.635382 s: REMOTE_SERVICE: Init ... Done !!!
[MCU2_0]     18.635447 s: ETHFW: Init ... !!!
[MCU2_0]     18.668782 s: CPSW_9G Test on MAIN NAVSS
[MCU2_0]     18.686270 s: EnetPhy_bindDriver: PHY 12: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK
[MCU2_0]     18.686506 s: EnetPhy_bindDriver: PHY 0: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK
[MCU2_0]     18.686741 s: EnetPhy_bindDriver: PHY 3: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK
[MCU2_0]     18.686953 s: EnetPhy_bindDriver: PHY 15: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK
[MCU2_0]     18.687011 s: PHY 0 is alive
[MCU2_0]     18.687040 s: PHY 3 is alive
[MCU2_0]     18.687063 s: PHY 12 is alive
[MCU2_0]     18.687081 s: PHY 15 is alive
[MCU2_0]     18.687101 s: PHY 23 is alive
[MCU2_0]     18.688821 s: ETHFW: Version   : 0.01.01
[MCU2_0]     18.688902 s: ETHFW: Build Date: Mar 19, 2021
[MCU2_0]     18.688933 s: ETHFW: Build Time: 14:29:20
[MCU2_0]     18.688952 s: ETHFW: Commit SHA: 
[MCU2_0]     18.689015 s: ETHFW: Init ... DONE !!!
[MCU2_0]     18.689036 s: ETHFW: Remote server Init ... !!!
[MCU2_0]     18.690288 s: Remote demo device (core : mcu2_0) .....
[MCU2_0]     18.690347 s: ETHFW: Remote server Init ... DONE !!!
[MCU2_0]     18.710180 s: Host MAC address: 70:ff:76:1d:92:c2
[MCU2_0]     18.740884 s: DSS: Init ... !!!
[MCU2_0]     18.740942 s: DSS: Display type is eDP !!!
[MCU2_0]     18.740965 s: DSS: SoC init ... !!!
[MCU2_0]     18.740983 s: SCICLIENT: Sciclient_pmSetModuleState module=152 state=2
[MCU2_0]     18.742382 s: SCICLIENT: Sciclient_pmSetModuleState success
[MCU2_0]     18.742426 s: SCICLIENT: Sciclient_pmSetModuleState module=297 state=2
[MCU2_0]     18.744525 s: SCICLIENT: Sciclient_pmSetModuleState success
[MCU2_0]     18.744556 s: SCICLIENT: Sciclient_pmSetModuleState module=151 state=2
[MCU2_0]     18.746006 s: SCICLIENT: Sciclient_pmSetModuleState success
[MCU2_0]     18.746037 s: SCICLIENT: Sciclient_pmSetModuleClkParent module=152 clk=9 parent=11
[MCU2_0]     18.746494 s: SCICLIENT: Sciclient_pmSetModuleClkParent success
[MCU2_0]     18.746521 s: SCICLIENT: Sciclient_pmSetModuleClkParent module=152 clk=13 parent=18
[MCU2_0]     18.747065 s: SCICLIENT: Sciclient_pmSetModuleClkParent success
[MCU2_0]     18.747093 s: SCICLIENT: Sciclient_pmSetModuleClkParent module=152 clk=1 parent=2
[MCU2_0]     18.747504 s: SCICLIENT: Sciclient_pmSetModuleClkParent success
[MCU2_0]     18.747534 s: SCICLIENT: Sciclient_pmSetModuleClkFreq module=152 clk=1 freq=148500000
[MCU2_0]     18.767028 s: SCICLIENT: Sciclient_pmSetModuleClkFreq success
[MCU2_0]     18.767058 s: SCICLIENT: Sciclient_pmModuleClkRequest module=152 clk=1 state=2 flag=0
[MCU2_0]     18.767503 s: SCICLIENT: Sciclient_pmModuleClkRequest success
[MCU2_0]     18.767532 s: DSS: SoC init ... Done !!!
[MCU2_0]     18.767555 s: DSS: Board init ... !!!
[MCU2_0]     18.767574 s: DSS: Turning on DP_PWR pin for eDP adapters ... !!!
[MCU2_0]     20.201587 s: Function:CpswProxyServer_attachExtHandlerCb,HostId:0,CpswType:6
[MCU2_1]      3.830788 s: CIO: Init ... Done !!!
[MCU2_1]      3.830858 s: ### CPU Frequency <ORG = 1000000000 Hz>, <NEW = 1000000000 Hz>
[MCU2_1]      3.830905 s: APP: Init ...test123 !!!
[MCU2_1]      3.830929 s: SCICLIENT: Init ... !!!
[MCU2_1]      3.832061 s: SCICLIENT: DMSC FW version [20.8.5--v2020.08b (Terrific Lla]
[MCU2_1]      3.832107 s: SCICLIENT: DMSC FW revision 0x14  
[MCU2_1]      3.832137 s: SCICLIENT: DMSC FW ABI revision 3.1
[MCU2_1]      3.832162 s: SCICLIENT: Init ... Done !!!
[MCU2_1]      3.832185 s: UDMA: Init ... !!!
[MCU2_1]      3.843529 s: UDMA: Init ... Done !!!

        1. How can I see more log info in rtos side?

        2.Why rtos side didnt response the RPMSG_KDRV_TP_ETHSWITCH_ATTACH_EXT request?

    Thanks