Jump to content

Recommended Posts

Posted

Can you check the installation in eMMC on K2 ?

After recording the Armbian image for the TV box (add u-boot to SD card and DTB settings), you need to download and copy these two files to the /root directory on the SD card. After starting the system from SD card to K2, you need to run the script s905_install.sh from the user "root". The script should install the system on eMMC and create a new u-boot (special version for eMMC). I have on S905 this works (I installed in eMMC the latest armbian image with kernel 5.3.0).

Before starting the system SD card and run install on K2, to avoid side effects, you need to completely clean the eMMC.

 

If the u-boot installation does not work from the script, you can re-write the file (uboot_s905_emmc_1m. img) to eMMC after the script runs s905_install.sh two commands

 

dd if=uboot_s905_emmc_1m.img of=/dev/mmcblkX conv=fsync bs=1 count=442

dd if=uboot_s905_emmc_1m.img of=/dev/mmcblkX conv=fsync bs=512 skip=1 seek=1

 

https://yadi.sk/d/3RhEo60liJuTDw

 

 

For a quick check, you can immediately write uboot_s905_emmc_1m.img to eMMC with a single DD command and check the overall launch of the u-boot itself with eMMC. After writing u-boot to eMMC, there should be a partition table (two partitions) on eMMC.

Posted
  On 10/27/2019 at 4:55 PM, balbes150 said:

For a quick check, you can immediately write uboot_s905_emmc_1m.img to eMMC

Expand  

That is what I will do, because I've already working Armbian installed on the eMMC into a single partition, so I don't wish to erase it for now.

 

EDIT: It is a good step in the good direction, this U-Boot is now loaded from eMMC (wihout SD inserted) !

However, this U-Boot is far from the one from Armbian, it doesn't provide "ls", I had to do "ext4ls" instead, but this is not a big deal...

But it is also a bit buggy with sub-directories, since doing "ext4ls mmc 0 /boot" don't show any files, while doing "ext4ls mmc 0 /bin" is showing the files located in /boot ... :angry:

  Reveal hidden contents

 

I will now try to see if placing files in root will help, and try to adjust boot.scr to use ext4load instead of load like in Armbian U-Boot ...

 

EDIT2: Strangely, the bug about sub-directory with boot/bin confusing doesn't exist if done one the SDCard inserted :

  Reveal hidden contents

 

EDIT3: filesystem functions are really buggy ... Now, from SDCard, I can do "ext4ls mmc 1 /boot/dtb/amlogic" but can't do "ext4ls mmc 1 /boot/dtb/amlogic/meson-gxbb-nanopi-k2.dtb", so I presume I won't be able to do "ext4load" ...

 

  Reveal hidden contents

Posted
  On 10/27/2019 at 6:53 PM, martinayotte said:

filesystem functions are really buggy ... Now, from SDCard, I can do "ext4ls mmc 1 /boot/dtb/amlogic" but can't do "ext4ls mmc 1 /boot/dtb/amlogic/meson-gxbb-nanopi-k2.dtb", so I presume I won't be able to do "ext4load" ...

Expand  

I check the work, only together with the script s905_install. After using it, the system normally starts automatically from eMMC.

 

Important. The eMMC device number changes when the SD card is connected. With SD card, the eMMC number will be mmcblk1. Without SD card number mmcblk0. This should be considered when creating a startup script from eMMC.

 

Also in this u-boot "built" MBR partition table with two partitions, the first FAT and the second EXT4.

  • Igor unpinned this topic
Posted (edited)

Hi everyone, I'm kind new on linux, but I have some idea. I was running before another linux distribution and ethernet was working. Today I changed the SD because last one was not working fine, and I decided to installed the new armbian images. 
Wifi worked perfect, but I can't get eth0 working. When I try to activate it from ntmui, is showing this: 

image.png.965b1ddba7ea3b38d9ea39eef9dd61bc.png
Some info here: 

 

nanopik2:~:% sudo ethtool eth0
Settings for eth0:
Cannot get device settings: Device or resource busy
Cannot get wake-on-lan settings: Device or resource busy
Cannot get message level: Device or resource busy
Cannot get link status: Device or resource busy
No data available

nanopik2:~:% dmesg | grep eth
[    0.000000] psci: probing for conduit method from DT.
[    2.372867] meson8b-dwmac c9410000.ethernet: IRQ eth_wake_irq not found
[    2.372879] meson8b-dwmac c9410000.ethernet: IRQ eth_lpi not found
[    2.372999] meson8b-dwmac c9410000.ethernet: PTP uses main clock
[    2.373799] meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[    2.373814] meson8b-dwmac c9410000.ethernet:         DWMAC1000
[    2.373819] meson8b-dwmac c9410000.ethernet: DMA HW capability register supported
[    2.373823] meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported
[    2.373828] meson8b-dwmac c9410000.ethernet: COE Type 2
[    2.373832] meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported
[    2.373835] meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported
[    2.373924] meson8b-dwmac c9410000.ethernet: Normal descriptors
[    2.373928] meson8b-dwmac c9410000.ethernet: Ring mode enabled
[    2.373933] meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.373943] meson8b-dwmac c9410000.ethernet: device MAC address ca:6e:40:ff:62:6b
[   14.681861] meson8b-dwmac c9410000.ethernet eth0: no phy at addr -1
[   14.682506] meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)


nanopik2:~:% cat /proc/device-tree/model
FriendlyARM NanoPi K2%  

nanopik2:~:% uname -a
Linux nanopik2 5.10.21-meson64 #21.02.3 SMP PREEMPT Mon Mar 8 07:22:00 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

Thanks in advance. 

Edited by Muadiv
Posted

I tried the latest version of the firmware and

 Armbian_21.02.3_Nanopik2-s905_buster_current_5.10.21.img.xz

None of them enable K2 to run eth0 to connect to the local network.

I'm in the same situation as Muadiv above. Is there any solutions?

Much appreciated!

Posted

Hi

I know this is an old thread. A few years ago i bought two NanoPi K2's

I used these as kodi boxes for a while, but eventually stopped using them when i got an nvidia shield and other android tv boxes

Recently i have wanted to put these back to use, specifically to run Armbian and do a source install of Retropie (which works suprisingly well) with only two caveats

 

1: The Video resolution seems to be locked to lower resolutions (1024x768 and i think 800x600)

2: The onboard HDMI Audio does not seem to work 

 

these issues are both apparent with the latest "automated" builds available on the Armbian website

 

I was just wondering which build was the last "non automated" build where HDMI Audio and Video resolutions (say, 1920x1080) are supported

 

Alternatively, are there any patches that can be applied to make the HDMI Audio work or to hard code a custom resolution? I seem to be finding conflicting info online, and this board does not appear to be very popular which is a bit sad, because it actually seems like a well featured board. If only the manufacturer supported it better.  

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.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines