J.M.

  • Content Count

    9
  • Joined

  • Last visited

  1. After a short break I just want to update that I’ve managed to enable the i2c-3 on boot. The truth is that it was too simple… (later I’ll explain what was the mistake). All I’ve needed to do is: 1. Update the boot device tree (cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts) with: &i2c3 { pinctrl-names = "default"; pinctrl-0 = <&i2c3_pins_a>; status = "okay"; }; I guess that instead of updating the boot device tree, I could also just update /boot/armbianEnv.txt with: overlays=i2c3 2. Update Lamobo_R1_deconfig file w
  2. First I must to correct my mistake: I meant that cache/source/u-boot/v2019.04/configs/Lamobo_R1_defconfig and cache/source/u-boot/v2019.04/.config holds the same configuration. (I was afraid that maybe my modifications on Lamobo_R1_defconfig doesn't set on .config) In both Lamobo_R1_defconfig and .config these are my modifications, but the i2c still doesn't work (or presented on the device tree) on u-boot: CONFIG_I2C0_ENABLE=y CONFIG_I2C1_ENABLE=y CONFIG_I2C2_ENABLE=y CONFIG_I2C3_ENABLE=y CONFIG_I2C4_ENABLE=y CONFIG_DM=y CONFIG_DM_I2C=y C
  3. i did checked it, and configs in your cache/source/u-boot/v2019.04/.config and cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts seems to hold the same configuration... Perhaps I'm not defining the device tree correct at u-boot ? (this is the same as I did to the device tree in linux - and in linux it work) &i2c3 { pinctrl-names = "default"; pinctrl-0 = <&i2c3_pins_a>; status = "okay"; }; jkjhk
  4. Thanks! I did it, and I see that: fdtfile=sun7i-a20-lamobo-r1.dtb I've also validate it with ${fdtfile} and it prints sun7i-a20-lamobo-r1.dtb I noticed that ${efi_fdtfile} prints nothing. Is that ok? dm tree prints the following: Class Index Probed Driver Name ----------------------------------------------------------- root 0 [ + ] root_driver root_driver simple_bus 0 [ + ] generic_simple_bus |-- soc@1c00000 phy 0 [ + ] sun4i_usb_phy | |-- phy@1c13400 usb 0 [ + ] ehci_generic
  5. Yes, of course. My I've modified the DT file that is located here: ../../../armbian/cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts Anyway to verify the u-boot does use this DT file ?
  6. I need to use an external LED device (not the LEDs that are on the board), and I need to be able control this device both from boot and linux (and in order to control this device I'm must enable the i2c3 bus). The weird thing is that at the boot stage I do have access to i2c0 bus (which is used to control the AXP209), although I can't see it the device tree with "dm tree" (however i2c0 and i2c3 are defined in "sun7i-a20-lamobo-r1.dts"). Any ideas how to enable the i2c3 bus ? (I though about trying to do the same as implemented with i2c0 for the AXP209, but I still didn't
  7. Yes I did, but the compilation still fail. I guess I'm using the wrong configuration. However, when I add CONFIG_SPL_DM=y, the compilation seems to work but later fails on: u-boot-spl section `.data' will not fit in region `.sram' region `.sram' overflowed by 820 bytes Maybe I should try a different approach. I've noticed that if I run "dm tree", I don't see the I2C in the device tree, but if I call "i2c bus", I get: Bus 0: twsi0 and if I call "i2c dev 0", I get: Setting bus to 0 Valid chip addresses: 34 However, when I call "i2c dev 1
  8. Hi, I'm trying to enable the I2C at the U-BOOT stage, but so for with no success. I'm using Lamobo-R1 (Allwinner A20), but I guess that general tips from similar boards (Banana PI etc.) are still very welcome. I read these posts, and tried what has been suggested here, but with no success I2C control in u-boot: Orange Pi Zero enable i2c at u-boot for NanoPi Neo2 u-boot with I2C This is what I've done so far: I've modified the u-boot device tree to enable the I2C bus (I did the same with the kernel device-tree, and here it does wo
  9. Hi, I need to use the i2c in the u-boot stage. I've added a patch that enables this i2c bus in the device-tree, and when I run this command (just for example): sudo i2cset -y 2 0x1b 0x1 0xf AFTER the boot stage it seem to work. However when I try this command IN THE boot stage, I get: Unknown command 'i2cset' - try 'help'. 1. I guess I'm trying to use 'i2cset' in a too early stage - any idea how to control the i2c in the u-boot stage or how to make 'i2cset' available at the u-boot stage ? 2. Since 'i2cset' doesn't work in the u-boot stage, I don't kno