martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
On 9/19/2021 at 11:30 AM, Satyr said:
So, nobody knows ?
The DT overlay isn't written to support multiple buses ...
But, again, why do you need more than one bus, since OneWire support multiple devices on the same bus ?
-
On 9/5/2021 at 4:23 AM, Satyr said:
How to create more then one w1-gpio bus ?
Why do you need more than one bus ?
You can have multiple devices on the same bus ...
-
32 minutes ago, kentAVR said:
So how U-Boot knows about /boot/armbianEnv.txt ? There is no "/boot/armbianEnv.txt" in U-Boot source code...
If you look at /boot/boot.cmd (which then compiled into /boot/boot.scr), there is a line where /boot/armbianEnv.txt is loaded in memory and then "env import" is executed ...
-
2 hours ago, lanefu said:
yeah honestly I doubt any of us have tried emmc on the H5...
Personnally, I'm running on eMMC with other boards such OPi-ZeroPlus2-H5 since years ...
-
15 hours ago, Werner said:
@martinayotte maybe?
I will try, but daily job take most of my time these days ...
-
Sorry, completely forgot to join, it was too sunny outside ...
-
On 3/9/2021 at 1:35 PM, derpeter said:
Any advice where to go from here to help with fixing the issue would be very appreciated.
With the help of @megi / @megous , I've now my Pinebook-A64 LCD working.
Here is the patch : https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426
-
On 3/9/2021 at 1:35 PM, derpeter said:
So while i`m not familiar with the the details of the display init i assume this is not the display but the gpu / drm driver crashing.
I've tried for months to clarify the reason of such issue ...
My last working kernel was 5.7.6, and the issue appeared as soon as 5.8.0, I've done "diff" between both branches and I still didn't figured out the glitches ...
-
2 hours ago, guidol said:
Thanks for your commit
I've reverted my commit since now the original github has the changes done directly by CGarces ...
-
5 hours ago, guidol said:
I disabled the module
If you look at the resulting image, maybe the rtl8189fs.ko is still present and broken ...
Anyway, I've done builds+tests on all my OPi which using this rtl8189, and results are successful, I've done this commit :
https://github.com/armbian/build/commit/bba53d4644e83cd46b80820b5835ad7c2e7691e5
-
16 minutes ago, guidol said:
Thanks I will keep that in mind
I've just done new build with a 8189fs patch, it seems to work on my OPiPC+ ...
I will check other boards this afternoon. Now time to do some snowshows ...
-
Just now, guidol said:
does this prevent from booting up complete?
Yes, and No ... it prevent all networking if WiFi is present, such as running "ifconfig" will hang forever.
Simply move or delete the 8189fs.ko module will prevent that.
-
55 minutes ago, guidol said:
seem to make some trouble
It seems that NanoPi K1 Plus is using rtl8189 WiFi ... Right ?
Driver is broken in 5.11, I'm working on it with other guys, I'm using OPiPC+/OPiLite/OPiPlus2E.
In the mean time, if you don't need WiFi, disable the module :
mv /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko-disabled -
3 hours ago, ebalcsk said:
Sorry it was my fault
Do you mean that UART3 is working fine ?
-
10 minutes ago, ebalcsk said:
5.10.12-sunxi64
Could you check DTS directly by decompiling DTB ?
dtc -@ -I dtb -O dts -o /root/sun50i-h6-orangepi-one-plus.dts-5.10.12 /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb -
-
50 minutes ago, ebalcsk said:
I try to communicate on UART3
Can you check DT if pinctrl-0 is present in UART3 node ?
You can verify using this :
ll /proc/device-tree/soc/serial@5000c00(In my old 5.9 build, I see that they are missing and only UART0 has its pinctl-0 handle.)
If missing, you can decompile DTB into DTS, edit DTS to add "pinctrl-0 = <phandle>;" where phandle can be found in "uart3-pins" node ...
-
4 hours ago, xkcd said:
but nothing at /dev/spidev/
It won't appear as subfolder, but as direct node /dev/spidev0.0 ...
Also, check with "dmesg | grep spi" ...
-
20 hours ago, Lukas S said:
Sorry I didn't find it in overlay documentation that this flag is needed ^^
Look at this doc file : /boot/dtb/overlay/README.sun8i-h3-overlays
-
1 hour ago, Lukas S said:
Thanks in advance
You've forgot to define "param_spidev_spi_bus" which is mandatory ...
-
-
3 hours ago, sgjava said:
This is the step I'm missing.
I'm not understanding exactly.
Maybe because I've always producing patches manually ...
Here is a summary of how I would do it :
(edit the file to add "gpio-line-names" manually) nano cache/sources/linux-odroidxu4/odroid-5.4.y/arch/arm/boot/dts/exynos5420-pinctrl.dtsi (save) pushd cache/sources/linux-odroidxu4/odroid-5.4.y/ git diff arch/arm/boot/dts/exynos5420-pinctrl.dtsi > ~/my-gpio-line-names.patch popd mv ~/my-gpio-line-names.patch patches/kernel/odroidxu4-dev/odroidxu4-add-gpio-line-names.patch -
28 minutes ago, sgjava said:
each pinctrl using phandle to identify
Be carefull : phandle can vary between builds, so better use <&pio> and <&r_pio> symbols.
30 minutes ago, sgjava said:So next question is how do I make this part of build process
As I said earlier, append you overlay code in some new board specific patch such as ./patch/kernel/sunxi-dev/nanopi-duo/board-h2plus-nanopi-duo-add-overlay.patch which will also provide change to arch/arm/boot/dts/overlay/Makefile.
-
50 minutes ago, sgjava said:
Yes, I'm wondering is that another fragment section in one file or another file?
I would choose to simply add another fragment in the same overlay ...
RTS signal and uart2 init
in Orange Pi Zero
Posted
I don't know ... I've worked on this since almost a year ...