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.

norflash-writer fails to build for c6a816x from PSP04.00.00.10 (tiezsdk_dm816x-evm_5_01_00_77)

Hi,

I have CCS5 and I can't get the norflash-writer to build.  I'm probably doing something wrong but I'm following the flash utils guide and not quite sure what to do.

In CCS5, I do Project->Import Existing CCS/CCE Eclipse Project.

I then browse to the nor-flash-writer directory that has the src.

CCS5 finds the project and asks if I want to convert it to a CCS4 project or something like that.

When the project is finished importing, in the Problems window I get the following:

Description    Resource    Path    Location    Type
Invalid project path: Include path not found (/home/hutch/workspace/inc).    norflash-writer        pathentry    Path Entry Problem
Invalid project path: Include path not found (/home/hutch/workspace/include).    norflash-writer        pathentry    Path Entry Problem
Invalid project path: Include path not found (/home/hutch/workspace/norflash-writer/Debug/C::\netra\psp\nor-flash-writer.tar\nor-flash-writer\inc).    norflash-writer        pathentry    Path Entry Problem
This project contains unresolved buildable linked resources. It might not build as expected.    norflash-writer        project    TI Problem Marker

If I do Project->Clean I see:

/usr/local/CCSv5/ccsv5/utils/gmake/gmake -k clean
subdir_rules.mk:6: *** target pattern contains no `%'.  Stop.

**** Build Finished ****

 

If I do Project->Build all I see:

**** Build of configuration Debug for project norflash-writer ****

/usr/local/CCSv5/ccsv5/utils/gmake/gmake -k all
subdir_rules.mk:6: *** target pattern contains no `%'.  Stop.

**** Build Finished ****

 

I kind of need to be able to build these flash utilities so I can edit them for our custom board.  Any ideas as to what to check are greatly appreciated.

Regards,

