![]() Usually, functions are now RTOS thread-safe and can be called from different threads.įor a function-by-function comparison visit the appropriate reference sections: Parameters providing an IP address and a port are replaced with a single structure NET_ADDR that contains both, the IP address and port number. Most functions are compatible, with the exception of a few, where parameters are changed and optimized. In general, all function names are changed according to a new naming convention. This enables the user to change to the new API on a component level which reduces risk and required time for the migration. Using the Compatibility Mode, it is possible to mix old (v5/v6) and new API calls in the same project. This section shows how to migrate each software component of the Network separately. LOCALM structure defined network parameters for all available interfaces (Ethernet, PPP or SLIP). The following shows how to migrate code using LOCALM to the new Network Component API. netIF_SetOption to set values of an interface option.įor more information on the usage of the two functions refer to Runtime Configuration.netIF_GetOption to get the current value of an interface option and.This is deprecated and the following two control functions have been introduced for runtime configuration. This was used to change the configuration of the network interface at runtime. In previous versions of the Network Component (v5 and v6) and in the old RL-ARM networking stack it was possible to get direct access to a structure called LOCALM. The IDE will show an error message that a software component is not available:Įrror-free build output Note If you see errors/warnings in the Build Output window, check the section Porting Library Functionality for details on how to migrate functions that are not covered by the compatibility layer. Simply open the project that is about to be migrated in µVision. There is an easy migration path available for users of the Network Component v5 and v6. STDIO Debug explains how to use the legacy debug features.Network Configuration describes the differences in the configuration files of the Network Component.Component Migration explains the required code changes for every single software component.Porting Library Functionality demonstrates how to port functionality based on the internal library functions to the new API. ![]() Project Migration describes how to migrate an MDK Version 5 project from the previous Middleware (v5.x and v6.x) to the latest version.The following sections show how to migrate projects from previous versions of the Middleware: Based on this difference, the API has changed which will require either to use a compatibility mode to be able to use the new Network Core together with the old API or a manual change of the user code to reflect the API changes. The new Network Component supports IPv4 and IPv6, whereas previous versions of the Middleware provided support only for IPv4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |