arhi

figured it out adding "overlays=i2c0" to /boot/armbianEnv.txt solved the problem ..

mainline kernel/armbian here, "Welcome to ARMBIAN 5.27 stable Debian GNU/Linux 8 (jessie) 4.10.11-sun8i" but I can't find a way to use i2c .. starting to feel frustrated .. (not with the system but with myself, feeling overly stupid with these oranges) so I'd really appreciate some help I tried few libs, examples.. etc.. but they all expect /dev/i2c* to exist.. but I don't have those root@orangepione:~/nekiliksaforuma/orangepi_PC_gpio_pyH3# modprobe i2c-dev root@orangepione:~/nekiliksaforuma/orangepi_PC_gpio_pyH3# modprobe --show-depends i2c-dev builtin i2c_dev root@orangepione:~/nekiliksaforuma/orangepi_PC_gpio_pyH3# ls -lad /dev/i2c* ls: cannot access /dev/i2c*: No such file or directory root@orangepione:~/nekiliksaforuma/orangepi_PC_gpio_pyH3# ls -lad /dev/i* lrwxrwxrwx 1 root root 25 Jan 1 1970 /dev/initctl -> /run/systemd/initctl/fifo drwxr-xr-x 3 root root 80 May 23 13:17 /dev/input root@orangepione:~/nekiliksaforuma/orangepi_PC_gpio_pyH3# I have the orangepi_PC_gpio_pyH3 you mentioned but don't see how to use it for i2c now, I see further down the thread that DTB thingy needs to be changed but I'm stuck with it ... attm I have wrt i2c pinctrl@01c20800 { compatible = "allwinner,sun8i-h3-pinctrl"; reg = <0x1c20800 0x400>; interrupts = <0x0 0xb 0x4 0x0 0x11 0x4>; clocks = <0x2 0x36 0x9 0xb>; clock-names = "apb", "hosc", "losc"; gpio-controller; #gpio-cells = <0x3>; interrupt-controller; #interrupt-cells = <0x3>; linux,phandle = <0x11>; phandle = <0x11>; i2c0 { allwinner,pins = "PA11", "PA12"; allwinner,function = "i2c0"; allwinner,drive = <0x0>; allwinner,pull = <0x0>; linux,phandle = <0x1d>; phandle = <0x1d>; }; i2c1 { allwinner,pins = "PA18", "PA19"; allwinner,function = "i2c1"; allwinner,drive = <0x0>; allwinner,pull = <0x0>; linux,phandle = <0x1e>; phandle = <0x1e>; }; i2c2 { allwinner,pins = "PE12", "PE13"; allwinner,function = "i2c2"; allwinner,drive = <0x0>; allwinner,pull = <0x0>; linux,phandle = <0x1f>; phandle = <0x1f>; }; ... i2c@01c2ac00 { compatible = "allwinner,sun6i-a31-i2c"; reg = <0x1c2ac00 0x400>; interrupts = <0x0 0x6 0x4>; clocks = <0x2 0x3b>; resets = <0x2 0x2e>; pinctrl-names = "default"; pinctrl-0 = <0x1d>; status = "disabled"; #address-cells = <0x1>; #size-cells = <0x0>; linux,phandle = <0x54>; phandle = <0x54>; }; i2c@01c2b000 { compatible = "allwinner,sun6i-a31-i2c"; reg = <0x1c2b000 0x400>; interrupts = <0x0 0x7 0x4>; clocks = <0x2 0x3c>; resets = <0x2 0x2f>; pinctrl-names = "default"; pinctrl-0 = <0x1e>; status = "disabled"; #address-cells = <0x1>; i2c@01c2b400 { compatible = "allwinner,sun6i-a31-i2c"; reg = <0x1c2b000 0x400>; interrupts = <0x0 0x8 0x4>; clocks = <0x2 0x3d>; resets = <0x2 0x30>; pinctrl-names = "default"; pinctrl-0 = <0x1f>; status = "disabled"; #address-cells = <0x1>; #size-cells = <0x0>; linux,phandle = <0x56>; phandle = <0x56>; }; ... i2c@01f02400 { compatible = "allwinner,sun6i-a31-i2c"; reg = <0x1f02400 0x400>; interrupts = <0x0 0x2c 0x4>; pinctrl-names = "default"; pinctrl-0 = <0x26>; clocks = <0x23 0x6>; clock-frequency = <0x186a0>; resets = <0x25 0x6>; status = "disabled"; #address-cells = <0x1>; #size-cells = <0x0>; linux,phandle = <0x5c>; phandle = <0x5c>; }; ... pinctrl@01f02c00 { compatible = "allwinner,sun8i-h3-r-pinctrl"; reg = <0x1f02c00 0x400>; interrupts = <0x0 0x2d 0x4>; clocks = <0x23 0x0 0x9 0xb>; clock-names = "apb", "hosc", "losc"; resets = <0x25 0x0>; gpio-controller; #gpio-cells = <0x3>; interrupt-controller; #interrupt-cells = <0x3>; linux,phandle = <0x29>; phandle = <0x29>; ir@0 { allwinner,pins = "PL11"; allwinner,function = "s_cir_rx"; allwinner,drive = <0x0>; allwinner,pull = <0x0>; linux,phandle = <0x5d>; phandle = <0x5d>; }; r_i2c@0 { allwinner,pins = "PL0", "PL1"; allwinner,function = "s_twi"; allwinner,drive = <0x0>; allwinner,pull = <0x0>; linux,phandle = <0x26>; phandle = <0x26>; }; ... and more .. no clue how to solve the problem

thanks a million, that's what I was looking for

