none
Smart device App crashes if almost any change is made to OS Design,Though its given new SDK RRS feed

  • Question

  • Hi

    I have cloned an existing Wec7+VS2008 host to maintain the OS design on another PC.

    After installing wec7 I overwrote new host wec7 folder with older host's wec7 folder.

    We are now seeing a strange behaviour in the new host, our App is happy to run with nk.bin and SDK from new host, but the App crashes if we make any change to new host OS design that is not in old host.

    example it was fine with changing screen calibration constants on new wec7 host

    But adding catalogue item or new registry entry and the App crashes almost immediately after loading on target, sometimes it would even cause target to reboot.

    For example adding the AutoLaunch and selecting it in catalogue, the App crashes on resulting nk.bin. untick the set catalogue item and all is fine.

    Same result with adding new registry key, like I did for init key with new launch entry, and same result. remove the entry and all is fine.

    That said a very simple window test app and explorer are all happy on target regardless of OS Design changes.

    Hence started updating SDK for almost any change in OS Design, but did not solve the problem.

    Any ideas on this

    Thanks

     


    • Edited by Jaskan Thursday, October 16, 2014 3:31 PM added more comments
    Thursday, October 16, 2014 3:29 PM

All replies

  • I don't know, what you see if very unusual so I have some questions:

    1. Are you saying that you can build an OS today that your app will run on?  Or are you saying that if you go back to your original OS that your app will run?
    2. What language is your app written in?
    3. What debug output happens when you run your app?
    4. How much program RAM is available?


    Bruce Eitman (eMVP) Senior Engineer Bruce.Eitman AT Eurotech DOT com My BLOG http://geekswithblogs.net/bruceeitman Eurotech Inc. www.Eurotech.com

    Friday, October 17, 2014 12:26 PM
    Moderator
  • Thanks for the feedback.

    [Q]Are you saying that you can build an OS today that your app will run on?  Or are you saying that if you go back to your original OS that your app will run?

    [A]We have an older machine with wec7, the app runs on nk.bin from that machine. Created ew wec7 install based on BSP from previous machine and the app crashes one in ten times almost immediately after start-up  

    [Q]What language is your app written in

    [Y] Win32 C/C++mostly C++

    [Q]What debug output happens when you run your app

    [Y]very good point,  Unfortunately I arrived on the scene to an App with pretty much no logging, but gona add that soon as we passed a pending demo.

    [Q]How much program RAM is available

    [Y]Will look into this.

    Also could this have anything to do with CE SDK used by the App , I mean do you have to generate new CE SDK for every nk.bin build.

    cheers

     

    Tuesday, October 21, 2014 10:10 AM
  • I asked if there is any debug output, you didn't answer that - you answered an entirely different (but similar) question.  I did not ask if you app has debug messages.  I asked what debug output occurs when you run your app.  The answer may be "none", but since you didn't say that I have to assume that you didn't answer.

    You should create a new SDK if the OSDesign changes because you added/removed OS features.  You do not need to create a new SDK if all you did was rebuild.

    Your new information is very important - more important than almost anything that you included in your original post.   It seems that your problem is related to poor configuration management, and not to adding/removing OS components.   Because of that, only you can figure out what you didn't do when you set up the new PC.


    Bruce Eitman (eMVP) Senior Engineer Bruce.Eitman AT Eurotech DOT com My BLOG http://geekswithblogs.net/bruceeitman Eurotech Inc. www.Eurotech.com

    Tuesday, October 21, 2014 1:15 PM
    Moderator
  • Hi

    Thanks for the detailed reply, but Wec7 is almost impossible to add to source control once its been built, cause then you get all the output files, and need to figure out which to delete before adding to source control. Still looking for good guide on preparing existing built  wec7 install for source control.

    Tried this on the old machine, and resulting image would not boot cause I must have deleted needed output file. Left all files in public/private etc focusing only on BSP and third party folders.

    Else wec7 with output files is about 230,000 files at about 37Gig

    As a result best option was a fresh CE install with BSP and third party folders copied over to new wec7, but add to source control before first build is what I been advised on here.

    [1] SDK

    Thanks very much for the reply on SDK. So is it the case then that I don't need to do new SDK for registry changes that are not related to add/remove features. For example adding launch command, updated driver/oal code etc.

    I mean is new SDK only required when new components added via catalogue or script. And not source code changes or registry changes.

    Thanks again

    Tuesday, October 21, 2014 1:52 PM