MX_Master

I'm trying to use H6's ARISC (CPUS) core for my CNC project https://allwincnc.github.io/ There are no problems to switch ARISC (CPUS) clock source using H3 and H5 (latest Armbian Buster). I'm using R_PRCM (0x01F01400) > CPUS_CLK_REG (offset 0x0000) register to switch clock source to the PERIPH0 PLL. For the H3 I'm using uboot script, for the H5 - own kernel module. But for the H6 this register (R_PRCM) isn't properly documented. Found out this register was moved to the 0x07010000. But modifying this register at offset 0x0000 doesn't take any effect. Just checked this using uboot cmd and own kernel module. I need your help. guys. Any suggestions how to switch H6's ARISC (CPUS) clock to the PERIPH0 PLL? Is it possible this memory region is protected from uboot and linux kernel?

Try any gpio lib with pull up/down features included. For example: https://github.com/rm-hull/OPi.GPIO Pulling usage examples are here https://opi-gpio.readthedocs.io/en/latest/api-documentation.html

Pull up or pull down the pin using built-in 50k resistors. And compare the results.

See the a/arch/arm64/Kconfig section and compare it with other popular platforms lsdiff patch-5.4.22-rt13.patch | grep x86 filterdiff -i a/arch/x86/Kconfig patch-5.4.22-rt13.patch lsdiff patch-5.4.22-rt13.patch | grep arm64 filterdiff -i a/arch/arm64/Kconfig patch-5.4.22-rt13.patch

There's no PREEMPT_RT option for the arm64 inside patch-5.4.22-rt13.patch

If you want to use a 'big' apps like Chromium, setup a proper cooling for the board

Какой блок питания используется? Достаточно ли он мощный (5v, 2a)? Какое охлаждение у платы? Радиатор на процессоре есть?

Armbian image version? Chromium error logs? Версию системы, версию ядра, и прочие логи в студию

More tests results is here Using same desktop image (v20.02.1 buster). But this time with old kernel v4.19.38 from here https://apt.armbian.com/pool/main/l/linux-4.19.38-sunxi/. Same steps as before were made. And performance results are the same! I think the problem can be with armsoc+X11 pair. To prove that fact I installed an old package xserver-xorg-video-armsoc-sun4i instead of building it from the sources. Performance became very very low.

Your truth I forgot to `apt update` first. My bad. Thanks

https://dl.armbian.com/orangepipc/archive/ Armbian_20.02.1_Orangepipc_buster_current_5.4.20_desktop.7z Just checked a fresh buster desktop image. And found a tiny issue. If you will try to install linux-headers-current-sunxi using the latest v20.02.1 image (buster, K5.4.20), you will get the v5.3.9 headers It would be nice to get the v5.4.20 headers instead Quick tip for other users - headers package can be found here - https://apt.armbian.com/pool/main/l/linux-5.4.20-sunxi/

Big respect waiting for news

Just made a fullscreen test with glmark2 and the results are glmark2-es2 --fullscreen ======================================================= glmark2 2017.07 ======================================================= OpenGL Information GL_VENDOR: ARM GL_RENDERER: Mali-400 MP GL_VERSION: OpenGL ES 2.0 ======================================================= [build] use-vbo=false: FPS: 10 FrameTime: 100.000 ms [build] use-vbo=true: FPS: 14 FrameTime: 71.429 ms [texture] texture-filter=nearest: FPS: 16 FrameTime: 62.500 ms [texture] texture-filter=linear: FPS: 15 FrameTime: 66.667 ms [texture] texture-filter=mipmap: FPS: 14 FrameTime: 71.429 ms [shading] shading=gouraud: FPS: 10 FrameTime: 100.000 ms [shading] shading=blinn-phong-inf: FPS: 9 FrameTime: 111.111 ms [shading] shading=phong: FPS: 10 FrameTime: 100.000 ms [shading] shading=cel: FPS: 7 FrameTime: 142.857 ms [bump] bump-render=high-poly: FPS: 7 FrameTime: 142.857 ms [bump] bump-render=normals: FPS: 14 FrameTime: 71.429 ms [bump] bump-render=height: FPS: 11 FrameTime: 90.909 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 7 FrameTime: 142.857 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 7 FrameTime: 142.857 ms [pulsar] light=false:quads=5:texture=false: FPS: 15 FrameTime: 66.667 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 3 FrameTime: 333.333 ms [desktop] effect=shadow:windows=4: FPS: 10 FrameTime: 100.000 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 3 FrameTime: 333.333 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 3 FrameTime: 333.333 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 3 FrameTime: 333.333 ms [ideas] speed=duration: FPS: 11 FrameTime: 90.909 ms [jellyfish] <default>: FPS: 7 FrameTime: 142.857 ms Error: SceneTerrain requires Vertex Texture Fetch support, but GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS is 0 [terrain] <default>: Unsupported [shadow] <default>: FPS: 7 FrameTime: 142.857 ms [refract] <default>: FPS: 6 FrameTime: 166.667 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 15 FrameTime: 66.667 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 6 FrameTime: 166.667 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 14 FrameTime: 71.429 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 10 FrameTime: 100.000 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 7 FrameTime: 142.857 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 10 FrameTime: 100.000 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 10 FrameTime: 100.000 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 10 FrameTime: 100.000 ms ======================================================= glmark2 Score: 9 ======================================================= I don't no, but performance is very low OK, i got it, X11 + mali is totally bad idea. It's time to test something with direct rendering to fbdev

OK, I will make some fullscreen tests and will show the results. Also I heard about another installing method for the mali drivers/blobs. It's using ump cacher and libdri2 for direct rendering (without Xorg).

There are many use cases of r6p2 blobs a few years ago using kernel v4. 14. And all of them were pretty successful. Performance of es2gears was about 300fps. Software rendering can do only 100 fps on idle system. So, I think, in my case something goes wrong. While running the es2gears, Xorg uses the 99% of CPU core. It's very abnormal for the hardware acceleration