Nanopi M4 V1 won't boot latest versions

[dogshome]

Hi all, 

This has confused me! I have an old copy Armbian_20.02.7_Nanopim4_buster_current_5.4.28_desktop.7z which works fine. Any SD cards I put it on using Balena Etcher works. Any of the latest versions simply won't boot.

 

The only difference appears to be the XZ file format. I extracted one of the later ones using 7Zip and then Etcher to flash and as expected it mad no difference at all.

 

Has something been done to the V1 firmware from the V2 that doesn't work or firmwares containing the wrong naming etc? 

 

Help!

Edited June 9, 2020 by dogshome
New HDMI monitor is the problem!

[Werner]

Do you have an USB-TTL adapter? Best chance go get an idea what happens inside is via serial console and such a tool.

[dogshome]

Yes for Arduino. What PC software would i use?

[dogshome]

V2 firmware also doesn't work (despite only difference being RAM type DDR3 to DDR4). I'm not sure its getting a far as to start a UART. It's dead Jim!

[dogshome]

PS My somewhat older Orange Pi Plus works fine on the latest firmware!

[Kyra]

Ditto with the V2 and latest legacy kernel.

[Werner]

26 minutes ago, Kyra said:

Ditto with the V2 and latest legacy kernel.

  

4 hours ago, Werner said:

Do you have an USB-TTL adapter? Best chance go get an idea what happens inside is via serial console and such a tool.

 

[piter75]

@dogshome @Kyra I have just tested Armbian_20.05.2_Nanopim4v2_buster_current_5.4.43_desktop.img.xz and it boots fine with my M4 V2.

 

I have one suspicion though...

Can you try to boot with HDMI cable disconnected and then insert it again when the green led starts blinking? Does it boot this way?

[dogshome]

@piter75 Hi, yes it boots this way. lots of test as things starting up,  error country setting failed -2, but more drivers started OK, then it pauses with error:

drm:drm_scdc_set_scrambling failed to read tmds config, error 6

and 2 similar errors.

 

Logged in on terminal as normal startup. Desktop appears!

 

Subsequent reboot fails until HMDMI unplugged, then it boots to desktop.

 

 

 

I have a new 4K monitor with HDMI V2.0. That is something that has changed on my setup

 

Can you spill the beans???? 

[dogshome]

scdc set scrambling refers to HDMI 2.0. My new monitor is HDMI 2.0. The desktop obviously understands it, although not reporting full resolution and and sticking at 60Hz. my monitor is only 30Hz at 4K. It's the text based boot screen that can't handle it. My (almost vintage) Orange Plus sees it correctly when running on Armbian, as does a 6 month old version on the NanoPi, so someone knows how this works.

 

Thank you @piter75

 

So a 'lost setting' or 'feature' for development or porting from another build Mr Igor and friends please?

 

 

[piter75]

@dogshome yes, the HDMI is the culprit.

It (HDMI) was enabled for rk3399 boards in u-boot v2020.04.

It works for me with WQHD monitor (although the text is garbled in u-boot phase) but I have already seen one similar report for OrangePi 4 after u-boot upgrade.

 

I will disable HDMI in u-boot for all rk3399 boards that we support.

[dogshome]

On 6/9/2020 at 7:29 PM, piter75 said:

I will disable HDMI in u-boot for all rk3399 boards that we support.

[piter75]

@dogshome @Kyra what exact monitor models do you own?

[dogshome]

ASUS VP28UQG

[piter75]

@dogshome would you be able to test this image? 

It is a dev build with this PR: https://github.com/armbian/build/pull/2086 that switches u-boot v2020.07 and reenables HDMI.

[dogshome]

will do 

[denni_isl]

Did try few resent images as of beginning of feb 21 for nanopi-m4v2 and compiled my own using the armbian build and tried to move u-boot support for hdmi - bud did have to plug the hdmi cable after starting kernel ....  

 

This pilter75 image does bypass u-boot hdmi and therefore allows the kernel control of hdmi

https://users.armbian.com/piter75/Armbian_21.05.0-trunk_Nanopim4v2_buster_current_5.10.18_minimal-stability-fix.img.xz

 

There is one problem - USB 3 do flicker.  It is not possible to restore with rsync.    

Might be because I did install full firmware or overclocking.  

 

Edit:

It is either - USB is working okay without full firmware and overclocking.

[denni_isl]

One has to freeze kernel and u-boot upgrades because generation of new uInitr does disable linux kernel hdmi.    Disabling of hdmi in u-boot has to be implemented into armbian nanopi-m4v2 u-boot.