Ah good to know, far from important at this stage to get csi working. Thanks for the info! Would be interesting to have it in future. Is there a "supported stuff matrix" for different kernel "lines" (as a complete noob with linux on arm the "mainline" is not really clear to me yet, any link with explanation on what is available, what to expect from what etc?)

I see in the lib/extras-buildpkgs there's fswebcam-gc2035 config but I see no way how to build the kernel with support for gc2035 ? I built "Linux orangepione 4.10.11-sun8i #2 SMP Tue Apr 18 17:55:20 CEST 2017 armv7l GNU/Linux" but it does not recognise gc2035 and there's no gc2035 module anywhere to be found I have ./kernel/drivers/usb/gadget/legacy/g_webcam.ko ./kernel/drivers/media/usb/stkwebcam/stkwebcam.ko but nothing wrt gc2035 I also found https://github.com/avafinger/gc2035.git that's supposedly "better driver" for gc2035, but it's for 3.x kernel, don't see a way to get it into 4.10.11 kernel anyone with idea how to proceed?

thanks for confirming I'm not doing anything wrong .. that's important 'cause I was running in circles for a while.

that's weird what's even weirder, if I go and edit /etc/network/interfaces and add hwaddress ether ... and reboot it boots with old mac address but does not get ip from the dhcp server .. if I manually ifconfig eth0 hw ether .. it changes the mac address but again restarting networking won't get dhcp ip addr ?!?! totally weird.. will reconfigure other devices for the new mac on this one but weird that I can't change it will have to look how the u-boot works, it's attm complete mystery to me

I'm trying to get my MAC address on my orangepi-one to be what it used to be before the upgrade to "ARMBIAN 5.27 stable Debian GNU/Linux 8 (jessie) 4.10.11-sun8i" but I'm having dificulty I tried decompiling /boot/dtb/sun8i-h3-orangepi-one.dtb and adding mac-address = [52 53 3d 80 aa 0c]; few other tries, then tried mac-address = <0x52 0x53 0x3d 0x80 0xaa 0x0c>; in the ethernet@1c30000 { section: latest version looks like: ethernet@1c30000 { compatible = "allwinner,sun8i-h3-emac"; syscon = <0x20>; reg = <0x1c30000 0x104>; interrupts = <0x0 0x52 0x4>; resets = <0x2 0xc>; reset-names = "ahb"; clocks = <0x2 0x1b>; clock-names = "ahb"; #address-cells = <0x1>; #size-cells = <0x0>; status = "okay"; phy-handle = <0x21>; phy-mode = "mii"; allwinner,leds-active-low; linux,phandle = <0x57>; phandle = <0x57>; mac-address = <0x52 0x53 0x3d 0x80 0xaa 0x0c>; mdio { #address-cells = <0x1>; #size-cells = <0x0>; linux,phandle = <0x58>; phandle = <0x58>; ethernet-phy@1 { reg = <0x1>; clocks = <0x2 0x43>; resets = <0x2 0x27>; linux,phandle = <0x21>; phandle = <0x21>; }; }; }; I recompile this DTS to DTB (over the old one that I have backed up) dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb mv sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.original vi sun8i-h3-orangepi-one.dts dtc -O dtb -I dts -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts but I'm still getting old mac address after reboot !? I have zero experience with u-boot (if that's what's being used to boot this, I don't know for sure) or armbian till today so any help appreciated

I compiled and booted the "experimental" image (could not find with what to patch kernel to get display working) and yey, the display works .. now I just hope it's stable enough for the few simple tasks I need it to do thanks

Good question I would like to understand how "just keeping the same resolution that is set by the bootloader after kernel loads" is a problem :D.. it's not relevant to my current issue, just my curiosity and wanting to know more about linux internals as the way I get it when arm boots up it will load the bootloader (u-boot ?) from the sd card that will init the screen and load the kernel.. I assumed the kernel and the bootloader from the same repo are maintained by same team so that they support same resolutions Back to the question at hand, I think patching the kernel is more interesting to me as I'd like to figure out how to recompile the kernel for these embedded systems (lot of experience with linux on PC, no experience with linux on embeded systems, arm .. at all). This what I have: Welcome to ARMBIAN 5.25 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i System load: 0.88 Up time: 33 sec Memory usage: 16 % of 494Mb IP: 192.168.90.61 CPU temp: 44°C Usage of /: 20% of 7.2G Last login: Sat Apr 1 22:59:03 2017 from 192.168.89.6 root@orangepione:~# uname -a Linux orangepione 3.4.113-sun8i #10 SMP PREEMPT Thu Feb 23 19:55:00 CET 2017 armv7l GNU/Linux root@orangepione:~# Any links to "what to patch it with and how to compile the darn thing" I just started going trough and https://docs.armbian.com/Developer-Guide_Build-Preparation/ and looks like I'll have to get ubuntu on some of the boxes (I use mostly redhat myself), that's not the big deal, but I don't see with what to patch the kernel to get this resolution issue solved thanks

Hi guy's, trying to get my hdmi screen to work on some board (not really relevant but board is orangepi on and lcd is "7inch hdmi lcd (c), usb capacitive touch screen, 1024x600, rev 2.1" - the box it came in states brand is "waveshare") with armbian and I'm having issues. I don't care too much of getting screen to work "ideally", having txt console working is all I need. When I turn the board on I see everything properly, background is, as expected black, letters are white + some colors, it starts the booting process, looks for mmc controller, ethernet etc etc.. then it finds the kernel and start loading it and then - puf, the screen is gone... depending on what h3disp option I use I get different behaviors (from going slowly all white to filling slowly screen white from corner pixel by pixel..) but not a single option gave me visible picture (when I connect some big "normal" monitor I see the console). So, the "pre kernel" screen is visible, is there any way I can configure armbian to keep "that" hdmi output after kernel boots up?