| Table of Contents |
|---|
Introduction
...
Store configuration parameters permanently
A major difference is that the functions to store between NIC 50-RE and NIC 52-RE is in storing configuration parameters permanently in flash memory are no longer supported on NIC 52 devices.
This has been changed to save the Due to a limited number of write cycles on the flash memory, thus preventing device defects.So now after each reset of the netIC the configuration parameters are taken from the flash memoryit is not recommended not to use the application to change a permanent configuration.
We therefore recommend to create a fixed basic configuration using the NetX Configuration Tool and configure everything else during startup via the configuration register via Modbus.
--> This is a wrong information. The function is supported since Therefore this function has been deactivated for the netIC 52, at product release.
However, since Firmware V2.3.0.0 storing a configuration into the flash has been activated again.
the customer should use the following steps, as described for NIC 50:
1. To use this function, beside the appropriate Firmwareversion, a 2nd stage bootloader with V1.6.0.0 needs to be used inside the NIC 52-RE.
V1.6.0.0 is used in production since April 2019.
The steps for storing a fixed configuration to the flash memory, is nearly the same as for NIC 50-RE:
- Write all configuration parameters to the corresponding registers using function code 16.
...
- Set the CLR_CFG
...
- (Register 1999, Bit 6) flag within the command register to clear the configuration parameter in the Flash memory.
...
- Check
...
- the status of the System Flag (Register 999) until the flag FLS_CFG (Bit 7) has been cleared
...
- .
...
- Set the STR_
...
- CFG (Register 1999, Bit 7) flag within the command register to store the configuration parameter in the Flash memory.
...
- Check
...
- the status of the System Flag (Register 999) until the flag FLS_CFG (Bit 7) has been set again.
...
...
- Set the INIT
...
- (Register 1999, Bit 4) flag.
- The netIC now starts with the new configuration parameters.
BUT he needs to use this flag for clearing the configuration:
Page 94: netIC - Real-Time Ethernet and Fieldbus Gateways UM DG 36 EN.pdf
...
Mirko 2020-03-13:
The feature CLR_CFG / STR_CFG supported beginning with netIC FW V2.3 works only in conjunction with a new "second stage boot loader" which is not yet introduced in the netIC production.
This is addressed to product managment.
If you want, i can provide a such special 2nd boot loader to just for test purposes on your local desk.
Then you have the chance at least to test this feature on you desk.
Otherwise you should wait until new netIC with a new 2nd stage loader are deliverd.
Handling for storage:
The CLR_CFG (bit6) is only required once as long the configuration from the netX Configuration tool is still present in the netIC.
As long the "netX Configuration tool configuration" is present you can NOT set the STR_CFG (bit 7) an exception will appear.
...
Once the "netX Configuration tool configuration" is cleared you can store the configuration any time with STR_CFG (bit 7).
Its is not required to clear the config any time before. Just modify and store.
A new flag REM_CFG (bit12) has been spend in the status register to indicate that the netIC has loaded a remanent configuration by the host.
If you want to delete the remanent configuration written by the host you must use the new defined flag CLR_REM_CFG (bit12) in the command regsiter.
Once you have stored the configuration you activate it eather by setting the INIT flag or RESTET the netIC with the Reste Flag.With netIC 52, for step 2 the CLR_REM_CFG Flag (Register 1999, Bit 12) needs to be set to clear the configuration parameter in the Flash memory.
netIC - Design guide and User manual