Network issues after upgrading to Stretch + kernel to 5.4

[carmel85]

Recently we purchased NetPi3 (model: NIOT-E-NPI3-51-EN-RE) for evaluation.
we have our project working on RPI3 with Jessie image. (our Jessie image seems to work fine on NetPi.)
today I tried to use our new upgraded image ( Stretch + Kernel 5.4) on NetPi
but network interfaces failed
here are steps for upgrade:

1. Update
   
2. Upgrade
   
3. Dist-upgrade
   
4. Rpi-updtae (updates Kernel)
   
5. Switch to Stretch
   
6. Update
   
7. Upgrade
   
8. Dist-upgrade (or full-upgrade) – this is not working well, it removes our internal "SA" service and more. this mechanism is also removing packeges/services as opposed to “upgrade”
   
   1. So I did not performed it
      
9. Rpi-updtae (for Kernel)
   
10. Kernel version now is 5.4.51
    

 
Unfortunately After I inserted SD with Stretch (+new Kernel) into NetPi
It had network issue: LAN + Wifi interfaces could not be up.
attached screenshots.

Any idea why network stopped working on NetPi? (on RPI 3 it works fine with same image)

Carmel.

[Armin@netPI]

Can you please confirm that your are using a Raspberry Pi 3B and not a Raspberry Pi 3B+. 3B+ is not compatible with netPI. Only the RPi 3B is.

Please look to the screen shot attached how a Raspberry Pi 3B looks like:

   

[Armin@netPI]

I have another question. You said you started with the upgrade process on a commercial RPi3, right? And then you took the SD card of the commercial Rpi3 and put into netPI and are faced with the problems you are referencing.

But how about this process: start using the jessie SD card version on netPI directly without an extra commercial RPi3 and then do the upgrade process as described. How is then netPI behaving?

netPI uses the same CPU, same LAN controller, same Wifi/BT chip as a commercial RPi3B. I see no chance for any type of software to see any differences. And also netPI is manufactured in the same fab in China where the commercial RPi3 have been produced 3 years ago. Meanwhile of course the fab switched to Rpi4 production while we stay stable with netPI

Thx
Armin