There is definitly no hardware acceleration support for the efusA9X, see here:
https://community.nxp.com/t5/i…m-p/439215/highlight/true
CASE CLOSED.
Posts by BrenkeM
-
-
This case seems to be closed according [1] under the chapter "4.10 Multimedia (gstreamer support)" there is the statement that the efusA9X which is based on a imx6sx chip does not provide any hardware acceleration:
QuoteBoards based on fsimx6sx do not have any hardware accelerated video or audio processing
in gstreamer. Decoding or encoding can only be done in software.
-
I checked out the BUILDROOT symboles and noticed that the i.MX platform (imx6sl/imx6sx) ---> has only a GPU but no VPU. According [1], the i.MX 6SoloX Processor contains a Vivante GC400T GPU, which is not a VPU. Regarding this information, I configured the BUILDROOT system according [2] and the Linux Kernel according [3].
[1]:
https://www.nxp.com/products/p…d-cortex-m4-cores:i.MX6SX
[2]:
Display MoreDiff- diff --git a/configs/fsimx6sx_min_efus_defconfig b/configs/fsimx6sx_min_efus_defconfig
- index cca93bde..c86dbc68 100644
- --- a/configs/fsimx6sx_min_efus_defconfig
- +++ b/configs/fsimx6sx_min_efus_defconfig
- @@ -34,6 +34,12 @@ BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="efusa9x.dts"
- BR2_PACKAGE_BUSYBOX_CONFIG="board/f+s/common/busybox-1.30.1.config"
- BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
- # BR2_PACKAGE_EUDEV_ENABLE_HWDB is not set
- +BR2_PACKAGE_FREESCALE_IMX=y
- +BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX6S=y
- +BR2_PACKAGE_IMX_CODEC=y
- +BR2_PACKAGE_FIRMWARE_IMX=y
- +BR2_PACKAGE_IMX_GPU_VIV=y
- +BR2_PACKAGE_KERNEL_MODULE_IMX_GPU_VIV=y
- BR2_PACKAGE_UBOOT_TOOLS=y
- BR2_PACKAGE_OPENCV3=y
- BR2_PACKAGE_OPENCV3_LIB_VIDEOIO=y
[3]:
Display MoreDiff- diff --git a/Kconfig b/Kconfig
- index b39a5d19..6ff7c9f5 100644
- --- a/Kconfig
- +++ b/Kconfig
- @@ -169,7 +169,7 @@ CONFIG_REGULATOR_ANATOP=y
- CONFIG_REGULATOR_PFUZE100=y
- # CONFIG_HID is not set
- # CONFIG_USB_SUPPORT is not set
- -# CONFIG_MXC_GPU_VIV is not set
- +CONFIG_MXC_GPU_VIV is not set
- CONFIG_NEW_LEDS=y
- CONFIG_LEDS_CLASS=y
- CONFIG_LEDS_GPIO=y
-
I wand to accelerate video decoding via ffmpeg using the internel imx6 VPU on the efusA9X module. Currently ffmpeg is running on our headless system and does all decoding in software (CPU). But I want wo enable hardware acceleration using the internel VPU. Is there any detailed instructions how to achive this? I currently researched the following links:
libimxvpuapi - frontend for i.MX hardware video codecs:
https://github.com/Freescale/libimxvpuapi
i.MX 6Dual/6Quad VPU Application Programming Interface Linux Reference Manual:
-
-
To adapt the buildroot configuration for using the mainline kernel I changed the following parts:
- changed linux folder (linux-fsimx6sx) to git repo of mainline kernel
- prepair the changes under [1]
- build image and load according uboot procedure under [0]
[0]:
Starting and running system completely in RAM (from UBOOT)
[1]:
Display MoreDiff- diff --git a/efusa9x.dts b/efusa9x.dts
- index 20dd8991..39153b4b 100644
- --- a/efusa9x.dts
- +++ b/efusa9x.dts
- @@ -142,10 +142,10 @@ lvds_wvga { \
- //#define CONFIG_EFUSA9X_CAPTOUCH_ILITEK
- /* CMA: Set 320 MB for Continuous Memory Allocator */
- -#define CONFIG_EFUSA9X_CMA_SIZE 0x14000000
- +//#define CONFIG_EFUSA9X_CMA_SIZE 0x14000000
- /* On-board NAND */
- -#define CONFIG_EFUSA9X_NAND
- +//#define CONFIG_EFUSA9X_NAND
- /* On-board eMMC */
- //#define CONFIG_EFUSA9X_EMMC
- @@ -565,15 +565,15 @@ lvds_wvga { \
- };
- /* RAM size for Continues Memory Allocator */
- -&cma {
- - size = <CONFIG_EFUSA9X_CMA_SIZE>;
- -};
- -
- -&busfreq {
- - /* Disable bus frequency scaling, because reducing bus frequency to
- - 24 MHz does not work with all types of DDR3 RAM */
- - disable-scaling;
- -};
- +//&cma {
- +// size = <CONFIG_EFUSA9X_CMA_SIZE>;
- +//};
- +
- +//&busfreq {
- +// /* Disable bus frequency scaling, because reducing bus frequency to
- +// 24 MHz does not work with all types of DDR3 RAM */
- +// disable-scaling;
- +//};
- #ifdef CONFIG_EFUSA9X_ADC_1
- &adc1 {
Display MoreDiff- diff --git a/Kconfig b/Kconfig
- index b39a5d19..cd5057a3 100644
- --- a/Kconfig
- +++ b/Kconfig
- @@ -10,6 +10,12 @@ CONFIG_CGROUPS=y
- CONFIG_NAMESPACES=y
- # CONFIG_PID_NS is not set
- CONFIG_RELAY=y
- +CONFIG_BLK_DEV_INITRD=y
- +# CONFIG_RD_BZIP2 is not set
- +# CONFIG_RD_LZMA is not set
- +# CONFIG_RD_XZ is not set
- +# CONFIG_RD_LZO is not set
- +# CONFIG_RD_LZ4 is not set
- CONFIG_EXPERT=y
- CONFIG_KALLSYMS_ALL=y
- CONFIG_PERF_EVENTS=y
- @@ -88,9 +94,6 @@ CONFIG_MTD_PHYSMAP_OF=y
- CONFIG_MTD_DATAFLASH=y
- CONFIG_MTD_M25P80=y
- CONFIG_MTD_SST25L=y
- -CONFIG_MTD_NAND=y
- -CONFIG_MTD_NAND_GPMI_NAND_FUS=y
- -CONFIG_MTD_NAND_MXC=y
- CONFIG_MTD_SPI_NOR=y
- CONFIG_SPI_FSL_QUADSPI=y
- CONFIG_MTD_UBI=y
Display MoreDiff- diff --git a/board/f+s/common/sbin/fsgetty b/board/f+s/common/sbin/fsgetty
- index 196ad2fe..141b3892 100755
- --- a/board/f+s/common/sbin/fsgetty
- +++ b/board/f+s/common/sbin/fsgetty
- @@ -34,9 +34,11 @@ get_login_tty
- if [ $login_tty != null ] ; then
- get_login_speed
- logger -t $fsgetty "Starting getty on $login_tty with speed $login_speed"
- - exec /sbin/getty -L $login_tty $login_speed vt100
- +# exec /sbin/getty -L $login_tty $login_speed vt100
- fi
- +exec /sbin/getty -L 115200 ttymxc0 xterm
- +
- logger -t $fsgetty "No login requested, going to sleep"
- # Sleep forever; wake up every second to check if login_tty has changed
Display MoreDiff- diff --git a/configs/fsimx6sx_min_efus_defconfig b/configs/fsimx6sx_min_efus_defconfig
- index cca93bde..8009890c 100644
- --- a/configs/fsimx6sx_min_efus_defconfig
- +++ b/configs/fsimx6sx_min_efus_defconfig
- @@ -26,27 +26,22 @@ BR2_ROOTFS_OVERLAY="rootfs_overlay"
- BR2_ROOTFS_POST_BUILD_SCRIPT="board/f+s/fsimx6/finalscript_min-fsimx6sx"
- BR2_LINUX_KERNEL=y
- BR2_LINUX_KERNEL_CUSTOM_VERSION=y
- -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.9.88"
- +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.19.0"
- BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
- BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="Kconfig"
- BR2_LINUX_KERNEL_DTS_SUPPORT=y
- BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="efusa9x.dts"
- BR2_PACKAGE_BUSYBOX_CONFIG="board/f+s/common/busybox-1.30.1.config"
- BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
- +BR2_PACKAGE_BZIP2=y
- # BR2_PACKAGE_EUDEV_ENABLE_HWDB is not set
- BR2_PACKAGE_NANO=y
- +BR2_TARGET_ROOTFS_CPIO=y
- +BR2_TARGET_ROOTFS_CPIO_GZIP=y
- +BR2_TARGET_ROOTFS_CPIO_UIMAGE=y
- # BR2_TARGET_ROOTFS_TAR is not set
- -BR2_TARGET_ROOTFS_UBIFS=y
- -BR2_TARGET_ROOTFS_UBIFS_LEBSIZE=0x1f000
- +BR2_PACKAGE_HOST_E2FSPROGS=y
-
Sometime it would be nice to only run the current release of a F+S module with a mainline kernel, for example to check if bugs where fixed in newer versions or to develop patches for pushing them to the mainline source code later.
What do we need to do, to build and run the current buildroot fsimx6sx-B2019.11 release with the current mainline kernel (5.18.0) from https://github.com/torvalds/linux?
-
To simplify the procedure above, I recommend to prepare a cpio image:
Display MoreCode- # config system
- make menuconfig
- Filesystem images
- …
- [*] cpio the root filesystem (for use as an initial RAM filesystem)
- Compression method (gzip)
- [*] Create U-Boot image of the root filesystem
- …
- # config kernel
- make linux-menuconfig
- General setup
- [*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
- …
- [*] Support initial ramdisks compressed using gzip
- …
Then you can (for example on a efusA9X module) run the following commands in the uboot shell:
-
Indeed, I checked the kernel configuration but missed that option. But now it works and we can perform test independent from NAND.
Case closed.
Thanks.
-
"Sorry, it seems you were trying to access a page that doesn't exist.
Please check the spelling of the URL you were trying to access and try again."
Is this service inactive or just moved to a different URL?
-
A alternative of how to run a system in RAM (because there are a lot of options to achive this would also be great. Thanks.
-
To run a system without any ROM completely in RAM, on a efusa9x module, I tried the following steps, but failed to load the ROOTFS in the RAM from the LINUX kernel.
Following the steps here to configured a minimal system and started it from RAM:
https://imxdev.gitlab.io/tutor…o_boot_imx_using_ramdisk/
The used buildroot configuration for the filesystem is the following:
Display MoreCode- [ ] axfs root filesystem │ │
- │ │ [ ] btrfs root filesystem │ │
- │ │ [ ] cloop root filesystem for the target device │ │
- │ │ [ ] cpio the root filesystem (for use as an initial RAM filesystem) │ │
- │ │ [ ] cramfs root filesystem │ │
- │ │ [*] ext2/3/4 root filesystem │ │
- │ │ ext2/3/4 variant (ext2 (rev1)) ---> │ │
- │ │ () filesystem label │ │
- │ │ (40M) exact size │ │
- │ │ (0) exact number of inodes (leave at 0 for auto calculation) │ │
- │ │ (5) reserved blocks percentage │ │
- │ │ (-O ^64bit) additional mke2fs options │ │
- │ │ Compression method (gzip) ---> │ │
- │ │ [ ] f2fs root filesystem │ │
- │ │ [ ] initial RAM filesystem linked into linux kernel │ │
- │ │ [ ] jffs2 root filesystem │ │
- │ │ [ ] romfs root filesystem │ │
- │ │ [ ] squashfs root filesystem │ │
- │ │ [ ] tar the root filesystem │ │
- │ │ [ ] ubi image containing an ubifs root filesystem │ │
- │ │ [ ] ubifs root filesystem │ │
- │ │ [ ] yaffs2 root filesystem
And starting the system with the following UBOOT commands leads to the error under [1]:
Display MoreCode- # requirements
- # - bootfile set (kernel)
- setenv bootfile zImage
- # - bootfdt set (DTB)
- setenv bootfdt efusa9x.dtb
- tftpboot . ${bootfile}
- tftpboot ${fdtaddr} ${bootfdt}
- tftpboot 83000000 rootfs.ext2.gz.uboot
- setenv initrd_size ${filesize}
- setenv bootargs 'console=ttymxc0,115200 login_tty=ttymxc0,115200 root=/dev/ram rw'
- bootz 81000000 83000000 82000000
[1]:
Display MoreCode- …
- caam_jr 2101000.jr0: Instantiated RNG4 SH1.
- caam algorithms registered in /proc/crypto
- caam_jr 2101000.jr0: registering rng-caam
- caam-snvs 20cc000.caam-snvs: can't get snvs clock
- caam-snvs 20cc000.caam-snvs: violation handlers armed - non-secure state
- NET: Registered protocol family 26
- NET: Registered protocol family 17
- can: controller area network core (rev 20120528 abi 9)
- NET: Registered protocol family 29
- can: raw protocol (rev 20120528)
- can: broadcast manager protocol (rev 20161123 t)
- can: netlink gateway (rev 20130117) max_hops=1
- 8021q: 802.1Q VLAN Support v1.8
- Key type dns_resolver registered
- cpu cpu0: Registered imx6q-cpufreq
- imx_thermal 2000000.aips-bus:tempmon: Extended Commercial CPU temperature grade - max:105C critical:100CC
- rtc-pcf8563 0-0051: low voltage detected, date/time is not reliable.
- rtc-pcf8563 0-0051: retrieved date/time is not valid.
- rtc-pcf8563 0-0051: hctosys: unable to read the hardware clock
- List of all partitions:
- 0100 8192 ram0 (driver?)
- 0101 8192 ram1 (driver?)
- 0102 8192 ram2 (driver?)
- 0103 8192 ram3 (driver?)
- 0104 8192 ram4 (driver?)
- 0105 8192 ram5 (driver?)
- 0106 8192 ram6 (driver?)
- 0107 8192 ram7 (driver?)
- 1f00 262144 mtdblock0 (driver?)
- No filesystem could mount root, tried: ext2
- Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
P.s.:
Additional I tried to define the ROOTFS by its address and size like mentioned here:
https://lists.denx.de/pipermail/u-boot/2009-June/054782.html
Code- tftpboot . ${bootfile}
- tftpboot ${fdtaddr} ${bootfdt}
- tftpboot 83000000 rootfs.ext2.gz.uboot
- #setenv initrd_size ${filesize}
- #setenv bootargs 'console=ttymxc0,115200 login_tty=ttymxc0,115200 root=/dev/ram rw'
- setenv bootargs "console=ttymxc0,115200 login_tty=ttymxc0,115200 root=/dev/ram0 rd_start=83000000 rd_size=${filesize} rootfstype=ext2 rw"
- bootz 81000000 83000000 82000000
But this results in the same error as in [1].
How can I successfully let the kernel find the root filesystem?
-
Hi, do you build your LINUX system with Buildroot or Yocto?
For buildroot simple set the following option to include the ssh server into your build:
Display MoreCode- make menuconfig
- Target packages --->
- Networking applications --->
- [*] openssh
- Alternativly you can select dropbear as a smaller embedded variant of SSH.
- [*] dropbear │ │
- │ │ [*] client programs │ │
- │ │ [ ] disable reverse DNS lookups │ │
- │ │ [*] optimize for size │ │
- │ │ [ ] log dropbear access to wtmp │ │
- │ │ [ ] log dropbear access to lastlog │ │
- │ │ [ ] enable legacy crypto
Afterwards, build the image again and load it to the system, than you should check the following directory on your embedded system:
-
To patch the kernel we can simple follow one of the tutorials online (see [1]).
But for the kernel version 4.9.88 we can not find a matching rt patch. But a older one is working nice for this issue, see [2].
This will patch the kernel ready for compilation, but it is recommended to adjust the realtime priorities, see [3] for this. Otherwise a realtime application can sporadically block your system.
I also attached both patches for every one how wants to use it.
[1]:
https://stackoverflow.com/ques…rt-linux-patch-for-ubuntu
[2]:
https://mirrors.edge.kernel.or…atch-4.9.84-rt62.patch.gz
[3]:
-
Detailed information about PREEMPT RT can be found in the presentation here:
-
To handle application in the Linux userspace in hard realtime the current LINUX kernel 4.9.88 must be patched.
This is because LINUX does not include all realtime patches from the PREEMT RT version (which is the preferred realtime implementation from LINUX Kernel developers). Newer kernel will less differ from a fully PREEMPT RT kernel version.
So, how do we have to patch the Kernel from the efusA9X release to gain full realtime support?
-
To use the ads1118 ADC IC via an SPI interface with the current efusA9X kernel (4.9.88) it is necessarry to add a driver to the kernel space.
After some research I found a kernel driver implementation under [1]. I collected all information (code+docs) and implemented them into the current kernel with the attached patch under [2]. After adding the node to the device tree (convertig spidev to adc node (see [3])), I testing the driver successfully for a half day.
@F+S: I request to implement this patch to your kernel sources.
Best regards.
[1]:
https://lore.kernel.org/patchwork/patch/698694/
[2]:
0001-add-support-for-adc-ads1118.patch.zip
[3]:
Display MoreDiff- diff --git a/efusa9x.dts b/efusa9x.dts
- index 2e1f157..048a211 100644
- --- a/efusa9x.dts
- +++ b/efusa9x.dts
- @@ -1417,12 +1417,24 @@ lvds_wvga { \
- reg = <0>;
- };
- - spidev@1 {
- - #address-cells = <1>;
- - #size-cells = <1>;
- - compatible = "linux,spidev";
- + ads1118@1 {
- + compatible = "ti,ads1118";
- spi-max-frequency = <20000000>;
- + spi-cpha;
- reg = <1>;
- + #address-cells = <1>;
- + #size-cells = <0>;
- + ti,tempsensor;
- + voltage0@0 {
- + reg = <0>;
- + ti,fullscale = <6144000>;
- + ti,datarate = <128>;
- + };
- + voltage1@1 {
- + reg = <1>;
- + ti,fullscale = <6144000>;
- + ti,datarate = <128>;
- + };
- };
- spidev@2 {
-
I also would like to request that the adc nodes in the device tree will be configurable through macros like other hardware too.
Please patch also the device tree also on your (F+S) side.
P.s.: Sorry but I need to rename the patch file because the website is not accepting a file suffix like "patch":
$ mv 0001-add_adc_node_control.patch.txt 0001-add_adc_node_control.patch
-
Hello,
I just want to share my investigation regarding the ADCs and how I got it working:
[1] provides a overview about the ADCs numbers, channels and devicefiles. The kernel support can be enabled via [2] and [3] provides a overview about the devicefiles in the filesystem. To calculate the voltage on the pin, see [4]. Furthermore, I contacted F+S to produce efusA9X modules with the missing parts. Until the production will be adjusted please take a look at the attached picture and [5], which provides the information what resistor network IC is missing and where it needs to be placed. Hopefully the efusA9X module will be updated soon.
@F+S: Please check if everything here is correct and please tell us know when the production was adjusted.
[1]:Code- ADC# | channels| pin | /sys/bus/iio/devices/iio\:
- ----------------------------------------------------------------------------
- adc1 | ADC_A | 44 | device0/in_voltage0_raw
- adc1 | ADC_B | 42 | device0/in_voltage1_raw
- adc2 | ADC_C | 40 | device1/in_voltage0_raw
- adc2 | ADC_D | 38 | device1/in_voltage1_raw
[2]:
[3]:
Display MoreCode- $ ls /sys/bus/iio/devices/
- iio:device0@ iio:device1@
- $ ls /sys/bus/iio/devices/iio\:device0/*
- /sys/bus/iio/devices/iio:device0/dev
- /sys/bus/iio/devices/iio:device0/in_voltage0_raw
- /sys/bus/iio/devices/iio:device0/in_voltage1_raw
- /sys/bus/iio/devices/iio:device0/in_voltage_sampling_frequency
- /sys/bus/iio/devices/iio:device0/in_voltage_scale
- /sys/bus/iio/devices/iio:device0/name
- /sys/bus/iio/devices/iio:device0/of_node@
- /sys/bus/iio/devices/iio:device0/sampling_frequency_available
- /sys/bus/iio/devices/iio:device0/subsystem@
- /sys/bus/iio/devices/iio:device0/uevent
- /sys/bus/iio/devices/iio:device0/power:
- autosuspend_delay_ms runtime_active_time runtime_suspended_time
- control runtime_status
[4]:
[5]:
QuoteDisplay MoreHallo Herr Brenke,
unten im Bild habe ich Ihnen rot das zu bestückende Bauteil markiert. Gerne können wir Ihnen dazu passende Widerstandsnetzwerke zukommen lassen. Andernfalls gibt es das Bauteil z.B. bei digikey:
https://www.digikey.de/product…AT10-000J4LFCT-ND/3592947
Das zukünftige Bestücken des Bauteils habe ich mir nochmals notiert und werde dies nächste Woche mit unserem Vertrieb abklären.
-
Hello,
I noticed that if I strip down the "fsimx6sx_min_defconfig" I am limited of the filesystem size to 7110656 bytes, when I am using buildroot.
So for example I create a system and load it to check the disk free space: I see that I only use 5.1 MB (see [1]). But the created and loaded ubifs image is bigger than this (~7 MB, see [2]).
Does this have to so with the options:
BR2_TARGET_ROOTFS_UBIFS_LEBSIZE
BR2_TARGET_ROOTFS_UBIFS_MINIOSIZE
BR2_TARGET_ROOTFS_UBIFS_MAXLEBCNT
I also checked the docu under [3], but could not find a suitable answer. For example how can I create a ubifs image that takes only 3 or 4 MB of space?
[1]:
# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 214.1M 5.1M 209.1M 2% /
…
[2]:
$ du -b output/images/rootfs.ubifs
7110656 output/images/rootfs.ubifs
[3]:
https://bootlin.com/blog/creating-flashing-ubi-ubifs-images/
