Jump to content

MikePooh

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by MikePooh

  1. If I understand correctly PA11 and PA12 are connected to +3.3V through 2.2k resistor on Orange Pi PC Plus. That means that it is impossible to use internal pull-up.
  2. I switched mentioned pins to IN mode. And it is seems they are pulled up by default. +-----+-----+----------+------+---+-Orange Pi+---+---+------+---------+-----+--+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+----------+------+---+----++----+---+------+----------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 12 | 8 | SDA.0 | IN | 1 | 3 || 4 | | | 5V | | | | 11 | 9 | SCL.0 | IN | 1 | 5 || 6 | | | 0v | | | If physically connect that pins to the ground it shows 0 level. But I need it 0 by default. All other pins which are not related to I2C/TWI I can easilly pullup/pulldown, but these not. i2c0 is disabled in armbiaEnv.txt Thank you.
  3. Does someone solved the problem with wrong resolution on boot? I have Waveshare touchscreen LCD(B) with resolution 800x480. Sometimes it detects as expected and after boot my GUI application run well with correct touchscreen coordintaes. If I run DISPLAY=:0 xrandr -q I got output Screen 0: minimum 320 x 200, current 800 x 480, maximum 8192 x 8192 HDMI-1 connected primary 800x480+0+0 (normal left inverted right x axis y axis) 150mm x 100mm 800x480 65.68*+ The screen detects default resolution and even screen physical size. However sometimes it detects wrong and touchscreen coordinates doesn't match to physical position. If run DISPLAY=:0 xrandr -q I got output Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 HDMI-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.32 56.25 848x480 60.00 640x480 59.94 The resolution is wrongs as well as the physical coordinates isn't detected. I've tried to put this row to armbianEnv.txt extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/800x480.bin video=HDMI-A-1:800x480-24@60 This solved correct position of bootlogo during boot, but does't solve wrong touchscreen coordinates after boot. Moreover it causes very long boot time (more than 1 minute) I've tried to put U-boot env and save it setenv video-mode sunxi:800x480-24@60,monitor=hdmi,hpd=0,edid=0 saveenv It doesn't work at all. I've tried to set U-Boot variable CONFIG_INITIAL_USB_SCAN_DELAY=2000 I was thinking the wrong detection of screen dimension may lay in surface of screen initialization time. However it doesn't help too. The screen initialized before that delay. I've tried to put conf file to xorg conf according to this topic. It give correct resolution and touchscreen coordinates after boot, but form time to time wrong position of bootlogo. Does someone find the best solution?
  4. Answering my own question. I was needed to change U-Boot configuration during Armbian build. According to this manual, and answers given above I've run following command: ./compile.sh docker RELEASE=focal BOARD=orangepipcplus BRANCH=current KERNEL_ONLY=yes KERNEL_CONFIGURE=no CREATE_PATCHES=yes REPOSITORY_INSTALL="kernel,armbian-config,armbian-firmware" Just before U-Boot build step patch looking dialog appears. Than I've put needed settings to my boards U-Boot defconfig file /armbian/cache/sources/u-boot/v2021.10/configs/orangepi_pc_plus_defconfig CONFIG_ENV_IS_IN_EXT4=y CONFIG_ENV_EXT4_DEVICE_AND_PART="1:1" CONFIG_ENV_EXT4_FILE="/boot/uboot.env" CONFIG_ENV_EXT4_INTERFACE="mmc" Than pressed Enter in build terminal. Patch has been applied and I've got U-Boot with desired params.
  5. So only the way to change U-Boot config is to use: ./compile.sh CREATE_PATCHES=yes Am I right?
  6. MikePooh

    MikePooh

  7. I am trying to build U-Boot from source with docker using this guide. The Armbian commit hash is 3c4b890ead32720fbfc77356c9600c4ff08a91a3 ./compile.sh docker-shell RELEASE=focal BOARD=orangepipcplus BRANCH=current Than ./compile.sh 'prepare_host && compile_sunxi_tools && install_rkbin_tools' And dot error: /root/armbian/lib/main.sh: line 576: compile_sunxi_tools: command not found Could someone help with the issue? Thanks in advance.
  8. Answering your second question, yes, it is. Try this: aptitude search arm-linux-gnueabihf
  9. Hi! I have Orange Pi Pc Plus and Armbian based on Linux 5.8.11-trunk which successfully loads with any U-Boot taken from official Armbian distro. However I need to do minor changes in U-Boot KConfig (Allow store env vars in ext4). For that purposes I cloned U-Boot from its GitHub repo and build it. make CROSS_COMPILE=arm-linux-gnueabihf- orangepi_pc_plus_defconfig make CROSS_COMPILE=arm-linux-gnueabihf- This make me a u-boot-sunxi-with-spl.bin file which I transferred to my SD card. The U-BOOT loading step passes well, and I've seen "Starting kernel ..." However kernel doesn't start. I've set VERBOSITY=7 in armbianEnv.txt and seen that kernel loading just suspends on different steps time by time. I've tried to build and use different versions of U-Boot, form 2022-01-rc3 (latest) to 2020-10 which is used in default Armbian distro and got the same effect. Maybe I am missing some KConfig params? Please advice. Thanks in advance.
  10. It is so nice that you post the code as image. Please let me paste it as code. if test -e ${devtype} ${devnum} ${prefix}boot.bmp; then splashpos=m,m splashimage=66000000 load ${devtype} ${devnum} ${splashimage} ${prefix}boot.bmp bmp d ${splashimage} fi P.S. Code works.
  11. Could you please share the full step-by-step how-to enable the OV5640 camera on mainline kernel on H3 devices. Including CSI, drivers etc. Thanks in advance.
  12. Target board is Orange Pi PC+ based on H3 the <ump/ump.h> file is needed which must contains in linux-headers-XXX-sunxi with version match to 20.02.0-rc1 however aptitude search linux-h | grep sunxi outputs linux-headers-current-sunxi 19.11.3 <none> Linux kernel headers for 5.3.9-sunxi on armhf linux-headers-legacy-sunxi 19.11.3 <none> Linux kernel headers for 4.19.84-sunxi on armhf linux-headers-next-sunxi 5.92 <none> Linux kernel headers for 4.19.62-sunxi on armhf And there is no version for 5.4.14 (20.02.0)
  13. Same issue I got today when upgrade to Armbian 5.60 As recommend I've loaded from SD card (same content as eMMC) copied /boot folder from SD to eMMC, changed rootdev UUID in armbianEnv.txt. It doesn't help. Do I need to recompile boot.scr or something like this?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines