NanoPC T4


Recommended Posts

I'm having booting issues with the new Bionic Desktop image i.e 19.11.7. It won't boot at all. Black screen with no signal. Sdcard green light flashes only once after 5 secs of starting and then nothing.

 

Last image worked was 19.11.3 (kernel 4.4.192). 4.4.198 didn't boot either, so I flashed now 19.11.7 (kernel 4.4.208) and it fails as well.

 

I waited over 25 mins for it to boot.

Link to post
Share on other sites
Donate and support the project!

1 hour ago, Aciel said:

I'm having booting issues with the new Bionic Desktop image i.e 19.11.7. It won't boot at all. Black screen with no signal. Sdcard green light flashes only once after 5 secs of starting and then nothing.


Do you hold boot button? Otherwise it boots something from your eMMC ... I just tried this image and works normally on my T4.

Link to post
Share on other sites
11 hours ago, Igor said:

Yes.

 

11 hours ago, Igor said:


Do you hold boot button? Otherwise it boots something from your eMMC ... I just tried this image and works normally on my T4.

No, I only hold the power button ~2secs when 1st starting the board and it always boot from sdcard (worked with 19.11.3). I do the same to boot my LibreELEC SDCard. No card,  power on boots Android from eMMC.

 

6 hours ago, starman345 said:

Maybe try a different SD card?  Those images you mention boot fine on my NanoPC-T4

Tried 2 different SDCards, but same behaviour.

Link to post
Share on other sites
46 minutes ago, Igor said:

It is expected to behave like this. If you don't hold boot button, you boot with boot-loader which is present on eMMC. Which is out of our control ... 

I tried with holding the boot button then power up the board, and kept holding the boot button for like 10 secs = Still won't boot.

 

I'll re-try 19.11.3 (kernel 4.4.192) image now and post result.

Link to post
Share on other sites
13 minutes ago, Aciel said:

I tried with holding the boot button then power up the board, and kept holding the boot button for like 10 secs = Still won't boot.

 

1. Attach power

2. Hold boot button

3. Power the board and wait until leds start to flash, then release.

Link to post
Share on other sites
4 minutes ago, Igor said:

 

1. Attach power

2. Hold boot button

3. Power the board and wait until leds start to flash, then release.

Did the exact thing, no result. Board turns on (red light is there) but it won't boot from sdcard. Will the try last image that worked for me now.

Link to post
Share on other sites

@Igor

 

