November-3rd-2020, 03:54 PM
(This post was last modified: November-3rd-2020, 04:53 PM by Armin@netPI.)
There is one thing as additional remark:
The upper 4 leds of netPI named ERR RUN APL SYS are all connected to netPI's netX network controller.
Whenever there is a firmware download activated you see the LED SYS going to state "off" for a short time and then turning "on" again. This is an indication that netX controller has performed a shutdown/reset/firmware load which is totally unusual to see if you are always starting the same container application with the same netX firmware inside.
As I said the netX driver always checks if the firmware on Linux side is the same as loaded in netX. If there is a checksum difference the driver automatically loads the software again into the netX controller.
The upper 4 leds of netPI named ERR RUN APL SYS are all connected to netPI's netX network controller.
Whenever there is a firmware download activated you see the LED SYS going to state "off" for a short time and then turning "on" again. This is an indication that netX controller has performed a shutdown/reset/firmware load which is totally unusual to see if you are always starting the same container application with the same netX firmware inside.
As I said the netX driver always checks if the firmware on Linux side is the same as loaded in netX. If there is a checksum difference the driver automatically loads the software again into the netX controller.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)