• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 199 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.

the problem of mcfw demo's abort

zwh awe
Prodigy 90 points

hello everyone，i was plagued by the following problem:

8168 board sometimes crashes when running the mcfw demo（modified usecase）

so i use Ctrl+C to exit demo forced.

after back to linux command line,the linux runs slowly.. ls command will have 1-2 seconds delay...

initialization is aborted and Ctrl+C is no use when i run the mcfw demo again

now power off and restart only can be done

how to solve this problem? thankyou

  • 0
    TI__Guru 59700 points

    Which DVR RDK release are you using. Before RDK 3.0 there was a syslink bug which would cause syslink to go into busy loop causing 100% CPU load when a SIGINT signal is received the process doing MessageQ_get. This was fixed in RDK 3.0 and above.This may solve the CPU loading but application _must_ register for Ctrl+C signal handler and _must_ do clean shutdown before exiting the process. If the process is simply terminated all the syslink data structures will be in wrong state and the mcfw links will not be deleted. So you will not be able to run the application again. In summary Ctrl+C signal should be registerted by application and application should do clean teardown by deleting all the links the same way if usecase did clean exit.

  • 0 in reply to Badri Narayanan
    Prodigy 90 points

    thankyou

    new version RDK mcfw demo can handle Ctrl+C signal handler??

  • 0 in reply to zwh awe
    TI__Guru 59700 points

    RDK 3.5 has the syslink bug fix which ensures that doing CTRL+C doesn't cause 100% CPU loading. However it is your application which should implement a Ctrl+C signal handler which does proper deletion of all the links created in your usecase.