I flashed the 19.11.3 (kernel 4.4.192) image and it booted right away (I didn't hold the boot button) and I get to the console. Set user account, etc and I'm in desktop.

 

Now the diagnostic part about what is wrong with the new images.

 

When I flashed the 19.11.7 (kernel 4.4.208), this is what my blkid said (sda = sdcard Armbian is flashed to)

# blkid
/dev/loop0: TYPE="squashfs"
/dev/mmcblk0: PTUUID="b811ee1f" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="2211-5513" TYPE="vfat" PARTUUID="b811ee1f-01"
/dev/mmcblk0p2: LABEL="STORAGE" UUID="a321c910-4860-4321-bec0-31d20884f00c" TYPE="ext4" PARTUUID="b811ee1f-02"
/dev/sda1: PTUUID="02f47b31" PTTYPE="dos" PARTUUID="cf28ecd8-01"
/dev/sdb1: LABEL="Aciel" UUID="4E1AEA7B1AEA6007" TYPE="ntfs" PARTUUID="51e1ebcd-01"
#


Here is the one from 19.11.3 (kernel 4.4.192):

# blkid
/dev/loop0: TYPE="squashfs"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="2211-5513" TYPE="vfat" PARTUUID="b811ee1f-01"
/dev/mmcblk0p2: LABEL="STORAGE" UUID="a321c910-4860-4321-bec0-31d20884f00c" TYPE="ext4" PARTUUID="b811ee1f-02"
/dev/sdb1: LABEL="Aciel" UUID="4E1AEA7B1AEA6007" TYPE="ntfs" PARTUUID="51e1ebcd-01"
/dev/mmcblk0: PTUUID="b811ee1f" PTTYPE="dos"
/dev/sda1: UUID="dd3833fd-2ea5-411b-a48d-91968fe7241f" TYPE="ext4" PARTUUID="cf28ecd8-01"
#

 

19.11.7 = creating dos partition and unable to boot

19.11.3 = creates ext4 partition and it boots normally

Link to post
Share on other sites
35 minutes ago, Aciel said:

When I flashed the 19.11.7 (kernel 4.4.208), this is what my blkid said (sda = sdcard Armbian is flashed to)


Images are made in automated fashion, they are also mainly tested. Yes, sometimes things go wrong which is why I test this image: https://dl.armbian.com/nanopct4/archive/Armbian_19.11.7_Nanopct4_bionic_legacy_4.4.208_desktop.7z and it works.

 

This means problem is 100% not ours. Since you don't have OS on the card, two things remains:
- failed SD card https://forum.armbian.com/forum/31-sd-card-and-psu-issues/

- wrong writing method or troubles with the computer where you write that image https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

Link to post
Share on other sites

Couple of issues I discover so far:

 

1. Just found that kernel upgrade via armbian-config cause replacing legacy u-boot (linux-u-boot-nanopct4-default version 5.98) with linux-u-boot-nanopct4-current 2020.01 (that was Bionic installation updated to Eoan) which refuse to boot from eMMC:

 

Hit any key to stop autoboot:  0  
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2949 bytes read in 21 ms (136.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
193 bytes read in 18 ms (9.8 KiB/s)
8355114 bytes read in 881 ms (9 MiB/s)
20722176 bytes read in 2146 ms (9.2 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
2698 bytes read in 39 ms (67.4 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 39000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8355050 Bytes = 8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
   Loading Ramdisk to f572b000, end f5f22cea ... OK
FDT and ATAGS support not compiled in - hanging
### ERROR ### Please RESET the board ###

Please let me know if I need to perform additional testing or provide additional logs.

 

2. While WD SSD, such as WDS200T3X0C, works just fine on both of Linux 4.4 and 5.3, SSD from Samsung, such as 970 EVO, works only with 4.4, but not with 5.3. Pci driver just fail to detect it, while on 4.4 same SSD works for half year without issues.

 

3. USB-C port doesn't work. Docking stations, flash drives, and external disks all detected in the same way:

phy phy-ff770000.syscon:usb2-phy@e450.2: charger = USB_DCP_CHARGER

Link to post
Share on other sites
2 hours ago, RussianNeuroMancer said:

kernel upgrade via armbian-config cause replacing legacy u-boot (linux-u-boot-nanopct4-default version 5.98) with linux-u-boot-nanopct4-current 2020.01 (that was Bionic installation updated to Eoan) which refuse to boot from eMMC

What version of kernel did you upgrade to?

 

To fix it without writing a new image you could probably simply boot with SD, mount eMMC and remove fdtfile entry from mounted "boot/armbianEnv.txt".

It is probably pointing to a "rockchip/rk3399-nanopi4-rev00.dtb" file that is not part of modern kernel package anymore :(

Link to post
Share on other sites
On 3/3/2020 at 5:55 PM, RussianNeuroMancer said:

2. While WD SSD, such as WDS200T3X0C, works just fine on both of Linux 4.4 and 5.3, SSD from Samsung, such as 970 EVO, works only with 4.4, but not with 5.3. Pci driver just fail to detect it, while on 4.4 same SSD works for half year without issues.

 

Same here. My 970 EVO NMVe doesn't get recognized by the 5.3 kernel  while legacy kernel works perfect (dev kernel doesn't work either).

Link to post
Share on other sites
On 3/4/2020 at 4:41 AM, piter75 said:

What version of kernel did you upgrade to?

 

To fix it without writing a new image you could probably simply boot with SD, mount eMMC and remove fdtfile entry from mounted "boot/armbianEnv.txt".

It is probably pointing to a "rockchip/rk3399-nanopi4-rev00.dtb" file that is not part of modern kernel package anymore :(

From 5.3.11 to 5.4.20, so simply from "old" current to "new" current.

Removing fdtfile entry indeed helps, thank you!

 

Any idea what to do with SSD? Upstream issue?

 

Link to post
Share on other sites

I have some progress with SSD issue:

 

On 3/7/2020 at 10:35 PM, diglos said:

Same here. My 970 EVO NMVe doesn't get recognized by the 5.3 kernel  while legacy kernel works perfect (dev kernel doesn't work either).

 

Try to remove (or move somewhere else) rockchip-pcie-gen2.dtbo from /boot/dtb/rockchip/overlay and let me know what you see.

 

From my testing 5.4.8 and 5.4.20 fail like this:

Quote

[   51.472906] rockchip-pcie f8000000.pcie: no vpcie12v regulator found            
[   51.472918] rockchip-pcie f8000000.pcie: no vpcie3v3 regulator found            
[   51.472928] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found            
[   51.472938] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found            
[   51.997942] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!       
[   51.998038] rockchip-pcie: probe of f8000000.pcie failed with error -110

 

And 5.4.26 panic like this:

 

Quote

[   53.002702] SError Interrupt on CPU3, code 0xbf000002 -- SError                  
[   53.002706] CPU: 3 PID: 343 Comm: systemd-udevd Tainted: G        W         5.4.
26-rockchip64 #20.02.5                                                              
[   53.002708] Hardware name: FriendlyElec NanoPC-T4 (DT)                           
[   53.002710] pstate: 80000005 (Nzcv daif -PAN -UAO)                               
[   53.002711] pc : preempt_count_sub+0x10/0xb8                                     
[   53.002712] lr : _raw_spin_unlock+0x18/0x38                                      
[   53.002713] sp : ffff8000126cb740                                                
[   53.002715] x29: ffff8000126cb740 x28: 000000001d1c1100                          
[   53.002718] x27: 0000000000000001 x26: 0000000000000000                          
[   53.002721] x25: ffff0000f591d000 x24: 0000000000000000                          
[   53.002724] x23: ffff0000ee824618 x22: 0000000000000001                          
[   53.002727] x21: ffff0000eef59b08 x20: ffff8000126cb7e8                          
[   53.002730] x19: ffff0000eef59b00 x18: 0000000000000000                          
[   53.002733] x17: 0000000000000000 x16: 0000000000000000                          
[   53.002736] x15: ffff8000126cb784 x14: ffff0000f5975dc0                          
[   53.002738] x13: 0000000000000000 x12: 0000000000000000                          
[   53.002741] x11: ffff0000f67a9268 x10: 000000001d1c1101                          
[   53.002744] x9 : 0000000000000000 x8 : 0000000000000000                          
[   53.002747] x7 : 0000000000000001 x6 : 0000000000000000                          
[   53.002750] x5 : 0000000000000001 x4 : ffff8000126cb760                          
[   53.002753] x3 : 0000000000000400 x2 : 0000000000000000                          
[   53.002756] x1 : 0000000000000000 x0 : 0000000000000001                          
[   53.002759] Kernel panic - not syncing: Asynchronous SError Interrupt            
[   53.002761] CPU: 3 PID: 343 Comm: systemd-udevd Tainted: G        W         5.4.
26-rockchip64 #20.02.5                                                              
[   53.002763] Hardware name: FriendlyElec NanoPC-T4 (DT)                           
[   53.002764] Call trace:                                                          
[   53.002766]  dump_backtrace+0x0/0x140                                            
[   53.002767]  show_stack+0x14/0x20                                                
[   53.002768]  dump_stack+0xa8/0xd0                                                
[   53.002769]  panic+0x154/0x320                                                   
[   53.002770]  __stack_chk_fail+0x0/0x18                                           
[   53.002771]  arm64_serror_panic+0x70/0x80                                        
[   53.002773]  do_serror+0x6c/0x148                                                
[   53.002774]  el1_error+0x84/0xf8                                                 
[   53.002775]  preempt_count_sub+0x10/0xb8                                         
[   53.002776]  _raw_spin_unlock+0x18/0x38                                          
[   53.002778]  nvme_submit_cmd+0xec/0x118                                          
[   53.002779]  nvme_queue_rq+0x114/0x1e8                                           
[   53.002780]  __blk_mq_try_issue_directly+0x140/0x1c8                             
[   53.002782]  blk_mq_request_issue_directly+0x54/0x90                             
[   53.002783]  blk_mq_try_issue_list_directly+0x50/0xd0                            
[   53.002785]  blk_mq_sched_insert_requests+0x180/0x200                            
[   53.002786]  blk_mq_flush_plug_list+0x14c/0x190                                  
[   53.002787]  blk_flush_plug_list+0xd4/0x100                                      
[   53.002789]  blk_finish_plug+0x30/0x40                                           
[   53.002790]  read_pages+0x7c/0x180                                               
[   53.002791]  __do_page_cache_readahead+0x18c/0x1b8                               
[   53.002793]  force_page_cache_readahead+0x9c/0x100                               
[   53.002794]  page_cache_sync_readahead+0xd4/0xd8                                 
[   53.002796]  generic_file_read_iter+0x730/0x9c0                                  
[   53.002797]  blkdev_read_iter+0x38/0x48                                          
[   53.002798]  new_sync_read+0x100/0x178                                           
[   53.002799]  __vfs_read+0x2c/0x40                                                
[   53.002800]  vfs_read+0x9c/0x188                                                 
[   53.002801]  ksys_read+0x64/0xe8                                                 
[   53.002803]  __arm64_sys_read+0x18/0x20                                          
[   53.002804]  el0_svc_common.constprop.1+0x88/0x178                               
[   53.002805]  el0_svc_handler+0x20/0x80                                           
[   53.002806]  el0_svc+0x8/0xc                                                     
[   53.002827] SMP: stopping secondary CPUs                                         
[   53.002828] Kernel Offset: disabled                                              
[   53.002830] CPU features: 0x0002,20006008                                        
[   53.002831] Memory Limit: none

 

I also noticed that these fresh 4.4 legacy images no longer boot with Samsung SSD attached (really long "Unhandled fault" error) so I had to use vendor's microSD image to restore eMMC backup from NVME (I know, my fault, had to have one more copy somewhere else). Do you observe same behavior with Armbian 4.4 legacy images on your NanoPC-T4?

 

EDIT1 Hmm, somehow got 5.4.26 working with Samsung SSD. At least I upgraded to current u-boot manually by using dd (automatic u-boot updater from armbian-config didn't work with "Unsupported u-boot processing configuration" error) and removed rockchip-pcie-gen2.dtbo. Another difference with logs above that above I tried to boot from microSD and now I tried same steps with installation I have on eMMC.

 

EDIT2 It's seems like part of the errors above caused by the fact that I didn't power down board completely between attempts to run 4.4 and 5.4 kernels - I didn't detached PSU and I didn't detached serial console. I guess if I would try that before boot Armbian with 4.4 kernel from microSD it would work. However, interesting part here that is that friendlydesktop never fail to boot and never fail to detect Samsung SSD, even without detaching PSU and serial console. So it's seems like some necessary patches that make board boot more stable is still missing from upstream. Right now I have Samsung SSD working on 5.4.26 even with rockchip-pcie-gen2.dtbo.

Link to post
Share on other sites

There is a strange result. When using sources and patches from the Armbian build system (core 5.4) and adding changes from the T4 patch, the 5651 device does not appear. But if  comment on a line

 

&i2s0{
    assigned-clocks = <&cru SCLK_I2SOUT_SRC>;
//    assigned-clock-parents = <&cru SCLK_I2S0_8CH>;
    rockchip,i2s-broken-burst-len;
    rockchip,playback-channels = <2>;
    rockchip,capture-channels = <2>;
    #sound-dai-cells = <0>;
    status = "okay";
};

 

 the device appears and there are clicks in the speakers when switching on and off.

@Merblud  What alsa settings do you use to enable audio ?

Link to post
Share on other sites
6 hours ago, balbes150 said:

There is a strange result. When using sources and patches from the Armbian build system (core 5.4) and adding changes from the T4 patch, the 5651 device does not appear. But if  comment on a line

I am sorry. I checked with the 5.2.8 core from kernel.org (not from Armbian build system). I prepared the patch for core 5.4.35. But the core 5.4.35 didn 't have time to check. I have to do the assembly directly on T4. It long.

Link to post
Share on other sites
6 hours ago, balbes150 said:

What alsa settings do you use to enable audio ?

 

amixer set 'HPO L' on
amixer set 'HPO R' on
amixer set 'HPOVOL L' on
amixer set 'HPOVOL R' on
amixer set 'HPO MIX HPVOL' on
amixer set 'OUT MIXL DAC L1' on
amixer set 'OUT MIXR DAC R1' on
amixer set 'Stereo DAC MIXL DAC L1' on
amixer set 'Stereo DAC MIXR DAC R1' on

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...