Oleksii

Members
  • Content Count

    21
  • Joined

  • Last visited

Everything posted by Oleksii

  1. How come, USB Type-C port will magically start working if there is no proper support for this in the mainline kernel for this board family? Even if kernel version is declared as stable, this doesn't mean that 100% of the "expected" functionality will work on 100% of the platforms. If you decided to base your work on the mainline kernel versions for this board, you should already know about hardware limitations related to the presence of proprietary vendor's drivers that are not really maintained by the vendor.
  2. USB Type-C port will work as USB 3.0 port in HOST ONLY mode (which, as it appeared, is enough for the vast majority). And the only needed and sufficient change for this: &usbdrd_dwc3_0 { dr_mode = "host"; }; is to be added to the DTB
  3. My Transcend 110S SSD stoped working due to some driver changes in v5.4. But started to work again since next 5.5
  4. If you are still interested in Type-C for mainline kernels. My patches at least explain what is missing in the present drivers and why this magic dr_mode = "host" is specified everywhere in the mainline dtbs
  5. Hello, nanopc t4 folks, Some, not so long time ago, I worked on fusb302.ko driver and device tree improvements in order to make USB Type-C port working properly in the mainline 5.* kernel. I managed to get DisplayPort over type-C + some general type-c handling improved before my board simply died. Unfortunately, I was not able to finish all the planned work and cannot continue further However, I guess, working DP is already fairly good achievement that might be interesting for many of us. Hereby, I want to publish some patches to the mainline!!! driver and device tree that add mis
  6. Oleksii

    M4 Died

    Thanks for advise! However, even this process will eat my time which I can more productively spend to make money for another SBC and preferably not FriendlyArm product this time I'm really disappointed and do not want to deal with a company like this anymore I gave them enough time and information to resolve the issue in a "Friendly" manner. I also spent my spare time trying to contribute to the mainline linux in order to make their boards more "Friendly". And now, it seems to me, I should look for another friends
  7. Oleksii

    M4 Died

    From what I read: "You own some RK based devices and they do work! But you stopped treating them seriously". In my situation all 100% of my RK-based SBCs are faulty "black sheeps"
  8. Oleksii

    M4 Died

    I wrote the e-mail to their tech support. No answer, indeed. Then posted my question to them via "Contact Us" form on website. No feedback ... I saw some other people complaining about boards dying with the same symptoms (one can even find some posts in the FriendlyARMs dedicated forum). I worked on mainline fusb302 controller driver extension in order to gain some missing functionality crucially needed for Rockchip's DisplayPort and Type-C drivers. I managed to get DisplayPort working properly on T4 in mainline 5.6+ kernels. My SBC simply died right in the middle of kernel sources compilation
  9. Hold on ... it seems you are going too deep and too everywhere Things are not so bad to learn and "fix" everything at once. IMHO, fusb302, extcons, alternate modes handling in PD protocol and Rockchip's CDN_DP driver are the only things that worth research if you just want to see a picture on your DP monitor
  10. It is not only a matter of compilation, some important stiff is not yet there, so nothing to compile to get proper Type-C in 5.* kernels Don't look for black cat in the dark room, it will not help ....
  11. Mainline kernel is of fairly decent quality in regard to most popular RK3399 boards. All critical components work fine and have really good support. But something, which makes such boards outstanding, still doesn't work in 5.* It is normal for the situation when vendor's developers are locked inside of their private sandboxes (they call it SDK, LTS branch whatever, we call it simpler - "legacy") and do not really see the world is bigger outside . However, I have good news for those who own RK3399 based SBCs with Fairchild FUSB302 controller responsible for type-c handling and power delivery
  12. Are you referring to mainline 5.* kernels? If so, display-port cannot work there due to such reasons: 1. If you enable cdn_dp node in device-tree, its driver will fail to bind making parent rockchip_drm driver to also fail due to incomplete structure - you will loose all other working video outputs (including HDMI) in this case This happens because of: 2. There is no extcon notifications support in the present fusb302.ko driver. Rockchip's cdn_dp driver doesn't simply know when DP sink is connected and what is current pin assignment without extcon notification. 3. There
  13. Oleksii

    M4 Died

    My NanoPC T4 seems also died today with same symptoms Yesterday it stopped booting from MMC with only red power-on light and no other attempts to boot... Then I inserted sd-card and managed to boot from it in MASKROM mode. So I decided that main image is corrupted and planned to play with recovery today. This morning, it couldn't boot at all, neither MMC nor even SD - still the same red light only and that's it. Then I connected the board to PC via type-c port. It was detected as MASKROM device, but attempt to clear internal flash simply failed. I tried different proven to work PSU (works fin
  14. It is not so obvious I only consider the state in the mainline kernel as a reference (because I decided for myself to track changes since 5.* only). And I see that USB Type-C controller changes its state from "host" to "gadget" and almost immediately powers off during the boot. It should be correctly handled automatically by the driver on this board according to my understanding. And forcing to host mode is imho just a workaround for some issue in the current driver (or some other problems in device tree).
  15. 1. I still have quite shallow understanding of Armbian's internals 2. I use most up-to-date kernel revisions all the time in experimental mode and those are always several month ahead of Armbian's I suppose 3. I'm not sure that forcing controller to host mode purposely is a right fix - I miss experience and knowledge for such decisions. I did it for my personal sake and my own risk and clearly admitted this in the message above 4. Submitting the code to community project - is about 100% confidence and responsibility for me 5. Just have a look on the DT overlays capabilitie
  16. Yep, most probably file names will collide I use custom 5.* kernels all the time with optimized configuration + some DT tweaks, so I don't usually care about linux-dtb-current-rockchip64 updates. And if you want to overcome this, you may simply give your customized *.dtb a new name (make sure it is also correctly specified in the armbianEnv.txt). As another option, TD overlay might be handy too. However, I would admit with every mainline kernel version increment I keep less and less of my custom patches For the moment, I have only one important that fixes Type-C on NanoPC T4 (and s
  17. I managed to make Type-C port working on 5.* kernels by forcing its mode to "host": &usbdrd_dwc3_0 { dr_mode = "host"; status = "okay"; };
  18. Hi @pkfox, First of all, here comes official support matrix: https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2-supported-os.md Seems, debian package source is not maintained for linux arm64, so we should install .net core manually from here: https://dotnet.microsoft.com/download/dotnet-core/2.2 As you can see, only .net core 2.2 runtime has relevant arm64 distribution and aspnet core 2.2 only present for 32-bit. However, according to this info https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore30 both will
  19. Frankly, I wouldn't even bother myself with active cooling, because I like silent PCs more I simply underestimated this RK3399's temperament. I also purchased metal case for this model which can hardly fit standard dimensions fan and provide really efficient air-flow. Thus, I will try to improve passive cooling first of all (put some copper shim + thermal grease instead of magic blue chewing gum e.g.). Then, maybe, I will look for a decent (slim and silent) PWM-capable 12V fan and connect wires by myself as shaun27 suggested before. I've searched online shops quite a lot, and now I'm almo
  20. Well, I anticipated such answer just a little bit of hope there might be some ready-to-go solutions already... Thank you!
  21. I'm about to install active cooling fan on my recently delivered nanoPI T4. However, I cannot get what is a type of the soldered 3-pin fan connector on this board? What I see there is visually too small as for standard connector size. Is it something special I have no clue about yet, or it is for future proprietary Friendlyarm's fan designed specially for the board? Any suggestions are welcome! Thanks