Posts by Mike

    >>Assume you should see the DBs it in the explorer as file (*.vol). Did you try it? Threr are not much files and filder under "Documents and settings".

    <<Ah this is where I went wrong. i was expecting a file in the line of .cedb or otherwise. Yes a .vol file exists and I can check its size.

    I can also see that the exe does reduce the size of the file. But it seems like the call of "CeFlushDBVol" is indeed needed. Since a restart pretty much removes all changes.

    Is there a possibillity that you can forward me the old project of the CEDB_cleaner (if it still exists)? Since I am currently struggeling to get my own project with the mentioned change up and running. (As I have already mentioned, I am not really versed in c++ development)

    Worst case scenario, we need to add the cleaner to the Launch options of our devices to clear the db on start. (But I would really like to keep the changes after a restart)

    Thanks for the help

    >>Yes but is does not check and delete it is only done for DB notify.

    <<Are there any potential problems, that lead to the way this was done in the sample? Are there any averse effects if we delete duplicates from the other DBs?

    >>The DBs are located under ffsdisk\documents and setting with file attribute hidden (as far as i remenber).

    <<Should I be able to see these files if i set the Folder options to display hidden files and folders?

    >>If you run the sample application after each reboot and nothing grows after serveral reboots to empty DB notify should be enought.

    <<How am I able to check the directory size on winCe? Or do I need a winCe pro kernel for that?

    Thank you for your help

    Doesn't the sample check through data bases until it does not find any new ones? Or am I missinterpreting the code? I am not so experienced in c++ programming.

    Is there the possibilty to check the CEDBs from the devices explorer itself, or code only?

    Yes, all our software was made in .NET, CF2 and CF3.

    My first tests definitly result in duplicate entries that are removed by your exe.

    The interessting part is that we have not only duplicates of "repllog.exe" but also "TouchCalibrate.exe".

    Why TouchCalibrate would be called during the startup, I honestly cannot tell.

    Ok, thanks for the info, I will run some tests with the exe provided.

    Another question regarding this problem:

    As I have already stated, a registry erase also fixes the problem.

    Are the CEDB entries or files also removed, when I call "reg erase"?

    Or is there a possibillity that there are registry entries that also lead to this problem?

    best regards

    Good day,

    we have a problem with our WCE6 devices (PicoMOD7A and NetDCU8) and connection via ActiveSync (Windows Mobile Device Center).

    We are accessing the device data of older devices, at site, via this method. (No ethernet connectivity configured. sadly.)

    The problem is that some devices, can not be connected to with ActiveSync. The WMDC just shows a connecting circle and does not proceed, or it shows a connected state for less than a second and terminates the connection instantly.

    The curious thing is that once we reset the registry the connection works flawlessly again. Reapplying our registry settings has no effect on the connectivity state. (The devices are also partially setup with ActiveSync during production)

    Sadly we cannot reapply the entire registry at site, for various reasons.

    The error seems to develope after a certain amount of device restarts. (Power off, power on)

    These restarts are over many years, without any USB- connections or otherwise.

    Do you know about any problems with WCE and ActiveSync that might lead to this?

    Are there any registry keys we might be able to check? (Since it seems like there is something, that goes wrong with the registry here)

    Best regards

    Good day,

    I have a question about the SD-card pins of the PicoMOD.

    Are the on board microSD and the SD-Card pins on the J1 connector, connected in any way?

    Or does the PicoMOD offer 2 SD-Card interfaces? One on-board and one to be wired to the connector?

    Best regards

    Good day,

    i had to reinstall one of the 64bit packages, but now the build is working as intended.

    The only problem now is that the root filesystem seems to exceed the maximum size, but I guess I should be able to tweak that to get a working system.

    Thanks for the help

    Good day,

    EDIT: I most likely applied the patch wrong. I will test a build and delete this post if that is the case.

    EDIT2: Ok I still have the same problem as discribed below.

    Currently, I am running tests on QT, but I have problems building the qt5webengine package in buildroot_B2019.08, while running on the F&S Development VM.

    I have added the toolchain fix referenced here: Build error of package QtWebEngine with new release fsimx6-B2019.08

    On the first try for make I got the following error:


    Your Buildroot configuration needs a compiler capable of building 32 bits binaries.

    If you're running a Debian/Ubuntu distribution, install the gcc-multilib package.

    For other distributions, refer to their documentation.

    make[1]: *** [support/dependencies/ dependencies] Error 1

    make: *** [Makefile:84: _all]

    I fixed this problem by installing the following packages: glibc-devel.i686 and libstdc++-devel.i686. Please tell me if these were a wrong options, since I am not quite sure those are correct for a PicoModA9.

    After installing these packages the build can start like expected, but I get the following error when the build reaches qt5webengine:

    I would be glad, if you could show me in the right direction to fix this problem.

    Best regards

    Thank, I appreciate the help.

    But are you sure the new reference card is the correct one? I am having a hard time seeing any differences to the old reference card.

    For example Pin 29 is still GPIO1_IO05 and /sys/class/gpio/gpio5.

    Or am I checking the wrong file? It should be under Documents --> PicoMODA9 - Linux yes?

    best regards


    thanks for the reply on the pullUps, I'll try that as soon is I am able to.

    As for the Pin29 (J1): No I tried GPIO 5 in Linux, in accordance with the Reference Card in the download directory for the PicoModA9.

    I am gonna try pin 49 ASAP.

    Best regards

    Good day,

    after some tests with the GPIOs I have also noticed that trying to export GPIO5 (Pin29 J1 connector) fails.

    For reference I also tried to export GPIO1, 0 and 2, which all work.

    The hardware documentation does not indictate that GPIO5 would be used for any other kind of hardware.

    The kernel that I used is the new fsimx6-B2019.08.

    Any ideas what I might be doing wrong? Might the GPIO be set for another hardware device in the device tree? (No changes where made, but configuring the display as LCD)

    best regards

    Good day,

    I have got a problem building the kernel with the new buildroot release for fsimx6.

    I am trying to add the midori webbrowser for tests, which leads to the inclusion of the WebkitGTK2.24.3 package.

    The problem is that it always fails at the step below.

    1. >>> webkitgtk 2.24.3 Patching
    2. Applying 0001-Build-failure-after-r243644-in-GTK-Li.patch using patch:
    3. patching file Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp
    4. Reversed (or previously applied) patch detected! Skipping patch.
    5. 1 out of 1 hunk ignored -- saving rejects to file Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp.rej
    6. package/ recipe for target '/home/developer/fsimx6-B2019.08/build/buildroot-2019.05.1-fsimx6-B2019.08/output/build/webkitgtk-2.24.3/.stamp_patched' failed
    7. make[1]: *** [/home/developer/fsimx6-B2019.08/build/buildroot-2019.05.1-fsimx6-B2019.08/output/build/webkitgtk-2.24.3/.stamp_patched] Error 1
    8. Makefile:84: recipe for target '_all' failed
    9. make: *** [_all] Error 2

    Any ideas how to fix this problem? With the old buildroot release midori and its dependend packages worked.

    best regards

    Good day,

    I am currently trying to add internal pullups to some of my GPIOs on the PicoMODA9.

    As far as I have gathered, the device tree seems the way to go.

    But how would I, for example set a pullup on GPIO1 (J1 connector, pin 41)?

    I did find a device tree example for the raspberryPI and internal pullups, but I am not putting much trust in an example for another board, when I have little understanding for how to work with the device tree itself.

    On that note are there some documents that further explain working with the device tree itself?

    best regards

    Good day,

    I recently started working with your linux distributions on a PicoMODA9 and have some questions:

    As far as I understand, Buildroot as well as Yocto use DeviceTrees to further configure the system.

    Where would I find the adjustable DeviceTrees for a Yocto-distribution? I have set up the yocto-files from the download area in accordance with the First Steps docu, but I seem to be unable to find any .dts files in the Yocto directory.

    Should one use the deviceTree files from the buildroot directories shipped with the F&S VirtualBox image, or am I just mistaken in the usage of deviceTrees in Yocto?

    Best regards

    Thats good to know.

    Since we are currently using the PicoMod7A, I'd like to ask if the StarterKit board for PM7A is compatible with a newer PMA9 or if I'd need to get a newer board for any tests?

    Best regards

    Good day,

    would the PicoModA9 be able to support dotNet Core? Or would this need some work from the side of F&S?

    I am asking since we are currently discussing about switching to Linux as operationg system, in the next project.

    Best regards

    As I have written above:


    the PicoMOD seems unable to access the USB and the SD-Card

    So currently I am not able to use either of the devices. Are there any other possibilities?

    I know that PicoMod7A is not recommended for new developments, I would only like to test some features before we start a development procedure.

    Like integration of DotNet Core for example.

    Best regards