12:28 <eduardas_m> hello, anyone doing development with imx6ul in particular?

14:05 <frsc> eduardas_m: yes

14:28 <eduardas_m> frsc, it is nice to see that this channel is not completely dead :) I am developing using Variscite DART6UL SoM... I was wondering if perhaps someone would be willing to share their experience with the imx6ul

14:32 <eduardas_m> for example, how you accomplish reliable updates or boot optimization

14:34 <eduardas_m> frsc, does your application use a GUI? do you feel much restricted by the imx6ul lack of accelerated graphics and OpenGL?

14:36 <frsc> eduardas_m: We are currently working on customized BSPs for our custom UL-SoM, but we haven't done anything special regarding updates or boot optimization so far

14:37 <eduardas_m> frsc, do you happen to use a resistive touchscreen with integrated TSC?

14:37 <eduardas_m> I have made it work with Qt5.6 using tslib, but it is very unreliable so far

14:37 <frsc> eduardas_m: We have tested graphics with a Qt-Widgets demo app and gstreamer video playback with a small 4.3" LCD (480x272).

14:38 <frsc> It seems to work fine, but causes reasonable CPU load

14:38 <eduardas_m> frsc, I have actually done something similar

14:38 <eduardas_m> for UVC device

14:39 <eduardas_m> although I had one device where gstreamer did not work so I resorted to V4L2

14:39 <frsc> We haven't used the integrated TSC so far, only cap. touch via I2C.

14:40 <eduardas_m> frsc, my devboard comes with capacitive touch via i2c too and that works fine

14:40 <eduardas_m> but when it comes to resistive via TSC as I said that I find a bit problematic

14:40 <eduardas_m> may be that my tslib calibrations are wrong

14:41 <eduardas_m> so I was looking perhaps someone could comment on that

14:41 <frsc> eduardas_m: Did you check if there are any filters enabled in the tslib config file?

14:42 <eduardas_m> frsc, there are and I pretty much was using the defaults... haven't really found any deeper info on how to calibrate those though

14:43 <eduardas_m> during ts_test I get a coordinate jump sometimes

14:43 <eduardas_m> and have no idea where that comes from

14:43 <eduardas_m> whether that is a hardware issue or not

14:44 <frsc> eduardas_m: I'm just asking, because I was using tslib with a capacitive touch recently and the filters kind of messed up the readings

14:44 <frsc> but I guess this is because tslib is not intended to be used with cap touch

14:46 <eduardas_m> frsc, do you use some standard update framework for your other BSPs like SWUpdate?

14:46 <eduardas_m> because I was trying to use meta-swupdate with my BSP

14:47 <eduardas_m> would build with fsl community bsp krogoth + meta-swupdate jethro

14:48 <eduardas_m> but the update archive generation tool in meta-swupdate is something I can not get to work

14:49 <eduardas_m> things like meta-swupdate have u-boot config dependencies

14:49 <frsc> eduardas_m: no sorry, I have no experience with swupdate or the like

14:49 <eduardas_m> so I thought maybe there is a standard update mechanism that is more easily comaptible with imx6ul BSPs

14:50 <eduardas_m> frsc, do you not use a dual image update system for any of your stuff?

14:51 <eduardas_m> because it is said that doing updates via packages only is bad for QA

14:54 <frsc> eduardas_m: currently our update mechanism often looks like booting an image from sd card and reflashing the new image to nand.

14:55 <eduardas_m> frsc, in my case it is unacceptable as there is no SD card holder, or even USB port for mfgtool

14:56 <eduardas_m> also, is there any reason why you are using NAND?

14:56 <eduardas_m> I am using eMMC

14:57 <eduardas_m> could switch to NAND as there is a variant of DART6UL with it, but am wondering if there is anything to gain there?

14:57 <frsc> eduardas_m: We will probably have this case too at some time in the future and then we will have to think about more sophisticated update routines

14:58 <eduardas_m> frsc, today I have done something really primitive to get dual image update capability.. tested only on SD card so far

14:58 <eduardas_m> I have an MBR with 4 partitions only: boot1, rootfs1, boot2, rootfs2

14:59 <frsc> eduardas_m: on our UL-SoM we currently use SD card or USB-serial loader for intitial boot or update and then flash to NOR and/or eMMC

14:59 <eduardas_m> and I simply mount the unused boot2 and rootfs2 and use standard tools like rm -rf *, cp and tar -xjvf

14:59 <eduardas_m> then use fw_setenv to set u-boot to boot from updated partitions

15:01 <eduardas_m> it works, but is long and kinda ugly since I'm relying on the filesystem to do everything properly

15:02 <eduardas_m> frsc, could you comment on my earlier question of NAND vs eMMC?

15:04 <frsc> We're often using NAND on our i.MX6S-based boards, but on our UL-SoM we currently only have NOR for the bootloader and small linux images.

15:05 <frsc> For larger memory we have eMMC on the baseboard

15:09 <frsc> eduardas_m: Generally, from the hardware point of view, I can't tell you much, because I'm mainly working on the software/BSP end