• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 534 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.

RTOS/AM5718: NIMU error

Arpita Jena
Expert 1055 points

Part Number: AM5718
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hi All,

We are using CCS v 7.7 and pdk_am57xx_1_0_10 along with AM5718 EVM.

The example "NIMU_BasicExample_idkAM571x_armExampleproject" works fine with EVM but when we integrate the same with our custom application it doesn't work(hangs).Below is the debug print of the custom application with NIMU module integrated.

 

Ethernet Configuration Done!!

SetPhyMode:000021e1 Auto:1, FD10:64, HD10:32, FD100:256, HD100:128, FD1000:8192 LPBK:0

SYS/BIOS Ethernet/IP address I/F 1: 192.168.2.4
SetPhyMode:000021e1 Auto:1, FD10:64, HD10:32, FD100:256, HD100:128, FD1000:8192 LPBK:0

Can anyone please help us debugging this ?

Thanks and regards

Arpita Jena

  • 0
    Expert 1055 points

    Hii

    Sorry for the wrong info.

    The CCS version we are using is  7.4.

    NOTE :  RTOS processor sdk v 4.0 0

    Thanks

    Arpita Jena

  • 0 in reply to Arpita Jena
    TI__Guru* 95265 points

    Hi,

    I assumed you still used the same AM571x IDK board for the your own application. There is no change to the MDIO, CPSW and NIMU driver. If the original NIMU_BasicExample_idkAM571x_armExampleproject worked as it is, at least you will see some UART printf like below:

    SetPhyMode:000021e1 Auto:1, FD10:64, HD10:32, FD100:256, HD100:128, FD1000:8192 LPBK:0

    SetPhyMode:000021e1 Auto:1, FD10:64, HD10:32, FD100:256, HD100:128, FD1000:8192 LPBK:0
    ENETPHY_FindingState: PhyNum: 0
    ENETPHY_FindingState: PhyNum: 1
    ENETPHY_DisablePhy(0)
    Enable Phy to negotiate external connection
    NWAY Advertising: FullDuplex-1000 FullDuplex-100 HalfDuplex-100 FullDuplex-10 HalfDuplex-10
    ENETPHY_DisablePhy(1)
    Enable Phy to negotiate external connection
    NWAY Advertising: FullDuplex-1000 FullDuplex-100 HalfDuplex-100 FullDuplex-10 HalfDuplex-10
    Negotiated connection: FullDuplex 1000 Mbs

    This indicated the PHY is connected to the outside network. And you should be able to ping the EVM.

    I have no knowledge of your application, but I expect this application is LAYER 3 or higher network protocol, it should not change the L2 switch and PHY configuration, so I expect you still have the same Negotiated connection to the outside world and still be able to ping it. If not, your application must be crashed somewhere. Those print came from pdk_am57xx_1_0_14\packages\ti\board\src\idkAM571x. You can set some break point and debug if those get called.

    There are also some common tips for debug a RTOS application: http://processors.wiki.ti.com/index.php/Processor_SDK_RTOS:_TI_RTOS_Tips_And_Tricks#Debugging

    Regards, Eric

     

  • 0 in reply to lding
    Expert 1055 points

    Hi Eeic,

    Example code is working as it is on EVM. When i try to add Example code for Ethernet in my custom application, we are not getting prints as you mentioned. Only print which we are getting is as below.

    --

    SetPhyMode:000021e1 Auto:1, FD10:64, HD10:32, FD100:256, HD100:128, FD1000:8192LPBK:0

    --

    Will try with the breakpoints and update you soon.

    Thanks and regards

    Arpita Jena

  • 0 in reply to Arpita Jena
    Expert 1055 points

    Hiii,

    One more observation :

    We have added prints and checked once again.Now, the custom application is not going inside the NIMU_poll () function, but its returning properly from NIMU_Start() function.

    Thanks

    Arpita Jena

  • 0 in reply to lding
    Expert 1055 points

    Hii Eric,

    Thanks for your support.We are able to resolve the issue.

    After adding var SemiHostSupport = xdc.useModule('ti.sysbios.rts.gnu.SemiHostSupport') to the .cfg file it works fine.

    We are able to ping the EVM also.

    Thanks and Regards...

    Arpita Jena