Gunjan Gupta

If you are not able to understand what ag123 posted, I am guessing you also have no Idea about what an NPU is. You just took some tech jargons, started a thread to look cool with no Idea about what you are asking for. And when people tried to ask for explanation or tried explaining to you that you are not making sense, then you simply started insulting everyone. If that is the case, I suggest we lock and delete this thread. Its not helping anyone.

Alright, lets move the world forward together. How about you book a session for consultation and pay for the same - https://calendly.com/armbian/consultation?month=2024-01. We can discuss about what needs to be done there. Then you fund the development and we will happily work on it maybe even fulltime depending upon how much you are willing to fund.

@MaksimarmYou are evading the first ever question asked in reply to your thread, which is what you meant by migrating io scheduler to NPU. As I believe will be the case with most of us, when someone says NPU we will think about Neural Processing Units which are for use with AI inferences and hence something that will be used by end users. It has nothing to do with IO scheduler as explained by ag123 above as well. Hence we did asked you what you mean't by it as it does seem like you are clearly not talking about the same thing or have different understanding of the same.

I guess copy paste error from Orange Pi's repository. I do remember changing it to ok, but I guess I forgot to include that in the commit.

I have never tried doing it but I will guess either https://docs.armbian.com/User-Guide_Fine-Tuning/#swap-for-experts or disabling armbian-zram-config.service should disable zram

As you mentioned you had a serial adapter plugged into zero2 but not to the pc, its possible that the uart adapter might have sent some garbage character just when it says press any key to stop booting and hence it got stopped there. I have seen that happens sometimes when my serial adapters usb plug touches some metal or when I touch the same.

Is there any output on serial console?

As this is not orange pi 4 that is being used, moved the thread to community forum and removed orange pi 4 label

from armbianmonitor logs BOARD=mkspi BUILD_REPOSITORY_COMMIT=ed589b248-dirty This is not a board that we support. Either you have patched the build framework yourself to build for this board, or you are using some third party provided image. This is important because that means we never had any patches to support this board and that is why you are having issues after upgrade. Whoever build the image needed to specify SKIP_ARMBIAN_REPO=yes to make sure that kernel won't get upgraded from Armbian repo. As we never supported this board and never had any patches for this, its pretty much common sense that upgrading kernel from our repo will break functionality Ask where you got the image from. We can't provide support for the board that we never supported.

@NicoDCould you please guide the user on how to install armbian on vim3

if you have compiled the images yourself, its possible that you will be having the headers package in the output/debs/ directory. You should be able to install them using the deb file from there.

Moved to community forums and relabeled to reflect the correct board.

I am not the maintainer for vim3, but I do see some instructions on the download page - https://www.armbian.com/khadas-vim3/

You already posted this 12 hours ago. Why are you posting this again?

I don't have the screen. So I can't say if its working or not. If you have it, please try and let us know if you are facing any issues.

I would recommend you to get a fan. Vim4 does run hot. But its not the cause of the issue. The same issue is also there on the NPU model We are aware of the issue and are working on the same. Please be patient. A fix will be released once ready

Just a generic advice for both overlay and fixup script, look for whats done for H3, H5 and H6. Do something similar

I dont think it hurts to create more overlays. As most of the overlays provided by armbian for other allwinner soc's are for generic functionality, like enabling i2c but not configuring the same for connecting a specific peripheral like a temperature sensor, I believe same can be done here as well.

Yes the driver is not there. The driver code is from allwinner bsp kernel and is not in mainline linux kernel

Not really, Both hdmi and anolog audio is broken on all h616/h618 boards. This is what needs to be added for the same - https://github.com/orangepi-xunlong/linux-orangepi/commit/cfe0a8df18c2418f77acb24b17b88c9271d9613c#diff-b340c978bcdbe240f7b99f4d0d96ea130a8acb1a5786a8efbb24d9e7a0b14e53. Also its corresponding dts nodes along with dma node will be needed. I don't think we need to make modification to the dma driver like done here - https://github.com/orangepi-xunlong/linux-orangepi/commit/a86c734824acc775c3de5abc48fd48912087d73b. Instead we can just use compatible string as allwinner,sun50i-h6-dma in the dma node within dts. Settings used for h616 and h6 for dma looks exactly the same and hence using h6's compatible string should be enough. also the corresponding asound.state file will be needed to ensure alsa is properly initialized.

You already know what change needs to be done. All that is left is fork the armbian/build project on github, clone your fork, make and commit the change there and then push it back to github. Then whats left is creating a PR and github's UI will guide you with that. If you are not familiar with git and github that much, I am pretty sure you can find plenty of videos for the same on youtube that will walk you through it

The pin arrangement on the board can be different. But what pins can be used for what functionality is something that is fixed for the SoC. The pin PH9 for example, doesn't mean 9th pin on the header. Its the PH9 pin exposed on the h618 soc and will remain the same no matter whether that is exposed on header or used on the board to connect to some other device.

You are using a very old release. Please upgrade to latest image if possible. USB should work fine in 23.11 image.

with no logs shared, there is nothing that we can use to figure out what might be the issue. Upload logs using armbianmonitor -u and share the link here

Raise a PR and I will review and merge. I volunteered to be the maintainer for the board, but that doesn't mean I am the only one that can raise the PR for the same. Currently I am working on a vim1s and vim4 issue, so am a bit busy trying to figure that out. Until thats solved, I trust the community to take care of the development for this board.