Jeffer

So, it reach login prompt, you've logged in an still don't see the /dev/spidev0.0 ?
What shows up doing "grep SPIDEV /boot/config-*" ?
It should show :
CONFIG_SPI_SPIDEV=m Which kernel are you using ?

It is not for NanoPi-M4, as I mentioned I've use NanoPC-T4 ...
 
EDIT : I've just double checked on my T4 : SPI1 is really on spi@ff1d0000 ...
So, why your M4 doesn't boot after such changes ? Maybe you did some typo errors ?

Thank you for informing me that fact.
you know, the money for me is limited as well so we chose this chip.
Of course we understand it can fail during the flight.
It is going to be like "Welcome on board. You can enjoy playing some games running on RK3399 during our flight" haha 

Thank you for informing me that fact.
you know, the money for me is limited as well so we chose this chip.
Of course we understand it can fail during the flight.
It is going to be like "Welcome on board. You can enjoy playing some games running on RK3399 during our flight" haha 

I am just informing you that there are problems hidden deep inside. We have encounter some and some are ready to be found in a process when kernel gets matured. If I would sit in the plane where captain would say: "Welcome on board. This plane is running RK3399 ... I would immediately leave that plane"  In a few months from now, situation will be changed ... if there will be enough interest to have this kernel pitch perfect.