martinayotte

  • Content Count

    3873
  • Joined

  • Last visited

Reputation Activity

  1. Like
    martinayotte got a reaction from Fionn in GPIO not working for non root   
    Ok ! I've found the recipe :
    chmod 4775 /usr/bin/python If you wish to restrict the security, you should probably copy /usr/bin/python into /usr/bin/python-as-root and doing "chmod 4775 /usr/bin/python-as-root" and running your GPIO python code with this one.
  2. Like
    martinayotte got a reaction from gounthar in Orange Pi Zero: internal RTC   
    The PCF8523 chip is a good one since it can trigger an alarm interrupt ...
  3. Like
    martinayotte reacted to JMCC in RK3399 Legacy Multimedia Framework   
    IT'S FINALLY HERE...

    THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION
     
    After two years of using a separate script to enable the multimedia features in RK3399 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).
     
    I. Installation
    Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".
     
    II. Features
    Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K).
            - See instructions below, in the next post, for playing YouTube videos up to 4K with this MPV.
    ISP Camera with real-time h.264/1080p HW encoding: Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM menu as your user account: 


    Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed.  
    III. Sources
    This is the list of the sources used for the packages:
     
    IV. FAQ
    ¿Why did you use Debian Buster as a base for this implementation?
    It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal.
      ¿Why Legacy instead of Mainline?
    This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels.
      ¿Will you add new features to this implementation?
    No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
  4. Like
    martinayotte got a reaction from TRS-80 in Which kernel is the armbian supported one for OPI Zero H2?   
    It is here : https://www.armbian.com/orange-pi-zero/
  5. Like
    martinayotte got a reaction from TRS-80 in OrangePi One Plus (H6) - SPI Enabled but not communicating.   
    After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
     
    https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
     
  6. Like
    martinayotte got a reaction from Werner in Test new xradio firmware   
    I've checked on my second OPi0 where I didn't upgrade firmware, so still previous version, and the issue is also present :
    [ 14.824376] xradio: XR819 device discovered [ 15.056442] xradio: hardware vers. 7.9 [ 15.056457] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003 [ 15.056460] xradio: Config USE_EXTENSIONS [ 40.809788] xradio TXRX-WRN: received frame has no key status [ 40.809802] xradio TXRX-WRN: dropped received frame [ 3653.654011] xradio WRN: BH: missed 4 consecutive interrupts! [ 5423.670767] xradio WRN: BH: missed 5 consecutive interrupts! [ 7584.760350] xradio WRN: BH: missed 6 consecutive interrupts! [ 9724.478792] xradio WRN: BH: missed 7 consecutive interrupts! [10080.291066] xradio WRN: BH: missed 8 consecutive interrupts! [10777.751448] xradio WRN: BH: missed 9 consecutive interrupts! [13480.647858] xradio WRN: BH: missed 10 consecutive interrupts! [18367.827745] xradio WRN: BH: missed 11 consecutive interrupts! [19237.530227] xradio WRN: BH: missed 12 consecutive interrupts! [20461.024844] xradio WRN: BH: missed 13 consecutive interrupts!  
  7. Like
    martinayotte got a reaction from Nyx_ in OrangePi One Plus (H6) - SPI Enabled but not communicating.   
    After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
     
    https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
     
  8. Like
    martinayotte got a reaction from Werner in OrangePi One Plus (H6) - SPI Enabled but not communicating.   
    After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
     
    https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
     
  9. Like
    martinayotte got a reaction from kprasadvnsi in OrangePi Zero2 - Allwinner H616   
    I will try my best, but "time is the missing ingredient" as usual ...
    (I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)
  10. Like
    martinayotte got a reaction from TRS-80 in OrangePi Zero2 - Allwinner H616   
    I will try my best, but "time is the missing ingredient" as usual ...
    (I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)
  11. Like
    martinayotte got a reaction from Werner in OrangePi Zero2 - Allwinner H616   
    I will try my best, but "time is the missing ingredient" as usual ...
    (I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)
  12. Like
    martinayotte got a reaction from Werner in Test new xradio firmware   
    Upgrade done ! No side effect seen until now ...
  13. Like
    martinayotte got a reaction from PaddleStroke in Reading A20 LRADC0 and LRADC1 values   
    You can try a workaround by doing "cp /usr/bin/python /usr/bin/python-sudo ; chmod a+s /usr/bin/python-sudo" so that execution will be done as root.
  14. Like
    martinayotte got a reaction from PaddleStroke in Reading A20 LRADC0 and LRADC1 values   
    Using /dev/mem, you can poke control register at 0x01C22800 to be in continuous mode, and then peek data register to read ADC values at 0x01C2280C or 0x01C2280D, depending if LRADC0 or LRADC1.
  15. Like
    martinayotte got a reaction from PaddleStroke in Reading A20 LRADC0 and LRADC1 values   
    Right, but don't forget to initialize Control Register first by setting Continuous Rate and Continuous Mode...
  16. Like
    martinayotte got a reaction from PaddleStroke in Reading A20 LRADC0 and LRADC1 values   
    Download this UserGuide : http://dl.linux-sunxi.org/A20/A20 User Manual 2013-03-22.pdf
    Read the LRADC chapter starting at page 192.
    You will see the description of the ControlRegister at page 193-194.
    You need your /dev/mem to be "O_RDWR", not "R+" to allow writing into ControlRegister.
  17. Like
    martinayotte got a reaction from jslav in disable /dev/video0 and /dev/ttyS* in kernel 5.8.y with device tree   
    For video, I don't know ... But for serial, Yes !
     
    Doing this command :
    grep "=8" /boot/config-*-sunxi will reveal :
    CONFIG_SERIAL_8250_NR_UARTS=8 CONFIG_SERIAL_8250_RUNTIME_UARTS=8  
  18. Like
    martinayotte got a reaction from Zamana in Orange Pi PC 1-Wire   
    While adding w1-gpio in /boot/armbianEnv.txt, you don't need to add it in /etc/modules-load.d/modules.conf ...
    But you need to add "param_w1_pin=PD10" in /boot/armbianEnv.txt as well, otherwise it is defaulted to PD14.
  19. Like
    martinayotte got a reaction from gounthar in Orange Pi PC 1-Wire   
    While adding w1-gpio in /boot/armbianEnv.txt, you don't need to add it in /etc/modules-load.d/modules.conf ...
    But you need to add "param_w1_pin=PD10" in /boot/armbianEnv.txt as well, otherwise it is defaulted to PD14.
  20. Like
    martinayotte got a reaction from Werner in Orange pi 3 - change i2c speed   
    I2C standard clock are usually 100KHz or 400KHz, but you can try other values.
    Here is the doc, the parameter is "clock-frequency" :
    https://www.kernel.org/doc/Documentation/devicetree/bindings/i2c/i2c-designware.txt
  21. Like
    martinayotte got a reaction from jsorocil in Rock PI 4 A not starting   
    No ! Not true ! Trust me, or as Igor said, read the Rockchip datasheets !
    All RK3399, as well as any other Rockchip SoC, are loading U-Boot from eMMC first.
    The fact that some boards is looking at SDCard is simply that this U-Boot loaded from eMMC is checking for SDCard with specific format, partitions, or uEnv.ini, and then continue boot process from SDCard.
  22. Like
    martinayotte got a reaction from TonyMac32 in Le Potato max power draw on GPIO pins?   
    A simple MOSFET, such AO3402, should do the job ...
  23. Like
    martinayotte got a reaction from Werner in Amlogic forum adjustments   
    I don't have any objections to merge those subforums ...
  24. Like
    martinayotte got a reaction from 5kft in Switching SUNXI-DEV to 5.9.y (h3-h5-h6/megous)   
    My Allwinner garden tour using 5.9.y is almost finished ! Only 2 board models left ...
  25. Like
    martinayotte got a reaction from guidol in Switching SUNXI-DEV to 5.9.y (h3-h5-h6/megous)   
    I think it should be good to switch to u-boot v2020.07, at least for DEV, I've done that since few weeks locally and didn't got any issues ...