Brian

 

  • ... and what is the significance of using the tms420 cgtools vs the c6000 cgtools that came in the ezsdk?

    The flash document says to install tms420 cgtools and gives this URL which does not work:

    http://syntaxerror.dal.design.ti.com/release/releases/arm/rel4_6_2/build/install/ti_cgt_tms470_4.6.2_setup_linux_x86.bin

    When I look at the components already in my version of ccs5, the cgtools for tms420 looks like they are already installed so I'm not quite sure why the document is telling me to install tms420 cgtools.

    Regards,

     

    Brian

     

  • Update.   I went through the project making the paths right and now I am making it to the link stage.

    At first, this is the linker error that was displayed:

    <Linking>
    fatal error: object files have incompatible formats
      ("/usr/local/CCSv5/ccsv5/

    tools/compiler/tms470/lib/rts32earm9.lib<boot.obj>"
      = TI-COFF, "./util.obj" = ELF)

    Looks like COFF & ELF are being mixed???  In looking at the properties of the project ... in "CSS General" and I changed the "Output format:" to legacy COFF.

    Now when I build I see this link error:
    <Linking>
    warning: entry-point symbol other than "_c_int00" specified:  "mystartup"
    Finished building target: norflash-writer.out

    Not quite sure what to try next as I'm probably heading into the weeds.

    Regards,

    Brian

    .ps here is the build console output for reference:


    **** Build of configuration Debug for project norflash-writer ****

    /usr/local/CCSv5/ccsv5/utils/gmake/gmake -k all
    Building file: ../src/debug.c
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/debug.pp"  "../src/debug.c"
    Finished building: ../src/debug.c
     
    Building file: ../src/device.c
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/device.pp"  "../src/device.c"
    Finished building: ../src/device.c
     
    Building file: ../src/nor.c
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/nor.pp"  "../src/nor.c"
    Finished building: ../src/nor.c
     
    Building file: ../src/norwriter.c
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/norwriter.pp"  "../src/norwriter.c"
    Finished building: ../src/norwriter.c
     
    Building file: ../src/super_startup.asm
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/super_startup.pp"  "../src/super_startup.asm"
    Finished building: ../src/super_startup.asm
     
    Building file: ../src/util.c
    Invoking: TMS470 Compiler
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --include_path="/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" --include_path=/home/hutch/workspace/norflash-writer/inc --include_path="/usr/local/CCSv5/xdais_7_20_00_07/packages/ti/xdais" --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 --preproc_with_compile --preproc_dependency="src/util.pp"  "../src/util.c"
    Finished building: ../src/util.c
     
    Building target: norflash-writer.out
    Invoking: TMS470 Linker
    "/usr/local/CCSv5/ccsv5/tools/compiler/tms470/bin/cl470" -mv7A8 -g --define="_DEBUG" --define=USE_DDR_HEAP --define=CONFIG_TI816X --diag_warning=225 -me --abi=ti_arm9_abi --code_state=32 -z -m"norflash-writer.map" --warn_sections -i"/usr/local/CCSv5/ccsv5/tools/compiler/tms470/lib" -i"/usr/local/CCSv5/ccsv5/tools/compiler/tms470/include" -i"/home/hutch/workspace/norflash-writer" --reread_libs --entry_point=mystartup --rom_model -o "norflash-writer.out"  "./util.obj" "./super_startup.obj" "./norwriter.obj" "./nor.obj" "./device.obj" "./debug.obj" -l"rts32earm9.lib" -l"libc.a" "../linker.cmd"
    <Linking>
    warning: entry-point symbol other than "_c_int00" specified:  "mystartup"
    Finished building target: norflash-writer.out

  • Hutch, have you tried building it on Linux? Maybe not what you wanted to hear but you may have more luck there.

    Ralph

  • Hi Ralph,

    I am building it on Linux .... CCS5 for Linux (ver. 5.1.0.201104171800).  Were you meaning the TMS470 Compiler from the command line?  I haven't tried that yet.

    Specifically, I'm following:

    http://processors.wiki.ti.com/index.php/DM816x_C6A816x_AM389x_PSP_Flashing_Tools_Guide

    And I'm especially keying in on "Projects were verified on CCSV5 also" which is a direct quote from the above wiki page (and has been mentioned in every release of the ezsdk).

     

    Regards,

    Brian

     

     

  • Hi,

    I can't say I trust much of the documentation given how many mistakes I've seen so far. I have had some success building stuff on Linux _from the command line_. Maybe have a go at that, even though it says CCS should build them? How about trying CCS on Windows?

    Having said that, I had massive problems building the stuff on Windows CCS myself and as I recall I gave up on the whole exercise and now I'm using the pre-built binaries instead.

    I also had command line Linux building problems but if it helps at all my post on this issue which I solved is here:

    http://e2e.ti.com/support/dsp/integra_dsparm/f/625/p/89774/312244.aspx#312244

    When I used the command line I followed the flasher PDF in psp/docs/ I think.

    Ralph

  • TI guys ... where are you???

  • Hi Hutchman,

    Sorry for the delay and inconvenience. There seems to be some relative path issue in the NOR/SPI CCSv5 project. Also, we did not support Linux host build environment.

    The warning message "warning: entry-point symbol other than "_c_int00" specified:  "mystartup"" could be ignored. We are using a different entry point for NOR project to maintain ARM supervisor mode when control reaches main().

    I came across your pdf on NOR flashing tool and your feedback on the flashing tools user guide. We will consider them in our next release.

     

    Regards

    Mansoor

  • Hi Mansoor,

    I went through the CCS5 project and fixed all the path issues. I got past most of the issues but I don't think a .out was ever generated.

    I do have a fairly new CCS5 on my Window's machine but I haven't tried to build the flash-utils there.  I'll give that a try.  I just downloaded the June 2 releases CCS5 for win & linux so I'll also update my machines to the latest and give it a try.

    I sent Vaibhav the source .png files etc. for that flasher guide.  I did that to just further augment the documentation you guys had since the look and feel of ccs has changed so much.  Most here are only familiar with CCS3.

    Regards,

    Brian

     

     

  • Hi Brian,

    We will look into this issue. We will see if something is broken in NOR/SPI project with respect to the CCSv5 version in the latest EZSDK.

    Thanks a lot for sharing the diagrams, we will check the latest CCSv5 IDE and use them accordingly.

    Regards

    Mansoor

  • Has this been resolved?  We're seeing the same issue on our C6 based project.  We tried modifying the source to point to main directly, but we're getting errors that indicate it is missing the referenced library (tools/compiler/tms470/lib/rts32earm9.lib).  Where do we find this?