Jump to content

Recommended Posts

Posted

hi @balbes150 - here is my dtb in source and binary and to make it complete also the other patches i use against the current megous 5.4 tree (just in case there is anything interesting in them for you). to my surprise the frequency scaling hack i was using with an adjusted opp table and fake vcccpu and dcdcc does not seem to work anymore in v5.4 (it only runs at fixed 900mhz again now) - i'll have to investigate why ...

 

best wishes - hexdump

emmc-fix.patchFetching info... h6-ac200-eth-and-local-changes-v5.4.patchFetching info... h6-ac200-eth-new-files.patchFetching info... sun50i-h6-eachlink-h6mini.dtsFetching info... sun50i-h6-eachlink-h6mini.dtbFetching info...

Posted
  On 12/22/2019 at 9:18 AM, balbes150 said:

Took "clean" config from LE and built Armbian with It (version 20191222). Now the wired network works.  Perhaps when using the universal kernel config, some options are not in the state that would ensure the operation of a wired network. :)

 

@hexdump  @PiotrO   Can you drop me a copy of the u-boot and dtb you use for Eachlink H6 ? For u-boot, you can simply make a copy of the DD - 4M from your working SD card.

Expand  

@balbes150

pls find below:

On 5.5 kernel - for eachlink H6 i'm using this patch to get dtb:

https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-5.5/files/0530-arm64-dts-allwinner-add-Eeachlink-H6-Mini.patch

For u-boot I'm using custodian repo:

https://gitlab.denx.de/u-boot/custodians/u-boot-sunxi

with patch adding H6 support:

https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-sunxi/files/0001-sunxi-H6-Add-basic-Eachlink-H6-Mini-support.patch

Pls let me know do You still need 4M from SD card. 

(of corse I'm sure You remember to add PWM & AC200 support in kernel)

br

Posted
  On 12/22/2019 at 10:12 AM, PiotrO said:

Pls let me know do You still need 4M from SD card. 

Expand  

If you have an opportunity, it is better to throw off also your variant of u-boot, I will try to compare their work on the my models.

Posted

Looks like for my eachlink H6 model (not mini), need another u-boot. None of the tested variants did not produce results. Android starts. When you connect the SD card, there is no launch of Android (so there is an appeal to the SD card). On TX6 if is used not the right DTB, there is modicum any message, and here full silence. Without UART it is not clear what is happening. I tried to connect UART, but there is no output to the console at all. On infe in Internet, on this model there is no full-fledged UART, lacks parts of details. :(

Posted

@hexdump  @PiotrO

Can you for verification try to run any of my latest Armbian image for AW ? I am interested in such launch options.

1. The original state (after recording what not to change).

2. Add your DTB and write it in (extlinux.conf).

3. Replace u-boot with yours.

Posted

ok - i got the frequency scaling problem sorted out for my 5.4 kernel: if the opp table in your arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi is compatible = "allwinner,sun50i-h6-operating-points" instead of the old compatible = "operating-points-v2" then you need the attached dts/dtb and add the CONFIG_ARM_ALLWINNER_SUN50I_CPUFREQ_NVMEM option to your kernel ... it seems to be specific to the megous kernel i guess (https://github.com/megous/linux/commit/8bad58044be498d409400dbf9757f2ae25c6ad9d#diff-6b1746cab346b54e23ae12e093173b4c) but might get relevant for newer mainline kernel versions too as he seems to upstream quite a bit of his stuff ...

 

best wishes - hexdump

sun50i-h6-eachlink-h6mini.dtbFetching info... sun50i-h6-eachlink-h6mini.dtsFetching info...

Posted

@balbes150 - one other thing: try to add "mem=2048M video=HDMI-A-1:e" to your kernel cmdline - some boxes (like my eachlink h6 mini) fail to detect the memory size properly and/or fail to enable the hdmi port otherwise ...

 

best wishes - hexdump

Posted
  On 12/22/2019 at 12:11 PM, hexdump said:

mem=2048M video=HDMI-A-1:e

Expand  

Added these settings and got the message from the TV about an unsupported mode. Pulled out HDMI and plugged again and the image appeared. Means u-boot, kernel and DTB working. But there is no wired network yet. But this is already a big progress, there is something to work on that would make this TV box work, and not fall on the shelf. By the way, the sound and USB WiFi\LAN and stuff works. :)

 

 

 

Added these parameters to (extlinux.conf) for the Le image and everything automatically started with default u-boot and dtb for TX6. There is a network, a sound and other on Eachlink H6.  :)

Posted
  On 12/22/2019 at 2:33 PM, balbes150 said:

Added these settings and got the message from the TV about an unsupported mode. Pulled out HDMI and plugged again and the image appeared. Means u-boot, kernel and DTB working. But there is no wired network yet. But this is already a big progress, there is something to work on that would make this TV box work, and not fall on the shelf. By the way, the sound and USB WiFi\LAN and stuff works. :)

 

 

 

