problem with kernel generated with platform builder vs2005

    dear,


    i create a run time image with platform builder (NK.bin) and i load it to the development board of picocom4 with success but when i restart the board i can see errors on DCUtermi windows and windows doesn't start



    I don't find what is wrong because the build is ok without error

    Hello
    - kernel debugger enabled?
    - disable KITL
    - did you built release or debug image? I would built a release.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    I rebuild with only kernel debugger enabled in build options in release mode but i have the same problem


    dcutermi log when i start the board


    Hi,


    unfortunatly PicoCOM4 BSP does not support ethernet debuggung. So you should leave KITL and Debugging option in platform builder deselected.


    Is your custom kernel image already stored in NAND flash?
    If so, does a prebuild kernel image still work properly with this board?


    Did you remove any features?
    Please verify that your OSDesign includes hive based registry support.

    Software developer, F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    so when i open the property pages of my project, in "configuration properties" -> "build options" what do i select? i unchecked already KITL, i deselect debugger option. Should i select " write run time image to flash memory"? or other?


    And with a f&s kernel image, the board works well but not with a kernel image created with a bsp provided by f&s.


    How do i implement the have registry because in the prj provided by f&s the hive doesn't appears in the "project.reg" file

    Hello,


    Built options: only enable IMGEBOOT=1
    Hive registry: is enabled by a catalog item, and should already be activated using the fs template project.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    i have these errors when open fs template project (no one with my own) PRJ_PicoCOM4_20120416:


    - SDK2.sdkcfg not found (not in the archive?)
    - bcsend.pbpxml not found
    -checkautostart.pbpxml not found
    -fs_usbdisk6.pbpxml not found
    -fs_usbmsfn.pbpxml not found
    -fs2dctrl.pbpxml not found
    -fsboardconfig.pbpxml not found
    -fsmixer.pbpxml not found
    -fspmscreensaver.pbpxml not found
    -ndcucfg.pbpxml not found
    -touch_edt.pbpxml not found


    But when i verify the directories i found all these files except the sdk file?

    this the makeimg.out result with errors::





    so no nk.bin generated with the f&s template files.



    the file fs-touch-edt.dll is really missing!

    Hello,


    do you really use edt capacitive touch? If yes, we will provide it later. For now just excuded it from build ... . In the first step we should create a working run time image. After you can make it perfect.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Hello,
    search for "fs_touch_edt" in the sources files. If this project is not available (i assume this), remove "fs_touch_edt.dll" from the *.bib file(s)!


    PS: Why you do not order a custom image? This would be a very fast and cheap solution!

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    no "fs_touch_edt.dll" file in your template!!!!


    so you provide templates that don't work? and i have to pay ONLY 600 euros (price given by a french distributor) to have one good.. sure it's cheap. You provide bsp so it's normal that i think it's possible with platform builder to use it to make my own image without problem.


    platform builder doesn't find (and directories don't exist)


    C:\WINCE600\PLATFORM\COMMON\SRC\NETDCU\USBFN directory
    &
    C:\WINCE600\PLATFORM\COMMON\SRC\NETDCU\touch directory


    it's a sdk installation problem? bsp problem? and i don't no why but it's impossible to remove these subprojects from the template project.

    Hello,
    i must admit that it is not elementary to deploy the BSP, but we assume that the custmer has experience with PB and enviroment! In genernal we do *NOT* support the BSP.
    Exclude all stuff refers:
    C:\WINCE600\PLATFORM\COMMON\SRC\NETDCU\USBFN directory
    C:\WINCE600\PLATFORM\COMMON\SRC\NETDCU\touch directory
    from work space, *.bib, ... . I suggest you do not need this files. Do you need edt touch?
    All basic binaries are included.


    The price for the custom kernel do not only include "one good"!!! You can order updates and small modifictions for free. You have also enough time for testing. And we fix and administer your configuration.

    F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.