Posts by HWeber


    I changed the priority settings of serial 2 to 111 (adding Priority256=111). After that I rebooted the device and checked the NK.exe process and it's threads,
    bu I can't find any thread with a priority of 111. Does the entry not work or is it only the priority of the irq?
    Are there any other settings for the com ports, we lose some packages so is there a kernel buffer for the data which can be sized up?


    I tried to apply the RT patch to the current fsimx6-2.1 Kernel without success. There are too many changes between the vanilla and the kernel from F&S. Did somebody apply the patch successfully? I would be very happy if I don't need to do it by myself - if it is at all possible.

    Mkimage is a tool of uboot to create a correct kernel-image, I guess?!?!
    The update.scr file is an ascii file with commands for u-boot to flash files or change uboot variables. The file itself has a kind of checksum in its header and is followed by the commands. Maybe there are different mkimage programs?
    Uboot only checks the update.scr file and not any other file like the kernel or filesys image.

    We want to update efus boards in the field. Therefore we use the update.scr file the modified kernel and rootfs image an copy it on an USB stick. Everything is working fine with one issue. We also need to change the rootfs to rw and so we added a line with "run .mode_rw" to the update.scr file. At this moment the checksum of the update file is broken (in header) and the update doesn't work anymore.
    Is there a manual howto create a "signed" update.scr file?

    We have an issue, that we lose some data packages over the rs232 interface of the netdcu9. At the moment we are not sure where the packages are lost but we wonder how wince is handling rs232 data.

    The load on our system can raise up to 100% depending if something has to be drawn on the display or not. How is incoming data handled by wince? Is there any kernel thread which catches the data from rs232 and if yes, is it possible to change its priority?
    Is there also a kernel thread for sending the data or is it a blocking send?

    I want to format the emmc on my efus board with ext4 file system but there is no mkfs.ext4 command for that (only ext2 and vfat).
    As I can see the kernel supports ext4. I also tried the mke2fs command with parameter "-t ext4" but the command doesn't know this parameter.

    Do I need to adapt my busybox configuration? I didn't find any parameters so far....


    I use WCE6 and we want to install an additional executable on the system (NetDCU9). The installation should be as easy as possible.
    I remember of autorun.inf files in Win95 which automatically started programs on data CDs.

    Does WCE support an autorun.inf file which is copied to an USB-Stick?

    1. yes, use remote registry editor
    -> Select entry you wish to export (left side)
    -> Menu "Registry" -> "Export registry file...."
    2. do this for both device and make a diff with e.g. winmerge and copy the diff to a new file
    3. create an cab installer in VS08
    -> the .reg file can be imported in the VS08 installer registry editor

    I made some changes to the registry of our NetDCU9 WinCE board with the remote registry viewer. I want to transfer this settings to another NetDCU board.

    So I have the following questions:
    1. Is it possible to save the current registry
    2. make a diff between the current and the old registry
    3. only apply the diff to the other board

    I don't have any deep knowledge of the kernel but after some code research I found the following lines in drivers/net/fec.c:

    1. /* mask with MAC supported features */
    2. if (cpu_is_mx6q() || cpu_is_mx6dl())
    3. phy_dev->supported &= PHY_BASIC_FEATURES;
    4. else
    5. phy_dev->supported &= PHY_BASIC_FEATURES;

    I changed it to:

    1. /* mask with MAC supported features */
    2. if (cpu_is_mx6q() || cpu_is_mx6dl())
    3. //phy_dev->supported &= PHY_GBIT_FEATURES;
    4. phy_dev->supported &= PHY_BASIC_FEATURES;
    5. else
    6. phy_dev->supported &= PHY_BASIC_FEATURES;

    As I can see ethernet is now running on 100MBits. I don't think that this is a "good" solution so maybe you have a better idea.
    Both patches must be applied, if not, network is running on 100MBit but it has many RX errors and no connection can be established.

    Changing the location of the toolchain is not possible, that's true. We installed all the tools onto another partition (which is in the backup).
    The easiest solution for us was to set a symlink.

    ln -s /opt/toolchain/fs-toolchain-4.7.2-cortexa5-neonvfpv4 /usr/local/arm

    If this is not possible for you, you can also use mount with the "bind" option.