• Content Count

  • Joined

  • Last visited


About @lex

  • Rank
    Embedded member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2059 profile views
  1. I have been told LE 9.8.8 has panfrost working smooth , i think it's a @jernej's work. (not sure) I have no idea how to fetch this version and have a look at panfrost diff. Maybe you can. In my experience i have applied all available patches and still not stable enough.
  2. It has been a while since i last touched the 4.19 , but i think you should enable: CONFIG_DVB_USB_RTL28XXU Look for the module *rtl28xxu* (build as a module).
  3. Try traceroute (computer to orangepi) first time right after you boot orangepi and again after you ping from orangepi (serial console) to your computer. Compare the results, it can give you a clue. * and vice-versa
  4. If i recall correctly you need to set (enable) a pin on u-boot load time and specific to your PC Plus and OV5640. Have you tried to set the pin on u-boot boot.cmd? Something like: # OPI-PC camera (set PG11 for gc2035) gpio set PL10 gpio set PA17 #gpio set PG11 This error message typically tells you the board cannot find the attached sensor. Possible causes are: * Sensor Not powered correctly (see which pin or píns should be set at boot) Make sure theses lines are for the OV5640 and PC Plus. vip_dev0_power_en = port:PA17<1><default><default><1> vip_dev0_reset = port:PE14<1><default><default><1> vip_dev0_pwdn = port:PE15<1><default><default><0> * i2c is already in use, double check your Fex file and disable the correct twi, this seems to be OK in your FEX but try: [twi1] twi_used = 0 twi_scl = port:PA18<3><default><default><default> twi_sda = port:PA19<3><default><default><default> [twi2] twi_used = 0 twi_scl = port:PE12<3><default><default><default> twi_sda = port:PE13<3><default><default><default>
  5. @guidol Thanks for the tip. In fact i have sun50ia64audio available but no sound output on jack. Hdmi-sound always worked. My kernel is now based on mainline kernel with ir and cedrus patch, i tried to catch up with @jernej's and @kwiboo's patches and learn a few things but these guys are too fast... and it is time to slowdown... Great to see how your work and Armbian progresses, i think you will soon tag it as supported. This is/was a great board. I am just waiting for that board with the promising Grub open source (like).
  6. Try this: hit F2, select each label on the Right column and delete all CpuFreq (meter). Then add the available meters again. Exit htop and check again. There is a meter called CpuFreq and CpuFreq1,CpuFreq2,... (cpu count). I think the correct meters should be CpuFreq1,2,3...8 and not CpuFreq.
  7. You can refer to this patch: https://lkml.org/lkml/2018/11/27/1041 https://patchwork.kernel.org/patch/10783429/ If this works for banana pi it will work for orange pi. DO NOT MERGE is there for a reason. ov5640_read_reg: error: reg=300a. It usually means it cannot communicate with the sensor. Use this: PE12/CSI_SCK/TWI2_SCK ==> CSI-SCK PE13/CSI_SDA/TWI2_SDA ==> CSI-SDA PE14 ==> CSI-RESET# PE15 ==> CSI-STBY-EN
  8. @lex

    Updated htop

    According to this: https://github.com/armbian/build/blob/master/packages/bsp/helios4/90-helios4-hwmon.rules , it is not related to CPU temp. My guess is just a missing kernel config.
  9. @lex

    Updated htop

    Please check if you have: cat /sys/class/hwmon/hwmon0/name
  10. @lex

    Updated htop

    The path is hard coded in the HTOP for the cpu temp. I think the problem is that some boards (kernel) use the hwmon driver and sometimes different kernel config. I think the best approach would be to traverse /sys and try to find the label for the cputemp / gputemp / regulators, etc.. But what exactly look for to be Universal? In my x64 for example, same Intel, different kernel configs (server vs desktop) points to different locations: cat /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp2_label Core 0 cat /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp3_label Core 1 cat /sys/devices/platform/coretemp.0/hwmon/hwmon2/temp2_label Core 0
  11. I had the impression it was the other way around. Have you had success with lima? or anyone? Anyway, Looking forward to seeing the @NicoD's video about tee panfrost experience.
  12. i have had success with OV5640 on FE HW (H3,H5,A64, possibly H2+) You should check camera schematic of your board if it matches the same way FE handle the camera. I think I2C must be tied to CSI or you cannot communicate with the sensor. vfe_v4l2 driver seems to be from Android and has additional Image Processing in it. (ISP) (Kernel 3.x and 4.4.y, perhaps 4.9.y). I think there is still no support for OPIs, BPIs and some others for the mainline OV5640 / OV5647 and you have to use the Android kernel way or until someone writes the code.
  13. I have some experiments with legacy kernel 4.4 before the BPI updated the kernel source (changes on eMMC and possibly Wifi, my board is too old to check the new features), I don't know if it has been improved or not. Recently, the mainline stable kernel 4.20 has reached a very stable condition and you can even run KODI on A64, thanks to jernejsk's work. I think the problem is on the new eMMC version. I can't help on this since i don't have this hw revision. Tip: try to build Armbian without enabling eMMC and/or Wifi and see what happens. Grab the complete boot log, i think there are others here with the new hw revision that can help.
  14. This weekend I was revising and testing the OV5640 for some A64 boards. To enable the Camera (OV5640) on NanoPi A64 for the mainline kernel you have to update the following: * DT * GPIO-I2C Here is the excerpt : Kernel config: CONFIG_I2C_GPIO=m CONFIG_VIDEO_OV5640=m CONFIG_VIDEO_SUN6I_CSI=m
  15. Hmm. maybe you mean CPU version. A64 is the old one and R18 is the new one, they are essentially the same. Maybe you mean eMMC version , the new one has a newer eMMC version and you should run with a newer Kernel version that handles this new eMMC.