• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 444 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.

DRA829V: "Sciclient event config failed" on reboot

Joachim Wiesemann
Prodigy 160 points
Part Number: DRA829V

I'm currently running Ethernet (RTOS) tests on MCU2_0 / Main_Cortex_R5_0_0. (It's the only core I'm currently using.)

In CSS I use the lauch.js script to load the DMSC and the MCU1_0 sci server. Then I load the enet_lwip_example_freertos_mcu2_0_debug.xer5f.

When I reset the core and restart the program I get an Error:

[UDMA] [Error] Sciclient event config failed!!!

The only way to get the sample running again is to power down the board (E721_EVM) and start from scratch.

First the effort and the cycle times for testing are quite tedious and annoying. Second I fear that reseting the core in case of a severe problem would rendet it useless as it doesn't rebbot sucessfully.

Is there a way to sucessfully reboot the application?

  • 0
    TI__Intellectual 1400 points

    Hello,

    Can you provide further details such which SDK version are you using and if possible the output logs you are viewing on your terminal? Have you found that power cycling fixes the issue each time?


    Best,
    Kelvin

  • 0 in reply to Kelvin Ayala
    Prodigy 160 points

    Hello Kevin!

    It's PROCESSOR-SDK-RTOS-J721E, version 08_05_00_36.
    Power cycling the board works every time.

    Joachim

  • 0 in reply to Joachim Wiesemann
    TI__Intellectual 1400 points

    Hello Joachim,

    Thank you for providing me these details. We will be looking into the issue. I shall return with an update by 04/25/2023 on our findings from our side.

    In the meantime, may you please share any logs that were outputted during an unsuccessful and successful boot.

    Best,
    Kelvin

  • 0 in reply to Kelvin Ayala
    TI__Intellectual 1400 points

    Hello Joachim,

    I am still working on things on my end. Can you confirm that the pdk steps were followed and that this issue is regrettable each time?

    Best,
    Kelvin

  • 0 in reply to Kelvin Ayala
    Prodigy 160 points

    Hello Kevin,

    yes, the status is still the same: succesful boot after power up, same error every time I reboot without power down.

    Rebooting a processor without Ethernet but with Sciclient works. (Using CCS + XDS110 debugger: click Suspend, click CPU reset, click Restart, click Resume.)

    Log (sucessful):

    EnetBoard_setupPorts: 1 of 1 ports configurations found
    Starting lwIP, local interface IP is dhcp-enabled
    EnetMcm: CPSW_9G on MAIN NAVSS
    Mdio_open: MDIO manual mode enabled
    PHY 0 is alive
    PHY 3 is alive
    PHY 12 is alive
    PHY 15 is alive
    PHY 23 is alive
    EnetPhy_bindDriver: PHY 12: OUI:080028 Model:23 Ver:01 <-> 'dp83867' : OK
    Host MAC address: 70:ff:76:1e:c5:ba
    [LWIPIF_LWIP] Enet LLD netif initialized successfully
    status_callback==UP, local interface IP is 0.0.0.0
    Cpsw_handleLinkUp: Port 1: Link up: 1-Gbps Full-Duplex
    MAC Port 1: link up
    link_callback==UP
    status_callback==UP, local interface IP is 10.19.63.26
    Enet lwIP App: Added Network IP address I/F ti1: 10.19.63.26
    Initializing apps

    Log (error):

    EnetBoard_setupPorts: 1 of 1 ports configurations found
    Starting lwIP, local interface IP is dhcp-enabled
    [UDMA] [Error] Sciclient event config failed!!!
    [UDMA] [Error] Event config failed!!
    [UDMA] [Error] Global master event register failed!!!
    Assertion @ Line: 165 in ../src/enet_apputils/enet_udmautils.c: UDMA_SOK == retVal : failed !!!

  • 0 in reply to Joachim Wiesemann
    TI__Guru 63340 points

    Hi,

    It could be due to resource requested by Ethernet test application (enet_lwip_example_freertos_mcu2_0_debug) were already used during first time running of application.

    Here, resources were managed by SciServer running on MCU1_0 during first time load application requested for resources were being allocated as those are avaiable. When you do reset of MCU2_0 core and loading application, again it will request for resources then SciServer will return fail as resources being used in first time and no one has freed due to hard rest of core.

    If you want it to work normal, you have to load SciServer as well.

    Best Regards,
    Sudheer