rebooting netDCU6 by sw doesnt launch start-app

    hello,


    that question was already asked a few month ago, but wasnt really solved.
    i can reboot the entire netDCU6 by software calling KernelIO or creating a new process calling ndcucfg in batch-mode executing reboot hardware. the netDCU gets rebooted, but the startapplication referenced in the init-section of the registry doesnt get called. bootloader starts up and ndcucfg is run as well, only my app doesnt get started. if i reboot the board by disconnecting/reconnecting power supply it starts up without any problems?!
    does anybody know the reason why?


    thanks
    cu andreas

    If ndcucfg is started, this shows that the files of registry key "init" are in fact executed. Therefore I see no reason why your application should not be started, too.


    I assume that you have not given all required depend entries for your software. For example if your software uses graphic features (as most of the programs do), you have to give a depend entry for gwes. Maybe your application starts quicker when doing a reboot than when doing a cold start, and then gwes is not yet up and running and your first attempt to use graphic features (like creating your application window) will fail and your application crashes and stops execution. This looks like as if your application was not started at all. But in fact it was started, but failed.


    Try this: give your application the highest number of all launched programs. Give it a depend entry for all other (earlier) programs in init. Then try again. I bet that your application will start correctly now, even on reboot.


    Regards,


    H. Keller

    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.

    thanks for the help!
    perhaps you are right, but i really thought it would start up till i can display the taskmanager by a tip on the display.
    but by now i can reboot the netDCU6 with KernelIO or ndcuterm (in terminal mode) and my display stays dark. no communication on rs232 or via telnet. i have to to a cold start and everythig works fine?!


    do you have one idea left?
    thx
    cu andreas

    Well, probably the initialisation of the display is done in the boot monitor, not in windows (see commands XDI and XDE in boot loader EBoot). A restart probably only restarts windows, but does not repeat the initialisation steps of the boot loader. Therefore the display remains dark.


    Regards,


    H. Keller

    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,


    thanks for info. my rebooting problem is quite strange...
    i have ploted the output of the bootloader:
    after i execute the reboot command in my app...


    SENDING command id 0x0001 to CDialog target.
    NDCUCFG V: 021 started. Platform: NetDCU6
    Rebooting .<66><71><1>


    Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built Jun 13 2005 12:21:50
    Size of SDRAM memory: 32 MB
    Windows CE Bootloader for AMD Alchemy Built May 16 2007 at 12:35:08
    Portions copyright (c) 2004 F&S Elektronik Systeme GmbH
    Boot Loader, Version 1.12
    CPU running at 396000000 Hz
    Size of SDRAM memory: 32 MB
    BOOT FLASH: SST DEVCODE: 39VF040
    T: InitFlash ... Complete!
    FindRegistryValue: using registry 2
    System ready!
    Preparing for download...
    Press >S< to step into monitor...
    AUTO BOOT enabled
    Checking to see if a Windows CE image has been previously flashed...done
    Copying kernel from Flash to 0xA1300000, size 5884668, sectors 11494
    Kernel read from flash disk started ......ERROR: d line 137: FMD: bad data at sector 0. No corrections are done.
    ..ERROR: d line 137: FMD: bad data at sector 8. No corrections are done.


    ...some more bad data sectors...


    .. finished in 3264 milliseconds
    Kernel decompression started .............................................. finished in 490 milliseconds
    Found pTOC signature.
    Launching image at 80004004h...
    OEMCheckSignature: start= 0x0, offset= 0x0, launch= 0x0, downloaded= 0x0
    ---------------------------------
    ROMHDR Info (pTOC = 0x808E13A0)
    ---------------------------------
    dllfirst = 0x01E901E9, dlllast = 0x02000000
    physfirst = 0x80004000, physlast = 0x808E2870
    nummods = 0x00000080
    ulRAMStart = 0x808E3000, ulRAMFree = 0x8090A000, ulRAMEnd = 0x81DD4000
    ulCopyEntries = 0x00000001, ulCopyOffset = 0x806E7FA8
    ulProfileLen = 0x00000000, ulProfileOffset = 0x00000000
    numfiles = 0x00000029
    ulKernelFlags = 0x00000000, ulFSRamPercent = 0x80808080
    ulDrivglobStart = 0x00000000, ulDrivglobLen = 0x00000000
    usCPUType = 0x0166, usMiscFlags = 0x0000
    pExtensions = 0x80005E68
    ulTrackingStart = 0x00000000, ulTrackingLen = 0x00000000-
    -------------------------------
    OEMLaunch: Start 0x00000000 Length 0x00000000 Launch 0x00000000 Header 00000000
    Jumping to image at 0x80004004...


    it cant read the kernel any more?!
    and why it wanted to use registry 2?


    cu andreas

    As the messages imply, there is a problem with an inconsistent file system. Have you already tried a full flash erase (command 'E' in EBoot) and a new download of the kernel and your application?


    Regards,


    H. Keller

    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.