Keil Logo

MDK MIDDLEWARE: Migrating to RTX v5, hardfault caused by netInitialize


Information in this knowledgebase article applies to:

  • MDK v5.22 or newer versions
  • CMSIS RTOSv2 based RTXv5.x

SYMPTOM

While migrating a project using MDK Network component from RTXv4.x to RTXv5, a call to netInitialize() leads to a hard fault. This function returned successfully in RTX. What is happening?

CAUSE

netInitialize() must be called within a thread.

In the project, netInitialize() is probably being called from main(). In RTXv4.x, main() is a thread. In RTXv5.x, main() is not a thread.

RESOLUTION

Call netInitialize() from an existing thread, such as the app_main thread, or create a separate thread to start the Network Component.

MORE INFORMATION

Last Reviewed: Tuesday, December 22, 2020


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.