jock

Members
  • Content count

    87
  • Joined

  • Last visited


Reputation Activity

  1. Like
    jock reacted to TonyMac32 in U-boot v2018.05 and RK3288 not working?   
    U-Boot 2018.05-armbian (Jul 02 2018 - 00:54:54 -0400) Model: Tinker-RK3288 DRAM: 2 GiB PC event = 0x20 usb connected to SDP, force enter ums mode rk3288_maskrom_ctrl: enable_emmc = 1 usb_current_limit_ctrl: unlock_current = 1 MMC: dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 Loading Environment from EXT4... ** Unable to use mmc 0:auto for loading the env ** Failed (-5) In: serial Out: serial Err: serial Model: Tinker-RK3288 Net: failed to enable clock 0 No ethernet found. UMS: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x1d5a000 \wait for usb get descriptor cmd timeout rk3288_maskrom_ctrl: enable_emmc = 0 usb_current_limit_ctrl: unlock_current = 0 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 1498 bytes read in 17 ms (85.9 KiB/s) ## Executing script at 00000000 U-boot loaded from eMMC 178 bytes read in 14 ms (11.7 KiB/s) 41042 bytes read in 35 ms (1.1 MiB/s) 4908082 bytes read in 238 ms (19.7 MiB/s) 9272512 bytes read in 433 ms (20.4 MiB/s) ## Loading init Ramdisk from Legacy Image at 21000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4908018 Bytes = 4.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 0fb51000, end 0ffff3f2 ... OK Loading Device Tree to 0fb43000, end 0fb50051 ... OK gets right to starting kernel.  The delay is the dev kernel I was building.
  2. Like
    jock reacted to TonyMac32 in U-boot v2018.05 and RK3288 not working?   
    I tried it last night without any UART connection, it took it about 5 minutes to boot.  So I'm not certain what's going on, I have some other stuff to work on first in any case.
  3. Like
    jock got a reaction from TonyMac32 in RK3288 Media Testing Script   
    Yes exactly, just applied the patch and the kernel driver is back in the game
  4. Like
    jock reacted to Myy in RK3288 Media Testing Script   
    Ah, EOVERFLOW... You might need that kind of patch applied to the Mali drivers : https://github.com/Miouyouyou/RockMyy/blob/master/patches/Midgard/r19p0-01rel0/0009-GPU-ARM-Midgard-Adapt-to-the-new-mmap-call-checks.patch
     
    They might have imported Linus Torvalds patch to mmap into the 4.14 series.
  5. Like
    jock reacted to Myy in Questions about CMA on mainline kernel for Midgard   
    I don't think this is "required" per se.
     
    To reserve memory for the CMA allocator, you need to pass the cma=Size parameter to the kernel, at boot time.
    Edit your boot file accordingly and add something like cma=32M .
    Now this will reserve 32M of RAM for the CMA allocator. Meaning that, if it's not used, you'll just lose 32M of RAM for nothing.
  6. Like
    jock got a reaction from pro777 in Armbian for RK3288 XT-Q8L-V10 (Q8) boards   
    This is an unofficial Armbian variant for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc...
     

     
    All source code is available on github as an armbian fork: https://github.com/paolosabatino/build
    To compile armbian images, just follow the official instructions and select "xt-q8l-v10" board.
     
    Prebuilt images:
    Armbian Ubuntu Xenial 5.41 Desktop - Kernel 4.4.126 (legacy)
    Armbian Ubuntu Xenial 5.41 Desktop - Kernel 4.14.39 (mainline)
    Armian Debian Stretch 5.41 Server - Kernel 4.4.126 (legacy)
    Armian Debian Stretch 5.41 Server - Kernel 4.14.39 (next)
    Armbian Ubuntu Xenial 5.46 Desktop - Kernel 4.4.132 (legacy)
    Armbian Ubuntu Xenial 5.46 Desktop - Kernel 4.14.50 (mainline) (eMMC friendly)
     
     
    Instructions:
    First of all, tv boxes comes with an obsolete u-boot. To be able to fully boot from sdcard, the fastest way is to zero-fill the internal eMMC: you won't brick your box, instead it will be forced to boot in Maskrom Mode which, by default, boots from the external sdcard. rkdeveloptool may come really handy for such job. Follow the guide just below or learn some more reference: https://github.com/nolange/rk3288-guide/blob/master/bootloader.md Flash the image on the sdcard, plug it in and push the power button for 1 second (or until it turns blue) Wait some seconds, the led should start blinking soon (HDMI output during boot is not available yet, so just wait for the login prompt, it should be there in less than 30 seconds) As usual, armbian default credentials are user: root password: 1234 If you want to install an image into the embedded eMMC, just prefer an image with the "eMMC friendly" tag above  
    Boot priority:
    Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices.
    Priority is fixed and boot devices are probed in this order:
     
    External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports; USB OTG port still does not work for booting) Internal eMMC  
    This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices.
    Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command:
    dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync  
    Current status:
    Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode, no quirks apparently. Transfer rate is very good (topped at 38 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: seems to work fast and reliably HDMI: works but may have some quirks, expecially if you attach and detach the devices. Generally works, but resolution is not configurable (see the note at the bottom) Serial: works Audio: HDMI audio works, but SPDIF is still a work in progress IR remote: works on legacy kernel, mainline kernel still lacks the proper driver Reboot/Suspend process: still some mysteries lays around here: rebooting the device via command line actually shuts it down. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide may help you to gain an hardware accelerated X11 and Chromium  
  7. Like
    jock got a reaction from Tido in Armbian for RK3288 XT-Q8L-V10 (Q8) boards   
    @Exellent Finally I had the time to do some tests with the eMMC and it looks like everything works pretty fine.
    I changed the boot order of U-boot, so the priority is always the external sd card, then the USB stick and finally the eMMC, so even if the image is installed in embedded memory, it should be always possible to run newer images using an external sdcard. Still there is no rockusb nor fastboot, so it is wise to experiment only if you have access to the serial console.
    I added a new image to the first post with "eMMC friendly" tag, if you want to give it a try. Just burn the image on a sdcard and then use armbian-config to install the system into the eMMC
  8. Like
    jock got a reaction from Rfreire in Enable HDMI in u-boot for RK3288   
    Is it possible to patch the device tree someway to enable HDMI output and having the console on the framebuffer for debugging in current non-development armbian version?
     
    Thanks
  9. Like
    jock reacted to JMCC in RK3288 Media Testing Script   
    The UN-official, UN-supported, UN-necessary, UN-popular, UN-precedented...
    RK3288 MEDIA TESTING SCRIPT
     
    So here is the final release of the RK3288 media testing script. Basically, the script provides the following functionality:
    Installing all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL, full VPU video play acceleration up to 4k@30 HEVC (the maximum supported by the SoC), and GLES 3.1 / OpenCL 1.2 support. Three video players supporting full VPU acceleration (RKMPP) and KMS display (GBM or a X11 DRM "hack", as described by the authors), namely: MPV, Gstreamer and Kodi 18.0 alpha preview. Two example programs using the OpenCL functionality: Examples form the Arm Compute Library, and a GPU crypto miner (an old version, but small and simple). Two additional small packages, that have no big interest from the developer prospective, but I find them interesting to play with: Support libraries for commercial web video streaming (tested with Netflix), and a simple Pulseaudio GTK equalizer using LADSPA.  
    Here is a more thorough documentation:
     
    >>> DOWNLOAD LINK <<<
     
    Instructions:
    Download the file above Untar it: tar xvf media-rk3288_1.0.tar.xz cd media-script ./media-rk3288.sh  
    Notes:
    This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC. Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance. That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script.  
    Enjoy!
     
     
     
  10. Like
    jock got a reaction from pro777 in Armbian for RK3288 XT-Q8L-V10 (Q8) boards   
    This is an unofficial Armbian variant for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc...
     

     
    All source code is available on github as an armbian fork: https://github.com/paolosabatino/build
    To compile armbian images, just follow the official instructions and select "xt-q8l-v10" board.
     
    Prebuilt images:
    Armbian Ubuntu Xenial 5.41 Desktop - Kernel 4.4.126 (legacy)
    Armbian Ubuntu Xenial 5.41 Desktop - Kernel 4.14.39 (mainline)
    Armian Debian Stretch 5.41 Server - Kernel 4.4.126 (legacy)
    Armian Debian Stretch 5.41 Server - Kernel 4.14.39 (next)
    Armbian Ubuntu Xenial 5.46 Desktop - Kernel 4.4.132 (legacy)
    Armbian Ubuntu Xenial 5.46 Desktop - Kernel 4.14.50 (mainline) (eMMC friendly)
     
     
    Instructions:
    First of all, tv boxes comes with an obsolete u-boot. To be able to fully boot from sdcard, the fastest way is to zero-fill the internal eMMC: you won't brick your box, instead it will be forced to boot in Maskrom Mode which, by default, boots from the external sdcard. rkdeveloptool may come really handy for such job. Follow the guide just below or learn some more reference: https://github.com/nolange/rk3288-guide/blob/master/bootloader.md Flash the image on the sdcard, plug it in and push the power button for 1 second (or until it turns blue) Wait some seconds, the led should start blinking soon (HDMI output during boot is not available yet, so just wait for the login prompt, it should be there in less than 30 seconds) As usual, armbian default credentials are user: root password: 1234 If you want to install an image into the embedded eMMC, just prefer an image with the "eMMC friendly" tag above  
    Boot priority:
    Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices.
    Priority is fixed and boot devices are probed in this order:
     
    External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports; USB OTG port still does not work for booting) Internal eMMC  
    This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices.
    Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command:
    dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync  
    Current status:
    Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode, no quirks apparently. Transfer rate is very good (topped at 38 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: seems to work fast and reliably HDMI: works but may have some quirks, expecially if you attach and detach the devices. Generally works, but resolution is not configurable (see the note at the bottom) Serial: works Audio: HDMI audio works, but SPDIF is still a work in progress IR remote: works on legacy kernel, mainline kernel still lacks the proper driver Reboot/Suspend process: still some mysteries lays around here: rebooting the device via command line actually shuts it down. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide may help you to gain an hardware accelerated X11 and Chromium  
  11. Like
    jock reacted to JMCC in Tutorial: 3D, video acceleration and OpenCL in RK3288 boards with new 4.4 (default) kernel   
    I'm working on a script to install all the stuff at once, but I'm not sure when it will be finished. In the meantime,in case anyone wants to try MPV with GBM (dsiplay) and RKMPP (decoding) acceleration, here are the instructions:
    After installing the base libs, configs and MPV according to the first post, download this package and install it. From then, you can launch mpv like this, in order to have full acceleration: LD_LIBRARY_PATH=/opt/libmali-gbm:$LD_LIBRARY_PATH mpv --hwdec=rkmpp --vo=gpu --gpu-api=opengl --gpu-context=drm <file> The deb package above will install the GBM version of libmali. I packaged it to install under /opt, so it did not interfere with system libs and we can still have X11 acceleration with the libmali-X11 version.
     
    MPV can still be run normally, through X11-EGL, with the known performance limitations (see first post). But if you launch it with the command above, it will completely ignore the X server, and use directly GBM/KMS. That means it will only run in fullscreen, with no mouse support. You can control it with the keyboard and (I suppose) with a remote control or HDMI CEC. MPV on-screen display works normally,  so when you press the appropriate keys info is displayed on the screen (see MPV manpage for a list of keyboard controls). When you press "q" or "Q", it will exit and you will have your X11 session back as you left it.
     
    In MPV's implementation of RKMPP, it is bound to GBM display, so the only way to use hardware video decoding is with this launcher. Performance is outstanding: Silk-smooth 4K playback, with minimal CPU usage.
  12. Like
    jock got a reaction from Slackstick in Mali support announced for mainline (Allwinner SOC's)   
    Hi hoskit, yes I was able to get the job done. I suggest you to take the very latest development armbian nightly which already has the HDMI bits in the device tree, just not to tinker about the kernel compilation and other messy things.
    The guy (mripard) on github fixed some regression he introduced that broke the mali kernel driver compilation on slightly older kernel, so now compilation and installation should be pretty accessible.
    I tried only the framebuffer version, and yes, it was working pretty well: I tried different OpenGLES2 demos from the official Mali SDK and they all worked without issues
  13. Like
    jock got a reaction from Slackstick in Mali support announced for mainline (Allwinner SOC's)   
    Hi hoskit, yes I was able to get the job done. I suggest you to take the very latest development armbian nightly which already has the HDMI bits in the device tree, just not to tinker about the kernel compilation and other messy things.
    The guy (mripard) on github fixed some regression he introduced that broke the mali kernel driver compilation on slightly older kernel, so now compilation and installation should be pretty accessible.
    I tried only the framebuffer version, and yes, it was working pretty well: I tried different OpenGLES2 demos from the official Mali SDK and they all worked without issues
  14. Like
    jock reacted to balbes150 in ARMBIAN for Amlogic S905 and S905X   
    Image Yocto with kernel 4.12 (for S905X).  (v20170825)
    To download the image. Unzip. To record on the SD card. Rename the /boot partition file of the dtb to the "dtb.img". To download the script s905_autoscript. Add on the SD card in the /boot partition. On TV Boxing should be informed (with other images) is activated multiboot. Connect the SD card to TV box. To turn the power on. After running the screen is in hibernation (from your watch) for desktop display you have to press a key on the keyboard or moving the mouse.
     
    https://yadi.sk/d/f5HsAL913HYksf
     
     
    USB works in the kernel 4.12.9 (kernel source Neil Armstrong).
  15. Like
    jock got a reaction from wildcat_paris in orange pi from start   
    None of those voltages are fine with the boards. The board may run, but USB devices and HDMI devices won't work as long as they receive the proper voltage directly from the source.
    Also cheap power supplies with selectable output voltage usually have very little output amperage (200mA if you're lucky. These boards require 2000mA to work reliably with some USB devices attached)
  16. Like
    jock got a reaction from rodolfo in Performance/throttling problems with OPi One   
    You may take a look to this thread too:
     
    http://forum.armbian.com/index.php/topic/1010-orange-pi-one-1200-mhz-with-low-voltage/
     
    I tried to run the Opi One at 1.2 Ghz with 1.100 volts. In my experience, it works flawlessy and I tried all the stress tests suggested by tkaiser with success, plus I stressed it with cpuburn-a7 for some hours (with huge heatsink!!) without problems.