This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Build Error Matlab

Other Parts Discussed in Thread: CCSTUDIO, TI-CGT, TMS320F28335

Hey,

While trying to build the following model in matlab2016a, CCStudio v6  I get the following error. 

=== Build (Elapsed: 18 sec) ===
    ### Starting build procedure for model: c280x_2833x_adcpwmasynctest_ert
    ### Generating code into build folder: E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw
    ### Invoking Target Language Compiler on c280x_2833x_adcpwmasynctest_ert.rtw
    ### Using System Target File: C:\Program Files\rtw\c\ert\ert.tlc
    ### Loading TLC function libraries
    Warning:  The data type "int8" uses a word size that is not available on the intended target.
        Fixed-point signals using this data type will be put inside a larger word or multi words.  When used,
    extra software will be generated to force this larger word or multi words to emulate a smaller
    word.  This emulation is helpful when your prototype target and your final
    production target are not the same.  If the smaller word size does NOT exist
    on the final production target, then consider increasing the word size to
    one that is supported.
    .
    Warning:  The data type "uint8" uses a word size that is not available on the intended target.
    Warning:  The data type "boolean" uses a word size that is not available on the intended target.
    .
    ### Initial pass through model to cache user defined code
    .
    ### Caching model source code
    ### Writing header file c280x_2833x_adcpwmasynctest_ert.h
    ### Writing header file c280x_2833x_adcpwmasynctest_ert_types.h
    ### Writing header file rtwtypes.h
    .
    ### Writing source file c280x_2833x_adcpwmasynctest_ert.c
    ### Writing header file c280x_2833x_adcpwmasynctest_ert_private.h
    ### Writing source file c280x_2833x_adcpwmasynctest_ert_data.c
    ### Writing header file rtmodel.h
    .
    ### Writing source file ert_main.c
    ### TLC code generation complete.
    ### Creating project marker file: rtw_proj.tmw
    ### Evaluating PostCodeGenCommand specified in the model
    ### Using toolchain: Texas Instruments C2000 Code Generation Tools v5.2.12 | gmake (64-bit Windows)
    ### Creating 'E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw\c280x_2833x_adcpwmasynctest_ert.mk' ...
    ### Building 'c280x_2833x_adcpwmasynctest_ert': C:\PROGRA~1\bin\win64\gmake -B -f c280x_2833x_adcpwmasynctest_ert.mk all
     
    E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw>cd .  
     
    E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw>if "" == "" (C:\PROGRA~1\bin\win64\gmake -B -f c280x_2833x_adcpwmasynctest_ert.mk all )  else (C:\PROGRA~1\bin\win64\gmake -B -f c280x_2833x_adcpwmasynctest_ert.mk  )  
    C:/ti/ccsv6/tools/compiler/C2000_~1.LTS/bin/cl2000 --compile_only --large_memory_model --cla_support=cla0 --silicon_version=28 --define="LARGE_MODEL" -i"/~SupportFiles/DSP280x_headers" -i"/~SupportFiles/DSP280x_headers/include" -i"C:/ti/ccsv6/tools/compiler/C2000_~1.LTS/include" -v28 --float_support=fpu32 -ml -DMODEL=c280x_2833x_adcpwmasynctest_ert -DNUMST=1 -DNCSTATES=0 -DHAVESTDIO -DONESTEPFCN=1 -DTERMFCN=1 -DMAT_FILE=0 -DMULTI_INSTANCE_CODE=0 -DINTEGER_CODE=0 -DMT=0 -DCLASSIC_INTERFACE=0 -DALLOCATIONFCN=0 -DTID01EQ=0 -D__MW_TARGET_USE_HARDWARE_RESOURCES_H__ -DRT -DSTACK_SIZE=64 -DONESTEPFCN=1 -DTERMFCN=1 -DMAT_FILE=0 -DMULTI_INSTANCE_CODE=0 -DINTEGER_CODE=0 -DMT=0 -DCLASSIC_INTERFACE=0 -DALLOCATIONFCN=0 -DTID01EQ=0 -DRT -DSTACK_SIZE=64 -DMODEL=c280x_2833x_adcpwmasynctest_ert -DNUMST=1 -DNCSTATES=0 -DHAVESTDIO -IE:/Sem 3/Main Project/Step 5 - VCSVPWM Hardware/c280x_2833x_adcpwmasynctest_ert_ert_rtw -IE:/Sem 3/Main Project/Step 5 - VCSVPWM Hardware -IC:/MATLAB/SupportPackages/R2016a/toolbox/target/supportpackages/tic2000/tic2000examples -IC:/PROGRA~1/extern/include -IC:/PROGRA~1/simulink/include -IC:/PROGRA~1/rtw/c/src -IC:/PROGRA~1/rtw/c/src/ext_mode/common -IC:/PROGRA~1/rtw/c/ert -IC:/MATLAB/SupportPackages/R2016a/toolbox/target/supportpackages/tic2000/inc -IC:/PROGRA~1/toolbox/shared/can/src/scanutil -IC:/MATLAB/SupportPackages/R2016a/toolbox/target/supportpackages/tic2000/src -IC:/PROGRA~1/toolbox/target/extensions/processor/tic2000/include -IC:/PROGRA~1/toolbox/rtw/targets/common/can/blocks/tlc_c --output_file="MW_c28xx_board.obj" "MW_c28xx_board.c"
    [Main.] 
    >> WARNING: more than one source file is specified; option --output_file is ignored
    Fatal error: cannot open source file "3/Main" 
    1 catastrophic error detected in the compilation of "3/Main". 
    Compilation terminated. 
     
    >> Compilation failure 
    gmake: *** [MW_c28xx_board.obj] Error 1 
     
    E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw>echo The make command returned an error of 2  
    The make command returned an error of 2 
     
    E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware\c280x_2833x_adcpwmasynctest_ert_ert_rtw>An_error_occurred_during_the_call_to_make 
    'An_error_occurred_during_the_call_to_make' is not recognized as an internal or external command, 
    operable program or batch file.
    ### Creating HTML report file c280x_2833x_adcpwmasynctest_ert_codegen_rpt.html
    ### Build procedure for model: 'c280x_2833x_adcpwmasynctest_ert' aborted due to an error.
    Error: Error(s) encountered while building "c280x_2833x_adcpwmasynctest_ert":
    ### Failed to generate all binary outputs.

