• Content Count

  • Joined

  • Last visited

About whoman

  • Rank

Recent Profile Visitors

845 profile views
  1. Hello Everyone! I cannot get Gstreamer to use video acceleration on my ROC-RK3328-CC (Libre Renegade) rockchip-gstreamer from Rockchip's github page just wont let me compile the vpudec plugin I have tried both stretch and buster with 4.4 legacy kernel (currently on buster), but I seem to be missing one peice. Here's what I do: -Install a current Armbian Renegade Legacy image, and install all the tools necessary to compile everything. -Git Clone and compile: Gstreamer, plugins-base, plugins-good, plugins-bad, plugins-ugly, plugins-libav -Git Clone and compile: libmal
  2. It turns out that it's been renamed to 'hantro-vpu' starting with 5.3. I got the kernel module compiled but now I realize there's a bunch of patches that update everything for this name changed that were not applied while using the armbian build tool. I'll open up a new thread regarding that since it's a different issue.
  3. So after looking through the device tree, I see that it's called 'video-codec' however modprobe cant find the module... I only see it in these locations: /sys/devices/platform/ff350000.video-codec /sys/bus/platform/devices/ff350000.video-codec /sys/firmware/devicetree/base/video-codec@ff350000 it doesn't appear that I have the kernel module. Any ideas where I can find the source code for the 'video-codec' kernel module?
  4. Hello Everyone! What is the kernel config option that I need to set to enable the VPU driver? Background: I'm using the most current RK3328 RENEGADE armbian image (debian non-desktop) on my ROC-RK3328-CC (Libre Renegade). I've compiled a brand new kernel with the armbian build tool. first, I cloned and compiled gstreamer and it's plugins from Github. Everything works fine but no video acceleration... So then I clone, compile, and install libmali, mpp, gstreamer-rockchip and gstreamer-rockchip-extra, and although the new pluggins are now available to gstreamer (specifi
  5. I have got this working now... I could only find 2 GPIO pins on the ROC-RK3328-CC that were usable: Labeled "GPIO" - Pin 32 - GPIO0_A0 - Accesible as GPIO 0 Labeled "CLK0" - Pin 22 - GPIO0_A2 - Accesible as GPIO 2 Looking at this table, you can see that BCM 24 and 25 are routed to GPIO 102 and 103 on the ROCK64. https://github.com/Leapo/Rock64-R64.GPIO/wiki/GPIO-Modes So I replaced 102 and 103 with 0 and 2, on the line begining with "BCM_to_ROCK =" I then added 0 and 2 to the line beginning with "ROCK_valid_channels", so that it would pass the sanity checks
  6. I found this pin mapping table which refers to the Rock64, however looking at the GPIO pin numbers, it looks like it very likely is the same board pin numbers for the ROC-RK3328-CC. https://github.com/Leapo/Rock64-R64.GPIO/wiki/GPIO-Modes I will try it out tomorrow afternoon and report back with the results. Thanks everyone.
  7. Wow thank you so much for your insight! I changed RK3399 to RK3328 I changed ff1c0000 to ff190000 I removed all fragments relating to SPI1/2/3 /dts-v1/; / { compatible = "rockchip,rk3328"; fragment@0 { target-path = "/aliases"; __overlay__ { spi0 = "/spi@ff190000"; }; }; fragment@1 { target = < 0xffffffff >; __overlay__ { #address-cells = < 0x01 >; #size-cells = < 0x00 >; spidev { compatible = "spidev"; status = "disabled"; reg = < 0x00 >; spi-max-frequency = < 0x989680 >; }; };
  8. The overlay files are definitely there... /boot/dtb/rockchip/overlay$ ls -l total 36 -rw-r--r-- 1 root root 2455 Jan 4 15:31 README.rockchip-overlays -rw-r--r-- 1 root root 2698 Jan 4 15:31 rockchip-fixup.scr -rw-r--r-- 1 root root 218 Jan 4 15:31 rockchip-i2c7.dtbo -rw-r--r-- 1 root root 218 Jan 4 15:31 rockchip-i2c8.dtbo -rw-r--r-- 1 root root 267 Jan 4 15:31 rockchip-pcie-gen2.dtbo -rw-r--r-- 1 root root 1314 Jan 4 15:31 rockchip-spi-jedec-nor.dtbo -rw-r--r-- 1 root root 1266 Jan 4 15:31 rockchip-spi-spidev.dtbo -rw-r--r-- 1 root root 384 Jan 4 15:31 rockchip-uart4.dtbo -rw-
  9. So I decided to add uart4 overlay as well (after SPI, I'll be trying to enable UART): verbosity=1 overlay_prefix=rockchip rootdev=UUID=69320d26-57b1-49ed-b3d0-c1402e101ae0 rootfstype=ext4 overlays=spi-spidev uart4 param_spidev_spi_bus=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u and now somehow both are showing up in the debugger however both error out.... Applying kernel provided DT overlay rockchip-spi-spidev.dtbo fdt_overlay_apply(): FDT_ERR_NOTFOUND 384 bytes read in 24 ms (15.6 KiB/s) Applying kernel provided DT overlay rockchip-uart4.d
  10. So I had a spare arduino nano and looked up how to use that as a USB TTL debugger... here's the output (I don't see anything noting the spidev overlay) U-Boot 2017.09-armbian (Jan 07 2020 - 22:21:19 +0100) Model: Firefly ROC-RK3328-CC DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 Card did not respond to voltage select! mmc_init: -95, time 10 *** Warning - No block device, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Firefly ROC-RK3328-CC misc_init_r boot mode 0. Net: Net Initialization Skipped No etherne
  11. just ran it again after reboot and it comes back with disabled user1@renegade:~$ sudo cat /proc/device-tree/spi@ff190000/status disableduser1@renegade:~$
  12. Thank you for the info... I'll see about ordering a USB TTY debugger when I run that command, there's no output. It just goes straight back to the prompt. I verified that the directory and file do exist: ls -l /proc/device-tree/spi@ff190000/ total 0 -r--r--r-- 1 root root 4 Feb 13 20:19 '#address-cells' -r--r--r-- 1 root root 16 Feb 13 20:19 clock-names -r--r--r-- 1 root root 16 Feb 13 20:19 clocks -r--r--r-- 1 root root 40 Feb 13 20:19 compatible -r--r--r-- 1 root root 6 Feb 13 20:19 dma-names -r--r--r-- 1 root root 16 Feb 13 20:19 dmas -r--r--r-- 1
  13. Just to be clear, I believe device tree overlays are not working for me, and am wondering how I go about checking.
  14. Thank you for moving to the correct place. Is serial output the only way to get the u-boot debug info? Would I need to use a USB TTY device to view this? I assumed the u-boot info was written to some log file. Is that incorrect? What I'm looking for is something that would tell me if the fixup.scr was being executed properly, and any other dt overlay information. At this point I just want to make sure the device tree overlays are actually working Although this is for a different board, this is what I'm talking about (just did a cut and
  15. Hello everyone! I'm trying to use a small SPI LED screen with my ROC-RK3328-CC. I've scoured all over this website as well as the internet for information on enabling SPI on my ROC-RK3328-CC (libre renegade), and I'm sorry to say after trying so many things, I still cannot get it enabled. I'm currently using this image: Armbian_19.11.7_Renegade_buster_current_5.4.8.img I've added the following 2 lines to /boot/armbienEnv.txt overlays=spi-spidev param_spidev_spi_bus=0 and after reboot, nothing. nothing for dmesg|grep spi and no spidev devices in /dev