Blackmagic DeckLink SDI Micro in Rock5B

#1

Has anyone attempted to use the Blackmagic DeckLink SDI Micro in the Rock5B? Attempting to output through the card causes the DeckLink kernel module to hang. The Rock5B has to be power-cycled in order to use the DeckLink card again once this occurs. This was tested with the Blackmagic DeckLink SDK sample apps (SignalGenerator and TestPattern).

Not sure if this is an issue with their driver or some other kind of compatibility issue with the hardware. Just wanted to see if anyone else had tried it, and if so, had any success in getting output to work. I don’t have any other ARM64 platforms to test the card on.

Another person posted on the unofficial ubuntu-rockchip distro GitHub Discussions page asking the same thing. https://github.com/Joshua-Riek/ubuntu-rockchip/discussions/413

#2

Maybe because the Rock5b has 1080p hdmi in, its likely to be a rarity


Dunno about that card though

#3

The Blackmagic DeckLink SDI Micro is an M.2 form-factor capture/output device for SDI video. In my case it is installed in the M.2 slot on the bottom of the Rock5B. I was not using the Rock5B built-in HDMI input in this case.

#4

This issue looks like it might be due to the vmalloc size being too small (256MB) for the BlackMagic kernel module, which apparently wants 512MB. Is it possible to change the vmalloc size on Rock5B? My understanding is that this is typically done at boot time, i.e. in the bootloader. I’ve seen examples of doing this with a grub parameter, but Rock5B does not use Grub, to my knowledge. Does anyone know the answer?

#5

Its uboot not grub so you get the boot.cmd than what I can not remember grub does now.
That loads ubuntuEnv.txt which is a guess what you looking for.
I dunno if you can add the entry there as maybe but likely on updates it could get overwritten.
@RadxaYuntian Likely will be able to tell you or if it will have to be a kernel config and create your own custom kernel.

bootargs=root=UUID=d312d528-2e2f-4044-a702-659ba4cf55d5 rootfstype=ext4 rootwait rw console=ttyS2,1500000 console=tty1 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0 quiet splash plymouth.ignore-serial-consoles
fdtfile=rk3588-rock-5b.dtb
overlay_prefix=rock-5b
overlays=

Have a look at the boot /image as its a fat partition that with disk mounter you can have a look at or when running from inside just cd /boot and edits just need to be made with sudo?

#6

If you are using our latest system, then you can edit /etc/kernel/cmdline and add vmalloc=512M to that file, separated from other parameters with a space. Then run sudo u-boot-update to generated new boot config.

For other systems please consult their maintainers.

2 Likes