-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
1 hour ago, Marcomarco said:
I used the same wires on Rpi2 and on the opi 1+. I attached a picture
I can't see clearly what are the pins on this relay board, neither if it is using a MOSFET or not, which is important since GPIO are 3V only ...
-
8 minutes ago, iav said:
read how to "use this overlay source and compile it and load it"?
Install DT compiler from http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler_1.4.7-3_arm64.deb
Then, compile the DTS I've provided and then load it dynamically :
dtc -@ -I dts -O dtb -o odroid-n2-ic2@1c000.dtbo odroid-n2-ic2@1c000.dts mkdir /sys/kernel/config/device-tree/overlays/i2c3a cat odroid-n2-ic2@1c000.dtbo > /sys/kernel/config/device-tree/overlays/i2c3a/dtbo
-
7 minutes ago, Marcomarco said:
Everything seems to work but the relay doesn't open/close the contact.
How did you wired the relay ?
Do you use a MOSFET to drive it ?
-
11 hours ago, Burschi500 said:
I also have no i2c bus, in /dev/ there is only i2c-0.
Odroid-N2 external RTC is attached on I2C3 which isn't enabled by default.
To enable it, use this overlay source and compile it and load it.
/dts-v1/; /plugin/; / { compatible = "amlogic,meson-g12b"; fragment@0 { target-path = "/aliases"; __overlay__ { i2c3a = "/soc/bus@ffd00000/i2c@1c000"; }; }; fragment@1 { target-path = "/soc/bus@ffd00000/i2c@1c000"; __overlay__ { status = "okay"; pinctrl-0 = <&i2c3_sda_a_pins>, <&i2c3_sck_a_pins>; pinctrl-names = "default"; pcf8563: rtc@51 { /*I2C-bus slave address: read A3h and write A2h*/ compatible = "nxp,pcf8563"; reg = <0x51>; }; }; }; };
Then, the i2c will appear as well as module for PCF8563 will be loaded, it will be hookup as /dev/rtc1, you can then set the clock and re-read it using :
hwclock -w -f /dev/rtc1 hwclock -f /dev/rtc1
-
On 3/30/2020 at 12:19 PM, iav said:
How to set hardware clock correctly?
Odroid-N2 external RTC is attached on I2C3 which isn't enabled by default.
To enable it, use this overlay source and compile it and load it.
/dts-v1/; /plugin/; / { compatible = "amlogic,meson-g12b"; fragment@0 { target-path = "/aliases"; __overlay__ { i2c3a = "/soc/bus@ffd00000/i2c@1c000"; }; }; fragment@1 { target-path = "/soc/bus@ffd00000/i2c@1c000"; __overlay__ { status = "okay"; pinctrl-0 = <&i2c3_sda_a_pins>, <&i2c3_sck_a_pins>; pinctrl-names = "default"; pcf8563: rtc@51 { /*I2C-bus slave address: read A3h and write A2h*/ compatible = "nxp,pcf8563"; reg = <0x51>; }; }; }; };
Then, the i2c will appear as well as module for PCF8563 will be loaded, it will be hookup as /dev/rtc1, you can then set the clock and re-read it using :
hwclock -w -f /dev/rtc1 hwclock -f /dev/rtc1
-
1 minute ago, gounthar said:
If there is one better suited library for the Zero, I will gladly use it.
There is also this one, although not a fork of the previous : https://github.com/Jeremie-C/OrangePi.GPIO
-
1 minute ago, gounthar said:
I see...
Why don't you use well known lib like :
https://github.com/duxingkei33/orangepi_PC_gpio_pyH3
I think there is also a fork of it for specific OPiZero, which will avoid tweaking the mapping.h for the pins.
-
36 minutes ago, spikerguy said:
Any idea about kernel source for NeoPlus2 ?
If you look at Armbian build scripts, since NanoPiNeoPlus2 is an Allwinner H5 SoC, it is usual megous's github here :
Current : https://github.com/megous/linux/tree/orange-pi-5.4
Dev : https://github.com/megous/linux/tree/orange-pi-5.6
-
16 hours ago, braineniac said:
should I try to write my own overlay? Is that even doable?
I think writing your own overlay would be the most easy approach ...
Which board are you using ?
-
Lets say that the easiest way to clone a running SDCard is to blindly the first sectors where u-boot reside using "dd" :
dd if=/dev/mmcblk0 of=/dev/sda bs=1024 count=2048
Then, after that blind copy, you can use "gparted" like you did previously.
-
5 hours ago, dolphs said:
Err I assume it has been committed after all
Right ! Just a typo : "not" != "now"
-
10 hours ago, sfx2000 said:
mostly with how the chip is ID'd
If you look at U-Boot drivers/mtd/spi/spi-nor-ids.c, you will see that GigaDevice are well supported ...
-
6 minutes ago, Superkoning said:
Do you want me to change that for the existing posts?
You can also use spoiler
tags ...
-
-
12 hours ago, sfx2000 said:
Because they are not one for one replacements on the SPI-NOR...
But again, what are the differences that you found ?
(I was looking quickly at both GigaDevice and Winbond datasheets, and I didn't found any difference until now)
-
4 minutes ago, Tido said:
there are some PCB manufacturer that do also the assembly
Right ! But never tried such services ...
-
According to grep results on /boot/config* , CONFIG_CDROM=m is present on allwinner, rockchip, but not amlogic meson ...
-
10 hours ago, sfx2000 said:
but not 1 for 1 replacement.
What are the differences ?
-
1 hour ago, MaxT said:
FYI, ayufan updated to 5.6
That interesting ...
Last time I checked, he didn't even manage to complete 5.4.0-rcX, and I ask him around Christmas if he will update 5.4.0 without RC and also start 5.5.y, and he answered me "after holidays", which he didn't ...
-
You can use it with 12VDC and add a DC-DC converter at the end to produce the required 5VDC.
-
12 minutes ago, Cybrpunk said:
Could you please tell me when you expect your work to be done
Couple of days maybe ...
13 minutes ago, Cybrpunk said:because we are dependent on this LCD and the peripherals
What do you mean ? I don't work on any LCD, I'm just making DEV branch working with 5.6.y ...
-
Using Armbian build scripts, the patch should be placed into build/patch/kernel/sunxi-dev, then start the build.
You can look at build/output/debug/patching.log to see if it been applied properly ...
-
2 minutes ago, Igor said:
Have you manage to fix it in the mean time?
I've done a fresh "git clone" to get rid of the issue.
I'm now doing a new a new "tour of my Allwinner garden" with 5.6.1, and then I will do some commits ...
-
Redoing my work on a clean branch, I've just figured out that we have two RTL8723CS drivers in the tree ...
One is added using Armbian patch pushing code into driver/net/wireless/realtek and there is already another one in cache/sources/linux-mainline/orange-pi-5.5/drivers/staging/rtl8723cs-new that have been added since 5.5.y back in January.
@Igor, I think we should use the later since Smaeul and Ondrej have even done some "suspend" fix recently ...
ODroid-N2 RTC not work in linux-image-current-meson64=20.02.8 5.4.28-meson64
in Beginners
Posted
I'm one of the main Armbian devs, so, yes, I will add the DT overlay in builds in the near future ...