Posts by ahmedawad

    Thanks for your reply.


    I have tried your suggestion as follows:


    * I modified the LCD string "LCD-ET035080" in this file linux-4.1.15-fus-Y1.0/drivers/video/fbdev/mxc/mxc_lcdif.c according to your values that you suggested -->

    Code
    1. {
    2. /* 320x240 @ 60 Hz , pixel clk @ 6.5MHz */
    3. "LCD-ET035080", 60, 320, 240, 153846, 48, 20, 8, 4, 20, 10,
    4. 0,
    5. FB_VMODE_NONINTERLACED,
    6. 0,
    7. },

    Please is it possible to provide the values to be written in mxc_lcdif.c file as I tried many times but no gain to get our LCD working?


    another question please, is your 3.5 LCD working with efusA9 Quad core module ?


    Thanks,

    Kind regards

    Hi,


    please I want to mention that, I did not change the LCD configurations in file "linux-4.1.15-fus-Y1.0/drivers/video/fbdev/mxc/mxc_lcdif.c" for your 3.5 LCD and here is actually the configuration I used:


    Code
    1. {
    2. /* 320x240 @ 60 Hz , pixel clk @ 6.5MHz */
    3. "LCD-ET035080", 60, 320, 240, 153846, 48, 20, 8, 4, 20, 10,
    4. 0,
    5. FB_VMODE_NONINTERLACED,
    6. 0,
    7. },

    Then I had no chance to get it to work.


    Please I want to mention also that my 3.5 LCD worked very well on the 7Ull efus module (single core), because the configurations were looking a little bit different than in efus Quad core module.


    So I actually changed the LCD settings in the dts file of efus7ull module "linux-4.1.15-fus-Y1.0/arch/arm/boot/dts/efusa7ul.dts" to -->


    (It was previously configured to your standard 7 inch display and I used this configuration for my 3.5 LCD)



    Then with that configuration above, everything worked on the 7ull module but I tried to use it as well for the quad core but no gain.


    There are 4 parameters "hsync-active" , "vsync-active" , "de-active" and "pixelclk-active" which I could not set them in the "mxc_lcdif.c" for the 3.5 inch display in the "LCD-ET035080" part which I posted up there.


    Thanks in advance,

    kind regards

    Hi everyone,


    I am trying to integrate this 3.5 display with efusA9 quad core platform. That display has exactly the same AC timing characteristics as your 3.5 inch display. I want to know please what are the correct kernel configuration for this 3.5 display?


    I know I have to change the following:


    1- I modified only these lines in this file --> linux-4.1.15-fus-Y1.0/arch/arm/boot/dts/efusa9q.dts (I used LCD-ET035080 instead of the 7 inch display)

    Code
    1. /*
    2. * Configure LCD settings here (ignored if LCD is not used);
    3. * see drivers/video/fbdev/mxc/mxc_lcdif.c for possible LCD mode strings
    4. */
    5. #define CONFIG_EFUSA9_LCD_BPP 32
    6. #define CONFIG_EFUSA9_LCD_PIX_FMT "BGR666"
    7. #define CONFIG_EFUSA9_LCD_MODE_STR "LCD-ET035080"


    2- I looked as well into linux-4.1.15-fus-Y1.0/drivers/video/fbdev/mxc/mxc_lcdif.c file where the LCD-ET035080 defined


    Code
    1. {
    2. /* 320x240 @ 60 Hz , pixel clk @ 6.5MHz */
    3. "LCD-ET035080", 60, 320, 240, 153846, 68, 20, 18, 4, 20, 10,
    4. 0,
    5. FB_VMODE_NONINTERLACED,
    6. 0,
    7. },


    If you please have a look at the data sheet page 10 of my display, you will find it is exactly the same as your display at page 5. This means there is no difference between your display and my display and your configuration shall work.


    please what shall I change in order to get this 3.5 display to work?


    Thanks in advance

    Ahmed

    Hi everyone,


    I tried to build chromium within yocto and I followed the steps as in the Efus First steps guide, but in the middle of the build process bitbake can not find this file "file://include.gypi".


    in summary I did the following:

    - I downloaded "fsimx6ul-Y1.0.tar.bz2"

    - ./setup-yocto

    - DISTRO=fus-imx-x11 MACHINE=fsimx6ul source ./fsl-setup-release.sh -b build

    - I added the chromium package as in section 9.2.7

    - bitbake fus-image-std


    only in middle of the build process, I hit exactly this error -->



    Thanks

    kind regards

    Ahmed

    I did the following simple test.


    * Connect sd-card in Micro-slot on the development card. When checking the active slot on u-boot console

    Code
    1. mmc dev 0
    2. --> Card did not respond to voltage select!
    3. mmc dev 1
    4. --> switch to partitions #0, OK
    5. mmc1 is current device


    * Connect sd-card in Macro-slot on the development board. Then checking the active slot on u-boot console


    Code
    1. mmc dev 0
    2. --> No thing is showed on the console
    3. mmc dev 1
    4. --> MMC: no card present


    Please can you confirm if this is correct ?


    Thanks

    Ahmed

    Hi everyone,


    I have efusA7Ul-V1-Lin module which supports 2 sd-cards. I can very well boot my image from Macro-sdcard but not from Micro sd-card. I do the following:


    1- I change only 3 u-boot environment variables to boot from Macro sd-card as follows:


    Code
    1. setenv kernel ${.kernel_mmc}
    2. setenv fdt ${.fdt_mmc}
    3. setenv rootfs ${.rootfs_mmc}
    4. saveenv

    doing so is not enough to get the image to boot from (Macro sd-card slot). I have to change "rootfs" after performing the steps above from "root=/dev/mmcblk0p2 rootwait" to "root=/dev/mmcblk1p2 rootwait", I must change "rootfs" to


    Code
    1. setenv rootfs 'root=/dev/mmcblk1p2 rootwait'
    2. saveenv

    When kernel boots, I can see that Macro sd-card is read as slot 1 on the development board.


    Code
    1. This line is from kernel logs--->
    2. mmcblk1: mmc1:1234 SA04G 3.63 GiB
    3. mmcblk1: p1 p2 p3 p4

    Till now it is ok. If I insert the sd-card in (Micro sd-card slot) on the development board and try to perform the same trick as in step 1 above, the image does not boot at all.


    is slot 0 meant for Micro sd-card?


    Please any idea how can I get an image written on an sd-card to boot from Micro sd-card on the efus-development board ? what needs to be correctly changed in u-boot environment variables or do i have to recompile the kernel image to enable the recognition of 2 sd-cards?


    Thanks alot.

    Ahmed

    Thanks for your respond. I will tell the steps that I perform to use MfgTool:


    1- I downloaded "nbootimx6ul_31.zip" from the F&S DownloadArea

    2- Inside MfgTool folder I renamed the extracted file from "nbootimx6ul_31.bin" to "nboot.bin"

    3- I reviewed the content of ucl2 XML file, here is my content -->

    I am not sure if dev=MX6Q is correct for imx6Ul ?


    4- I attached imx6Ul module on the development board and plugged the USB-Macro cable in the board and in my PC. Then I started MfgTool2.exe, however I can not detect the board.


    Please do I miss any steps or you do have modifications ?


    Thanks

    Kind regards

    I deleted the Nboot accidentally on efusA9 module. I remember that I did the following:


    * Entered the Nboot console from the DCUTermi ( shift + s and click reset button on the development board)

    * Erased nand (shift + E) and clicked 'd' which will wait for the "uBoot" to be pushed on the module

    * Instead of writting uBoot and selected nboot.bin and it was written !!


    After that I could not get any response from the module. The only solution was using MFgTool to re-download the "nboot.bin" on the efusA9 module, then it worked again.

    When I was trying to do the same for efusA7Ull, the module does not show anything on any of the serial ports. The voltage pins on the development board is in order and no problems.


    The 2 leds which shall toggle on the module if there is no "uBoot" installed on the NAND flash do not toggle as well.


    Thanks

    Kind regards

    Hi everyone,


    I have been using 7ull module for long time but this is the first time I face this problem. I know when there is no nboot installed on the module and when I click on the reset button on the development board, then I can see on DCUTerminal <0> is printed.


    I have tested this before, I once removed nboot mistakenly on efusA9 module and i was able to retrieve it when I downloaded the MfgTool and i flashed a new one again. This time the module does not show anything when I connect it to the DCUtermi and it does not even print a <0> when I click on the reset button of the development board.


    Please do you have any way or suggestions to test if the module still functional?


    Thanks

    kind regards

    Ahmed

    Hi Everyone,


    I am testing a 3.5" display with efusA7Ull. The display should be compatible with your 3.5" display, here you please can have a look on the LCD. We are using touch controller SX8675 as SX8655 is obsolete but it should give the same result as stated from your note.


    I did the following:


    1- Build yocto image "fus-image-qt5" with modifying efusa7Ul.dts file in kernel, only this part to use for 3.5" display.



    I added some packages to IMAGE_INSTALL in fus-image-qt5 receipe such as tslib, tslib-calibrate and so on. So that was all my modifications in yocto


    2- I flashed the output sdcard image on the emmc on the efusA7ULL module and booted from the emmc.


    Result: The LCD worked and I was able run a qt application with the 3.5" correct resolution. To well describe my issue I used a qt app which is a combination of buttons when any button is clicked, then it simply counts a number inside this button. The problem is that most of buttons at the edges do not respond when they are touched. Only buttons almost in the middle work, outside the middle area do not respond. I thought it may be calibration problem so I used "ts_calibrate" but no gain. Here is a photo for the screen.


    These are my qt environment variables:


    Code
    1. export QT_QPA_PLATFORM=linuxfb:fb=/dev/fb0
    2. export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=/dev/input/touchscreen0:rotate=180
    3. export QT_QPA_FB_TSLIB=1
    4. export TSLIB_FBDEVICE=/dev/fb0
    5. export TSLIB_TSDEVICE=/dev/input/touchscreen0



    Please what could be the reason for this issue ? is it a miss configuration in the kernel for my LCD as described in step 1 ? what will be the correct configuration in case I use your 3.5" display ? Please any help is greatly appreciated.


    Last to mention that, when I build the yocto image without any modifications and flash it to the emmc, then the application works perfectly after "ts_calibrate" on your 7 inch display that comes with your SDK kit.


    Thanks in advance
    Ahmed

    Hi everyone,


    the current working yocto releases for some of f&s platforms such as efusA9 and efus7ull works with sysVinit (system V) which is not actually suitable for our requirement. I took Y0.6 version as an example and tried to remove sysVinit from it by adding in the local configuration file local.conf


    Code
    1. DISTRO_FEATURES_append = " systemd"
    2. VIRTUAL-RUNTIME_init_manager = "systemd"
    3. DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
    4. VIRTUAL-RUNTIME_initscripts = ""


    This should uses systemd and removes sysVinit when starting the services. It builds, outputs the final image and apparentlly it uses systemd to start the services. However I can not login ? when I enter the "root" as a login username, the console hangs and does not show anything, then after some seconds it prompots me to login again. I could not understand this behaviour. Note please that I have not changed any thing in the yocto sources except adding the last lines to my local.conf which I think it actually removes sysVinit.


    Please what is the correct way in order to backfall sysVinit in yocto and use sysemd instead?


    Thanks
    kind regards

    Hi everyone,


    I have the 7ULL module and I made some tests with the new yocto release Y1.0 specially with CAN interface. I didn't build the yocto from source but I directly tested the f&s compiled version in "binaries" folder after I extracted "fsimx6ul-Y1.0.tar.bz2"


    In this "binaries" folder there are many files, I copied them to FAT formated USB stick and only renamed the following files so that the names match the environement variables that will be set by the install.scr file.


    * uImage-fsimx6ul-Y1.0 --> uImage-fsimx6ul
    * install-fsimx6ul-Y1.0.scr --> install.scr
    * fus-image-std-x11-fsimx6ul-Y1.0.ubifs --> rootfs-fsimx6ul.ubifs
    * efusa7ull-Y1.0.dtb --> efusa7ull.dtb


    I erased the nand flash on the 7Ull module and installed new uboot version from the same "binaries" folder, exactly this one "uboot-fsimx6ul-Y1.0.nb0". After that I inserted the USB stick on the development boad then it started writing the ubifs to the nand and I can login normally.


    I brought CAN0 interface up using "ip link set can0 up type can bitrate 125000" then I used PCAN adapter to test the communication between the development board and the adapter.


    1- Transmission from PC over PCAN adapter to the development board:
    running the following on the serial console on the development board receives all messages correctly when they sent from the PC side.

    Code
    1. candump can0


    2- Transmission from development board to PC over PCAN adapter
    when sending this frame from the development board over the CAN bus using -->

    Code
    1. cansend can0 456#43414e2054657374


    it will not be correctly received on the PC side in the PCAN View window. !!


    PLEASE note when I perform the same test exactly as in 1 and 2 for those binaries of the buildroot method, then this problem does not show up again. This leaves no doubt that the CAN drivers used in yocto sources are somehow different from that of buildroot method.


    I attached also a photo of the received frame on the PCAN view whe transmitted from the development board.


    Thanks
    Kind regards

    Thanks again!
    I was actually trying to use an over the air updater called Mender on the efusA9 platform. The updater has yocto layer called meta-mender. I tried to integrate it with your new release of yocto [meta-fus (ver 0.6)], which actually took quite time but it worked at final. It would be much easier to use U-boot 2016 when integrating. Mender updater has some patches to the u-boot which adds its own environment variables to it to allow the update and roll back feature. As you mentioned Kconfig is replaced by Makefile.autoconf in newly u-boot versions, which required to remodify the patches and modify them locally in meta-mender to fit u-boot 2014 from efus.


    I think it will be easier in the integration process when u-boot 2016 is used and I thought you might have a new version from u-boot which may come out soon and we can use it. Besides the current u-boot version is getting older and a new version is preferable :)


    I may have a little sugesstion that it would be actually great to provide something like this mender updater when launching new release of yocto for all the efus boards. It is actually adds high value to the board and allows many for performing a way to update the controllers remotely.


    kind regards,