Please provide information on how to get rid of this error. 

Regards,

Lakshmi.

  • Lakshmi,

    Someone from the MathWorks may be better able to help you.

    When I look at the build command I see some include paths that include spaces but are not enclosed in quotes:

    -IE:/Sem 3/Main Project/Step 5 - VCSVPWM Hardware/c280x_2833x_adcpwmasynctest_ert_ert_rtw
    -IE:/Sem 3/Main Project/Step 5 - VCSVPWM Hardware

    If Matlab is passing the command to the compiler like that I could see it causing problems.

    Regards,
    John
  • Hi Lakshmi,

    I think John might be correct with his assessment, but I'll also ask my development team.

    You can contact MathWorks Technical Support directly; they don't monitor these TI forums.

    -Brian

  • Hi Lakshmi,

    Heard back from my development team - this is a bug on our side.

    The build folder in which you are trying to build the model is a different file system, and we are not handling the spaces in the path correctly. We transforming all paths with spaces to an alternate path name, but this does not work on all file systems, and it is failing on your build file system.

    From the error message it looks like MATLAB installation folder is transformed properly(C:/PROGRA~1)

    But the build folder E:\Sem 3\Main Project\Step 5 - VCSVPWM Hardware is not transformed properly.

    There are few workarounds you can try:

    1. Use folder without spaces as build directory.
    2. Use a different drive with different file format. (For example C drive)
    3. As mentioned in this bug report, create mapped drive for the build folder.
    4. If file system is NTFS, try the last workaround mentioned in the bug report above from #3 above

    If you have trouble with these workarounds, please contact MathWorks Tech Support for better assistance.

    -Brian

  • Brian,

    Thanks a lot. The 4th workaround helped.

    -Lakshmi
  • hello sir

    i am using F28335,CCCv6 with compiler version 6.4.6,MATLAB 2016a. While simulation my model on dspF28335 kit i am getting an error.

    ------------------------------------------------------

    Warning: The data type "int8" uses a word size that is not available on the intended target.
    Fixed-point signals using this data type will be put inside a larger word or multi words. When used,
    extra software will be generated to force this larger word or multi words to emulate a smaller
    word. This emulation is helpful when your prototype target and your final
    production target are not the same. If the smaller word size does NOT exist
    on the final production target, then consider increasing the word size to
    one that is supported.
    Warning: The data type "uint8" uses a word size that is not available on the intended target.
    Warning: The data type "boolean" uses a word size that is not available on the intended target.
    Warning: The data type "ufix1" uses a word size that is not available on the intended target.
    C:/ti/ccsv6/tools/compiler/TI-CGT~1.6/bin/cl2000 --compile_only --large_memory_model --cla_support=cla0 --silicon_version=28 --define="LARGE_MODEL" -i"/~SupportFiles/DSP280x_headers" -i"/~SupportFiles/DSP280x_headers/include" -i"C:/ti/ccsv6/tools/compiler/TI-CGT~1.6/include" -v28 --float_support=fpu32 -ml -DMODEL=arduino_exp_two_level -DNUMST=2 -DNCSTATES=0 -DHAVESTDIO -DONESTEPFCN=1 -DTERMFCN=1 -DMAT_FILE=0 -DMULTI_INSTANCE_CODE=0 -DINTEGER_CODE=0 -DMT=0 -DCLASSIC_INTERFACE=0 -DALLOCATIONFCN=0 -DTID01EQ=0 -D__MW_TARGET_USE_HARDWARE_RESOURCES_H__ -DRT -DSTACK_SIZE=512 -DONESTEPFCN=1 -DTERMFCN=1 -DMAT_FILE=0 -DMULTI_INSTANCE_CODE=0 -DINTEGER_CODE=0 -DMT=0 -DCLASSIC_INTERFACE=0 -DALLOCATIONFCN=0 -DTID01EQ=0 -DRT -DSTACK_SIZE=512 -DMODEL=arduino_exp_two_level -DNUMST=2 -DNCSTATES=0 -DHAVESTDIO -IC:/PROGRA~1/MATLAB/R2016a/simulink/include/sf_runtime -IC:/Users/satwant/Documents/MATLAB/arduino_exp_two_level_ert_rtw -IC:/Users/satwant/Documents/MATLAB -IF:/ieee paper Z source converterS/MATLAB WORK/PAPER_2_SEQUENCES_TWO_LEVEL -IC:/PROGRA~1/MATLAB/R2016a/extern/include -IC:/PROGRA~1/MATLAB/R2016a/simulink/include -IC:/PROGRA~1/MATLAB/R2016a/rtw/c/src -IC:/PROGRA~1/MATLAB/R2016a/rtw/c/src/ext_mode/common -IC:/PROGRA~1/MATLAB/R2016a/rtw/c/ert -IC:/MATLAB/SupportPackages/R2016a/toolbox/target/supportpackages/tic2000/inc -IC:/PROGRA~1/MATLAB/R2016a/toolbox/shared/can/src/scanutil -IC:/MATLAB/SupportPackages/R2016a/toolbox/target/supportpackages/tic2000/src -IC:/PROGRA~1/MATLAB/R2016a/toolbox/target/extensions/processor/tic2000/include -IC:/PROGRA~1/MATLAB/R2016a/toolbox/rtw/targets/common/can/blocks/tlc_c --output_file="MW_c28xx_board.obj" "MW_c28xx_board.c"
    [paper.]
    >> WARNING: more than one source file is specified; option --output_file is ignored
    Fatal error: cannot open source file "paper"
    1 catastrophic error detected in the compilation of "paper".
    Compilation terminated.

    ----------------------------------------------

    Please provide any suggestion.

    Thanks

  • Hi,

    I can't really tell what the issue is. I can say you have multiple warnings about data types in your model that don't exist on your device - so that may be a factor.

    I also suspect you have a directory "ieee paper Z source" which has spaces and not being correctly interpreted by the compiler call. I'd try converting that to "ieee_paper_Z_source" and try building again.

    You can contact  MathWorks Technical Support for additional assistance.

    -Brian

  • sir

    deploy was successfull when i moved my model into default MATLAB folder present in C drive.

    Thanks

  • sir i want to now the minimum sample time that F28335 can support.
    Can i use 2e-6.
    Thanks
  • Impossible to answer your question - depends on your model and IO requirements. You need to explore and test for your specific application.

    I know we have a simple power system demo with minimal IO running @200kHz right now (saw demo running on F28377S LaunchPad this morning)

    -Brian

  • sir
    i am using tms320f28335 experimental kit for real time implementation of MATLAB simulink model.
    build, load and run is successful.
    But the problem is :

    output, as we see in the scope of simulink model is not accurate as that of DSO (digital signal oscilloscope).
    I mean the output at the pins of experimantal board is not same as that of scope of simulink model.

    Actually the time resolution is not same

    waveform of pulses that came in 0.02 sec in simulink scope is actually coming in more that 5 sec on the DSO.

    I think dsp processor is taking long time to run the model. In this case real time implementation is not possible.

    Please suggest, what can be done

    Thanks
    satwant