Jump to content

rlu

Members
  • Posts

    6
  • Joined

  • Last visited

  1. The I2C is for enabling a Bakebit Oled for Boot, so that I later can select which OS I want to use from my dual boot
  2. I compiled u-boot myself and added the CONFIG_I2C0_ENABLE=y to the defconfig. After that I wasn't able to see the i2c0 in u-boot. then I added the code above and now I see the i2c bus. But I can't access it, because it is shown as Bus -1. At the moment it is only an exercise to get common with u-boot. Later I want to get dual boot via u-boot
  3. I’ve done this and in Linux I can access the i2c0, but I want to access it in u-boot. And i'm stuck there. I added the following code into the sun50i-h5-nanopi-neo2.dts, but now I see the i2c bus, but it is shown as Bus -1 and I can't access it &i2c0 { pinctrl-names = "default"; pinctrl-0 = <&i2c0_pins>; status = "okay"; };
  4. Hi, I tried to enable the i2c in u-boot by using the config flags shown in the Readme. But I had no success. What do I miss?
  5. I solved my problem. I made two mistakes. First: I compiled u-boot without the bl31.bin Second: for the third dd command I have to use the u-boot.itb not the u-boot.bin
  6. Hi, I compiled the newest version of u-boot. Then I updated it at my sd card via: dd if=/dev/zero of=/dev/mmcblk0 bs=1k count=1023 seek=1 dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8 dd if=u-boot.bin of=/dev/mmcblk0 bs=1024 seek=40 Now u-boot starts and I'll get to the message "Starting kernel ..." and nothing happens. Do I have to recompile the Kernel or did I something wrong? Edit: I did it on my NanoPi Neo2
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines