• Content Count

  • Joined

  • Last visited


About @lex

  • Rank
    Embedded member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2645 profile views
  1. @lex

    Odroid C4

    Can you show the output of the file log.txt from the command below after the board freeze? * fire htop * type in the shell: watch -n 10 "dmesg|tail>>log.txt&&echo ----->>log.txt&&sync"
  2. @lex

    Odroid C4

    I would like to know how htop can crash your system or make crashes. Please provide all information, screenshot when it crashes if you can't access the board. If you are using Desktop, connect also via ssh to grab all armbian info. *edited* I don't have the board, maybe you create a new thread related to the problem, i can follow that and share some thoughts. I can test the this Armbian version on another board.
  3. Attached is the working Pine64+ + LCD7 + touch dtb. pine64.dtb_5.5.0-rc5-next-20200109.tar.gz
  4. I was able to test the LCD7 with Pine64+ some time ago. I lost some work done with a 'rm *' in the wrong dir but i still have the sd card with the dtb if someone would like to 'decompile' it and compare. What i can recall from the tests are: * u-boot had hdmi and dsi disabled, so no initial display, only when kernel is up * the kernel tested had dsi support, linux-next (jan 9) [next-20200109], no patches were needed only the patch from @Clément Peron to fix that backlight dim issue. If you can fetch that specific linux-next version, only dts with dsi enabled is required.
  5. I don't want to hijack this one but what i mean is use the v4l2 commands to check for the camera, or use the command: dmesg|tail after you attach the USB camera. Moderator can delete this. no problem.
  6. Rollback to your 5.8 and try this tip with pulse-audio (learned myself the hard way) 1. Open a session (or cmd line) 1. Open a second session (or cmd line) 2. Run your MP3 to output to jack on the first session (or cmd line) 3. While the file is playing (silently as you say) on the first session, fire alsamixer (select audio-codec) on the second session and start unmuting the controls, upping the volume, etc. At some point, eventually you get the sound output to jack. Watch the kernel for some messages.
  7. I think you should read this thread to the end, you might need v4l2 and media to grab some image if you have a new kernel. This might be true to USB camera. (i have not tried using USB camera, just a guess.)
  8. Did you try to boot Android just to make sure LCD is not defective or if wired correctly? I don't know what are the changes from the Pine A64 LTS V1.2 to Pine64+. Pine64+ + LCD 7 + Touch works with mainline but it is tricky to setup. In this case i think u-boot should not have hdmi and dsi enabled and only when kernel is up and in control you will see the login prompt on the LCD.
  9. I have updated fswebcam for the mainline kernel. You get the FPS printed on the picture, all seems to be fine. Tested with A64, H3 and H2 with your: - {0x4407, 0x04, 0, 0}, {0x460b, 0x35, 0, 0}, {0x460c, 0x22, 0, 0}, + {0x4407, 0x04, 0, 0}, {0x460b, 0x35, 0, 0}, {0x460c, 0x20, 0, 0}, Samples: H3 https://github.com/avafinger/fswebcam/tree/mainline-kernel/nanopi-air H2 https://github.com/avafinger/fswebcam/tree/mainline-kernel/bpi-m2z A64 https://github.com/avafinger/fswebcam/tree/mainline-kernel/nanopi-a64 You should focus on the AF
  10. I will test with and without asap and give some feedback. Perhaps you should open a new thread, something like "Improving ov5640 (mainline)" and push your code/patch there (up to you). How do you test your FPS? Maybe you could get inspired by the BSP code: https://github.com/avafinger/ov5640/blob/A64/ov5640.c#L4577
  11. Untoched kernel driver works for A64 and H2/H3 on the following win size: * 320x240 (30 FPS) * 640x480 (30 FPS) * 1280x720 ( < 30 FPS) * 1920x1080 ( < 30 FPS) Quality is acceptable (outdoor). Does not work: 60 FPS, 2592x1944 I think you are right about 2592x1944 , i will test your changes and report back.
  12. Legacy = Kernel 3.x Mainline (?) >= 4.x I have not tested the @ubobrov solution, i think you should go with this one: https://github.com/uboborov/sunxi-cedar-mainline
  13. Encoding using cedrus264 was for legacy kernel. I think Uboborov has done some work with mainline kernel for encoding with cedrus. Search the forum for "encoding" or uboborov
  14. i think so. I tested your pattern sample on A64 and both pattern looked fine (exactly the same) ffmpeg -input_format yuyv422 -s 1920x1080 -i /dev/video0 /tmp/output_yuyv422.mjpg ffmpeg -input_format yuv420p -s 1920x1080 -i /dev/video0 /tmp/output_yuyv420.mjpg which i think should fail for the yuyv422 on fmt:YUYV8_2X8/1920x1080 Image quality is similar to what you got with your test_0. I would advise to move on to latest ov5640 driver or if you find the ov5640 driver (PinePhone) with additional fix , let us know the diff. Maybe @rreignier can have diffe
  15. Usually V4l2 applications map 4 buffers (you can map 8 buffers if you have enough memory to get some optimization). For the size of 1920x1080 and YUV420 format you get a buffer size of 1920*1080*2 = 4147200 mapped in memory and the sensor delivers an image of size 1920*1080*3/2 = 3110400. Looks like your VLC is addding some extra bytes for any reason. 32 buffers is around 128 MB, try to increase CMA, or change and recompile it for 8 buffers. Regarding the green tinge and pinkish or grainy image i think is related to light condition, if you take shoots at day light (outsid