Added these parameters to (extlinux.conf) for the Le image and everything automatically started with default u-boot and dtb for TX6. There is a network, a sound and other on Eachlink H6.  :)

Expand  

@balbes150

Regarding Eth: for sure You have AC200 2& H6 and PWM patches + proper kernel config?

IIRC kernel config should have:

CONFIG_COMMON_CLK_PWM=y

CONFIG_PWM_SUN4I=y

CONFIG_DWMAC_SUN8I=m

CONFIG_AC200_PHY=y

CONFIG_MFD_AC200=y

CONFIG_I2C_MV64XXX=y

note that all mentioned drivers have to be =y and only DWMAC_SUN8I=m 

 

Posted
  On 12/22/2019 at 4:24 PM, PiotrO said:

IIRC kernel config should have:

Expand  

I'll try to check these options for the universal kernel config.

 

  On 12/22/2019 at 4:41 PM, hexdump said:

for the ethernet patches maybe have a look at the patches i have appended above - they are mostly consisting of the ac200 eth + pwm stuff ...

Expand  

The kernel sources are the same, the difference is only in the kernel config. With config from LE network and everything else works well on both models (Tx6 and Eachlink). The network does not work only in a universal image (as @jernej and @PiotrO said above due to the specifics of kernel options).

Posted
  On 12/22/2019 at 4:24 PM, PiotrO said:

CONFIG_COMMON_CLK_PWM=y

CONFIG_PWM_SUN4I=y

CONFIG_DWMAC_SUN8I=m

CONFIG_AC200_PHY=y

CONFIG_MFD_AC200=y

CONFIG_I2C_MV64XXX=y

note that all mentioned drivers have to be =y and only DWMAC_SUN8I=m 

Expand  

I checked these options, they correspond to the specified values. Means the reason in availability of options from other platforms (RK and AML), which can hinder work AW.

Posted
  On 12/22/2019 at 4:57 PM, balbes150 said:

I checked these options, they correspond to the specified values. Means the reason in availability of options from other platforms (RK and AML), which can hinder work AW.

Expand  

@balbes150: fyi: I take special care with these options to have single kernel config working for AML/RK/ALW/BCM.

Tested on 7 hw platforms I have and those seems to work ok...

Posted

I figured out the kernel options, now the generic image (RK+AML+AW) starts up normally and works with the wired network on TX6. In the near future I will upload a new version of images 20191224 with support for AW.

Posted

The list of changed options is quite long, part from RK, part from AML and there were "extra" options for AW (for sunxi4). :)

Posted

@balbes150 Just build Armbian from your repo, used the aw-h6-tv config and flashed SD. Booted Eachlink H6 Mini and it seems to be working pretty good. Wired network works and I used the console uart mod from here. Made it crash by installing some apt packages. 

Ooops here:

  Reveal hidden contents

 

Posted

@Redferne - try to add mem=2048M to the kernel cmdline - the eachlink h6 mini otherwise detects the memory wrong as 3gb although only 2gb are useable - thus it will crash as soon as it tries to access the part of the memory which does not really exist :)

 

best wishes - hexdump

Posted

I'm trying to add support for running from USB. Changed the polling order and added commands to the config for working with USB. Assembled u-boot. When checking, I see an attempt to initialize USB in the UART console, but the system shows that there are no USB controllers. As far as I understand, they should be described in the DTS used ? Or do I need to add something else to the u-boot source code ?

Posted

i have qidianz H6-6K series tvb, it seems almost the same with the tanix tx6 (H6 with DDR3)

this device is able to run tanix image "Tanix_H6_4Gddr_8822bs_20190228.img" from the sdcard. everything seems to be well except the wifi

 

nah,,, the problem is it still couldn't run any linux until now, for about a week have been working on it...

so far this is what i got, the success boot log from the Android and the stuck log from compiled linux Armbian 19.11.8 - Orangepi 3 (with few patch, LPDDR3 to DDR3)

 

hope anyone can tell what next step i should do on it... thanks...

android.logFetching info... linux-failed.logFetching info...

Posted
  On 1/16/2020 at 2:48 PM, zero said:

hope anyone can tell what next step i should do on it... thanks...

Expand  

Judging by the Armbian startup log, you are missing a working DTB for the kernel itself.

Posted
  On 1/17/2020 at 6:44 AM, balbes150 said:

Judging by the Armbian startup log, you are missing a working DTB for the kernel itself.

Expand  

 

ok thanks, i'll give it a try...

so far i only working on the u-boot part...

 

still have not touch or doing any patch on the kernel, i just copy it from a working kernel from my orangepi 3 board...

soon i'll report again... thank you..

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines