none
wince6_imx35_build RRS feed

  • Question

  • Hi all,

    I got imx35 bsp from my client.The bsp was only osdesings folder and platform folder not any installer and all.

    I put these folders in the specific places and started to building .While I saw that in my solution explorer not showing the new bsp folder under platform.

    I copied one dirs file from another one bsp  to the new one.Then vs  was showing the new bsp platform in solution explorer.Nothing special in that dirs file.It was a simple code.

    After I started to build I got one build error as

    1:0000000025:ERRORE] E:\WINCE600\PLATFORM\nok\src\COMMON\ARGS\.\args.c(18) : fatal error C1083: Cannot open include file: 'bsp.h': No such file or directory.

    But in INC folder have this header file.But the pb not linking that to these files.

    I gone through many sites and experimented to solve this issue.But I could not solve it.

    So please help me to solve this.

    thanks...

    Monday, April 22, 2013 4:49 AM

Answers

  • Hi Rohith,

    Try by adding the following in your Sources file ,

       INCLUDES=$(INCLUDES); \
          $(_PLATFORMROOT)\nok\src\INC;

    If this will give some kind of error.Just check a other sources file of any other device.

    See how in your BSP they are adding the include path.

    With Thanks

    nadini

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:31 PM
    Monday, April 22, 2013 7:45 AM
  • The issue with your build is this :

    PB is not able to find bsp.h file. In your sources file you need to give link to this file.

    The reason it is not able to find the bsp.h file could be the path itself is incorrect or the macro which you are using "INCLUDES", "PLATFORMROOT" etc are not correctly set in sources.cmm.

    You can try giving the exact path under sources file and see it is able to find the bsp.h file

    This you can also try under your .c file as #include "E:\WINCE600\PLATFORM\nok\src\INC\bsp.h" (just an eg ...)

    Obviously the link suggested by Michel is worthy ...

    --- Misbah


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:31 PM
    Monday, April 22, 2013 8:40 AM
  • No, the sources.cmn is like a "master" sources file. Anything that is declared there is available in all sources files under your BSP root folder.

    The .cmn stands for "common", meaning the settings there are "common" for all sources. files in your BSP.

    So; no need to add the same INCLUDES macro to your specific components sources. files if that path is already in the sources.cmn.

    An example:

    sources.cmn:

    INCLUDES=$(_TARGETPLATROOT)\INC

    sources. of a component (driver) in your BSP:

    INCLUDES=$(INCLUDES);..\SDK\INC;

    So, this sources file redefines the INCLUDES statement but adds another relative path it needs (specific for this component).

    Another component might completely omit an INCLUDES macro in its sources. file. That component then still can access the files in $(_TARGETPLATROOT)\INC because it is defined in sources.cmn

    Think of sources files as simple DOS batch files where you set environment variables. The sources.cmn file is then simply a batch file that sets up a build environment by setting environment variables.
    Other batch files that run inside that build environment can redefine environment variables if required, or adding to it by "set includes=%includes%;anotherpath".

    I hope this clears it up.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:30 PM
    Tuesday, April 23, 2013 10:40 AM
    Moderator
  • Hi Michel,

    eu·re·ka  

    Lastly I did .

    I already mentioned in my starting question as I just copied the folders in its places.I mean platform, osdesings like.

    So In my platform folder bsp folder not have the sources.cmn file at all.Every time you were telling to check .cmn file I were checking in COMMON folder .So if I change also I could not solve the issue.

    Now what I did means I made one .cmn file for the new bsp and put it under the bsp folder.

    Now its building fine.

    Thanks alot Michel, nadini and misbah.

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:32 PM
    Tuesday, April 23, 2013 12:09 PM

All replies

  • Hi Rohith,

    Check in the Sources file for the Inlcude path of bsp.h file.

    The entry in sources file looks like,

    INCLUDES=$(INCLUDES); \
                   $(_PLATFORMROOT)\COMMON\SRC\SOC\$(_COMMONSOCDIR)\ASRC\INC;

    With Regards

    nadini

    Monday, April 22, 2013 5:14 AM
  • Check the sources. file and the sources.cmn file. It needs to set the INCLUDES to include your INC folder. It sounds like you've got a lot of reading to do in regards to building kernels with Platform Builder. That's ok, no problem, but I suggest getting a good book, read MSDN, maybe do a training, etc.

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Monday, April 22, 2013 5:15 AM
    Moderator
  • Hi Michel,

    Please suggest me any good book or sites for understand the basics of building kernels with pb.

    Thanks

    Monday, April 22, 2013 7:23 AM
  • HI nadini,

    Its not working for me.

    In my platform builder folder have Common and my bsp folder also.

    In common all are building fine.

    But in bsp folder making the errors.

    Actually the path of source is E:\WINCE600\PLATFORM\nok\src\COMMON\ARGS\args.c

    path of include file is E:\WINCE600\PLATFORM\nok\src\INC

    source file of ARGS is 

    TARGETNAME=args
    TARGETTYPE=LIBRARY

    RELEASETYPE=PLATFORM
    NOMIPS16CODE=1

    SOURCES=\
        args.c
    FILE_VIEW_INCLUDES_FOLDER= \

    RTTI=NO
    SAFESEH=1

    thanks

    Monday, April 22, 2013 7:36 AM
  • Hi Rohith,

    Try by adding the following in your Sources file ,

       INCLUDES=$(INCLUDES); \
          $(_PLATFORMROOT)\nok\src\INC;

    If this will give some kind of error.Just check a other sources file of any other device.

    See how in your BSP they are adding the include path.

    With Thanks

    nadini

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:31 PM
    Monday, April 22, 2013 7:45 AM
  • http://www.microsoft.com/windowsembedded/en-us/develop/windows-embedded-compact-7-development-books.aspx

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Monday, April 22, 2013 8:22 AM
    Moderator
  • The issue with your build is this :

    PB is not able to find bsp.h file. In your sources file you need to give link to this file.

    The reason it is not able to find the bsp.h file could be the path itself is incorrect or the macro which you are using "INCLUDES", "PLATFORMROOT" etc are not correctly set in sources.cmm.

    You can try giving the exact path under sources file and see it is able to find the bsp.h file

    This you can also try under your .c file as #include "E:\WINCE600\PLATFORM\nok\src\INC\bsp.h" (just an eg ...)

    Obviously the link suggested by Michel is worthy ...

    --- Misbah


    Senior Design Engineer T.E.S Electroni Solutions (Bangalore-India) www.tes-dst.com email-misbah.khan@tes-dst.com

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:31 PM
    Monday, April 22, 2013 8:40 AM
  • Hi nadini,

    I tried as you said.But now I am getting some other error.

    BUILD: [00:0000000005:PROGC ] Computing include file dependencies:
    BUILD: [00:0000000006:PROGC ] Checking for SDK include directory: E:\WINCE600\sdk\CE\inc.
    BUILD: [00:0000000007:PROGC ] Scan E:\WINCE600\PLATFORM\nok\src\COMMON\ARGS\
    BUILD: [00:0000000008:PROGC ] Saving E:\WINCE600\PLATFORM\nok\Build.dat.
    BUILD: [00:0000000011:PROGC ] Building COMPILE Pass in E:\WINCE600\PLATFORM\nok\src\COMMON\ARGS\ directory.
    BUILD: [01:0000000022:PROGC ] Compiling .\args.c
    BUILD: [01:0000000024:ERRORE] cl : Command line error D8004 : '/I' requires an argument
    BUILD: [00:0000000025:PROGC ]                        Files  Warnings  Errors
    BUILD: [00:0000000026:PROGC ] Midl                       0         0       0
    BUILD: [00:0000000027:PROGC ] Message                    0         0       0
    BUILD: [00:0000000028:PROGC ] Precomp Header             0         0       0
    BUILD: [00:0000000029:PROGC ] Resource                   0         0       0
    BUILD: [00:0000000030:PROGC ] MASM                       0         0       0
    BUILD: [00:0000000031:PROGC ] SHASM                      0         0       0
    BUILD: [00:0000000032:PROGC ] ARMASM                     0         0       0
    BUILD: [00:0000000033:PROGC ] MIPSASM                    0         0       0
    BUILD: [00:0000000034:PROGC ] C++                        0         0       0
    BUILD: [00:0000000035:PROGC ] C                          1         0       1
    BUILD: [00:0000000036:PROGC ] Static Libraries           0         0       0
    BUILD: [00:0000000037:PROGC ] Exe's                      0         0       0
    BUILD: [00:0000000038:PROGC ] Dll's                      0         0       0
    BUILD: [00:0000000039:PROGC ] Preprocess deffile         0         0       0
    BUILD: [00:0000000040:PROGC ] Resx                       0         0       0
    BUILD: [00:0000000041:PROGC ] CSharp Compile             0         0       0
    BUILD: [00:0000000042:PROGC ] Other                      0         0       1
    BUILD: [00:0000000043:PROGC ]
    BUILD: [00:0000000044:PROGC ] Total                      1         0       2
    BUILD: [00:0000000045:PROGC ]
    BUILD: [00:0000000046:PROGC ] 0 Warnings,  2 Errors
    BUILD: [00:0000000047:PROGC ] GetSystemTimes (seconds): Idle: 0     Kernel: 0     User: 0    
    BUILD: [00:0000000048:PROGC ] Elapsed  time  (seconds): 0    
    Build for Windows CE (Release 601) (Built on Aug 17 2006 15:18:52)
    File names: Build.log Build.wrn Build.err Build.dat
    E:\WINCE600\PLATFORM\nok\src\COMMON\ARGS\sources - 1 error(s), 0 warning(s)
    ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

    I am not getting which file is showing this error.From one site got an information that check the speces in the sources file.I checked and correct it.But still error persisting.

    please help me to solve this.

    thanks
    Tuesday, April 23, 2013 4:38 AM
  • Hi Rohith,

    The error is present in Sources file.

    Yes.Its related to spaces in the INCLUDE path that you have added in Sources file for the bsp.h.

    See the following posts you will get an idea to solve it,

    http://discovertheexperience.blogspot.in/2011/12/command-line-error-d8004-under-windows.html

    http://us.generation-nt.com/answer/aout-command-line-error-d8004-help-79449212.html

    Post the include path of bsp.h file that you have added in Souces file newely.It will help to give more information.

    With Regards

    nadini

    Tuesday, April 23, 2013 6:38 AM
  • Hi nadini,

    the path which I added in sources file is

    INCLUDES=$(INCLUDES);$(_TARGETPLATROOT)\SRC\INC;

    thanks
    Tuesday, April 23, 2013 6:53 AM
  • Hi Michel,

    Thanks for your  valuable suggestions.

    Let me know where I can get good training for understand the basics ?

    Tuesday, April 23, 2013 6:57 AM
  • The problem is that $(INCLUDES) is set to nothing, so you have:

    INCLUDES=;$(_TARGETPLATROOT)\SRC\INC;

    See the problem?

    The build system will now run the compiler with /I /I $(_TARGETPLATROOT)\SRC\INC

    The first (empty) /I is causing the problem.

    Put $(INCLUDES) at the end (or omit it).

    You should really be checking your sources.cmn file in the root of your BSP (as I said earlier). There's something wrong there that is causing all these problems.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Tuesday, April 23, 2013 6:59 AM
    Moderator
  • Hi Rohith,

    Try by adding as,

    INCLUDES=$(INCLUDES); \
          $(_TARGETPLATROOT)\SRC\INC;

    or

    INCLUDES=\
        $(INCLUDES); \
        $(_TARGETPLATROOT)\src\inc;

    With Regards

    nadini

    Tuesday, April 23, 2013 7:00 AM
  • That depends on your location. Several Microsoft partners offer anything from 1-day workshops to full 10 day trainings.

    You can try to find a partner that offers trainings on the microsoft partner network. For me I get to this page: http://www.microsoft.com/business/en-nz/support/pages/find-a-partner.aspx (New Zealand).

    For some strange reason GuruCE doesn't show up as partner there, but we are and also offer CE/EC training (in Europe and NZ).


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Tuesday, April 23, 2013 7:18 AM
    Moderator
  • sorry nadini,

    I tried the paths in sources file but still its showing the same error.

    Tuesday, April 23, 2013 8:44 AM
  • That's because Nadini's response doesn't make any sense (sorry Nadini).

    Have you looked at my response above?


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Tuesday, April 23, 2013 9:03 AM
    Moderator
  • Hi Michel,

    Yes I have seen.Thanks for the information I will try to get it more clearly.

    Sorry if I have made any mistake.

    Hi Rohith,

    Please check by seeing the Michel's response.

    With Regards

    nadini

    Tuesday, April 23, 2013 9:23 AM
  • HI michel,

    Is it need to add include file in both sources and sources.cmn file?

    Actually mine platform/common folder is building fine.The problem only with the new bsp folder in path of

    E:\WINCE600\PLATFORM\nok\

    thanks 

    rohith

    Tuesday, April 23, 2013 10:02 AM
  • No, the sources.cmn is like a "master" sources file. Anything that is declared there is available in all sources files under your BSP root folder.

    The .cmn stands for "common", meaning the settings there are "common" for all sources. files in your BSP.

    So; no need to add the same INCLUDES macro to your specific components sources. files if that path is already in the sources.cmn.

    An example:

    sources.cmn:

    INCLUDES=$(_TARGETPLATROOT)\INC

    sources. of a component (driver) in your BSP:

    INCLUDES=$(INCLUDES);..\SDK\INC;

    So, this sources file redefines the INCLUDES statement but adds another relative path it needs (specific for this component).

    Another component might completely omit an INCLUDES macro in its sources. file. That component then still can access the files in $(_TARGETPLATROOT)\INC because it is defined in sources.cmn

    Think of sources files as simple DOS batch files where you set environment variables. The sources.cmn file is then simply a batch file that sets up a build environment by setting environment variables.
    Other batch files that run inside that build environment can redefine environment variables if required, or adding to it by "set includes=%includes%;anotherpath".

    I hope this clears it up.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: http://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:30 PM
    Tuesday, April 23, 2013 10:40 AM
    Moderator
  • Hi Michel,

    eu·re·ka  

    Lastly I did .

    I already mentioned in my starting question as I just copied the folders in its places.I mean platform, osdesings like.

    So In my platform folder bsp folder not have the sources.cmn file at all.Every time you were telling to check .cmn file I were checking in COMMON folder .So if I change also I could not solve the issue.

    Now what I did means I made one .cmn file for the new bsp and put it under the bsp folder.

    Now its building fine.

    Thanks alot Michel, nadini and misbah.

    • Marked as answer by Rohith_88 Tuesday, April 23, 2013 12:32 PM
    Tuesday, April 23, 2013 12:09 PM