• State TI Thinks Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 5 answers
  • Subscribers 103 subscribers
  • Views 611 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

TMS320C6747：Please tell me about a parallel flash.

コンパイラ/ TMS320C6747：The following build errors occur in CCSv9, please tell me the workaround.

user6063296
Intellectual 280 points
Part Number: TMS320C6747

Tool/software: TI C / C ++コンパイラ

Hello
The issue of boot loading that I got advice from everyone found and solved a flash rewriting program developed nine years ago. Transfer this application to C6747 using UARTHOST.EXE, start it, send HEX in Hyper Terminal and the application will write. I apologize to you for a fuss over.

It is another question. I will tell you the condition again.
Developed nine years ago, there is another company's "C6747 + spartan3e + usb" circuit board.
There was a record that CCS at the time of development was IDE V4. There are also source files. This time CCS uses v9. xds200 usb is not yet purchased.
The installation location is C: \ ti \ ccs910
Workspace, project
C: \ Users \ alex \ workspace_v9
C: \ Users \ alex \ workspace_v9 \ LS041
In addition, I installed the following BIOS.
   DSPBIOS5_41_03_17
   C6747_BIOSPSP_01_30_01
   EDMA3_LLD_BIOS5_01_11_00_03
And
C: \ Program Files \ Texas Instruments \ ccsv4 \ emulation \
boards \ evmc6747 \ gel \ evmc6747_dsp.gel
Switched to a new one. The difference is
(1)Setup_System_Config, * _PLL, * _Psc_All_On, * _EMIFA / B
comment out in OnTargetConnect.
(2)100 MHz in Setup_PLL
(3)PLL0_PLLDIV3 / 5/7, KICK0 / 1R, CFGCHIPS3 Comment out.
The above settings were described in the found development document.


So the question is
The following build errors occur in CCSv9, please tell me the workaround.
">> Compilation failure
subdir_rules.mk:9: recipe for target 'syscfg.obj' failed
"../syscfg.c", line 3: fatal error # 1965: can not open source file "ti / pspiom / cslr / soc_C6747.h"
1 catastrophic error detected in the compilation of "../syscfg.c".
Compilation terminated.
gmake: *** [syscfg.obj] Error 1
gmake: Target 'all' not remade because of errors. "

The third line of syscfg.c is
#include "ti / pspiom / cslr / cslr_syscfg_C6747.h"

There are eight other errors of the same type.
Hst.h, iom.h, log.h, que.h can not be opened.
I searched for everything but I can not find it.

TI's compiler understands that only ascii can be used, and because Japanese is included in the comment section of each place of the source file with about 30 files, fatal errors may be caused by this Japanese. However, it should have passed 9 years ago, so there should be a way to avoid NG.
Is the setting I ran short? Is it possible for me to switch compilers?

It is very complicated, but I hope it helps.

  • 0
    TI__Mastermind 27355 points

    Hello,

    Can you please check if the file ti/pspiom/cslr/cslr_syscfg_C6747.h exists on your machine? It should be located in the BIOSPSP install directory, which by default is located at C:\Program Files\Texas Instruments\pspdrivers_01_30_01

    If it does exist, you may need to include the path "C:/Program Files/Texas Instruments/pspdrivers_01_30_01/packages" in CCS by going to Build Settings > Build > C6000 Compiler > Include Options as shown in the screenshot below.

    You can then repeat this for any other remaining errors of this same type.

  • 0 in reply to Sahin Okur
    Intellectual 280 points

    Hello
    Thank you for your response with screenshot.
    Well, it's a connection with a device I installed later.
    The problem presented has disappeared in the way you specified.
    All other files belonged to bios and disappeared in the same way.

    This led to many undefined errors.

    Add option settings and errors as shown in the screenshot below.

    In the first place, did you make a mistake at the time of installation?
    Also, please tell me the solution to this.

  • 0 in reply to user6063296
    Intellectual 280 points

    (Oops, I made a mistake.)
    In the first place, did I misconfigure the installation?
    Or is the definition file not included?
    There are undefined
    Uns, Arg, Void, String, Fxn, Ptr, Int, Bool, Char, and more!
    Please let me know if you can imagine some settings.

    Thank you.

  • 0 in reply to user6063296
    TI__Guru**** 173310 points

    Which header files are included in the source file being compiled here, (ie) Uart.c?

    Please show a snippet of the Uart.c source file with the #include statements or attach the file here.
    Also it would help if you did a Rebuild Project and saved the build log to a text file and attached that as well.

  • 0 in reply to AartiG
    Intellectual 280 points

    Hello
    I got that question from you and finally came to the need for a BIOS configuration. Can you introduce a user guide to configure with ccs 9 after DSP / BIOS installation?

    thank you.

  • 0 in reply to user6063296
    Intellectual 280 points

    Hi
    I think that the source file you say is the source file to be developed,
    Perhaps I noticed that the problem was that I was not processing the BIOS. I just installed it.
    The monthly Japanese magazine "interface (2009, mar)" explained that in order to use DSP / BIOS, it is necessary to perform configuration.
    I have an unknown point in the middle of configuration.
    Project location is
    C: \ ti \ ccs 910 \ workspace 910
    The bios installation location is

    C: \ Program Files \ Texas Instruments \ bios_5_41_03_17

    File | New | DSP / BIOS Configuration File

    TCF file name is the default DspBiosConfiguration.tcf
    After specifying the project location
    I do not know what to specify for a valid platform and filter.
    Please let me know the points to keep in mind, or tell me the appropriate user guide.
    By the way, the board is a custom board (LS041-1).

    Best regards,

    Suzuki

  • 0 in reply to AartiG
    Intellectual 280 points

    Hi
    Uart.c is a file of bios, and when I added the include path from the previous teaching, I found that file, but the next error is confused because the definition statement is in bios.
    I will send you the log (the log at build time) that you told me.

    Best Regardsbuild_log_2019_0724.txt

  • 0 in reply to user6063296
    TI__Guru** 114420 points

    User6063296,

    It appears that you are trying to revive nine year old software using latest and greatest software tools offered by TI. The build environment poses many problems as you need to know exactly what tool set and build environment to use for your development. There is quite a lot that has changed with the C6000 software and compiler and TI RTOS 

    Please consider the following issues:

    1. You seem to be using DSPBIOS with CGTools 8.3.3. Please note that the newer CGtools has dropped support for COFF binaries that DSPBIOS supported and now only supports EABI/ELF binaries which are the industry standard for executable. You need to use CGTools 7.x or earlier for this build to work.

    2. Prefer to use the correct combination of DSPBIOS and BIOS PSP versions that are compatible based on the release notes. Please note that XDC tools is now a separate component that is included with the CCS install. DSP BIOS included the XDCtools package so make sure the build is using XDCtools from DSPBIOS and not the latest XDC tool chain.

    The missing symbols Fxn,  Arg are defined in the file std.h in the folder location: bios_5_4x_xx_xx\xdctools\packages\xdc

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 280 points

    Thank you, Mr. Rahul

    Your detailed explanations made me much brighter.
    I will continue to ask what I do not know.
    1.
    > You need to use CGTools 7.x or earlier for this build to work.
    CGTools 7.x are
    http://software-dl.ti.com/codegen/non-esd/downloads/download.htm

    Should I download the following from?
    C6000 Code Generation Tools v7.4.24
    [Windows]

    In what procedure can I use this in ccs9?

    2.
    > so make sure the build is using XDCtools from DSPBIOS and not the latest XDC tool chain.
    In what procedure can I use this XDCtools in ccs9?

    3.
    > bios_5_4x_xx_xx \ xdctools \ packages \ xdc
    Should I add it to the include option ?

  • 0 in reply to user6063296
    TI__Guru** 114420 points

    For CCSv9, install the compiler version 7.x in the folder :

    C:\ti\ccs901\ccs\tools\compiler

    Restart CCS and right click on project and go to Build Settings-> General and change the compiler version associated from the drop down menu. If you don`t see the required compiler version, browse to the cl6x.exe utility in the compiler bin folder.

    A good way for me to provide XDC guidance would be if you can indicate what your project properties looks like and if you could provide a build log (attach to your post).  Typically for BIOS projects there is a XDCtools tab in CCS as shown below:

    Quite frankly, we have not supported DSPBIOS projects in CCSv9. DSPBIOS was last supported with CCSv5.x so we may need to figure some things as we debug your setup.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 280 points

    Thank you Mr. Rahul
    I am launching ccsv5 with bios support.
    As I only have win10 machines, I am installing in win7 compatible mode. Please wait as it takes time.
    For now, paste the project properties in v9.
    15: 00 @ japan

  • 0 in reply to user6063296
    Intellectual 280 points

    Hi Mr. Rahul

    I am troubled with this error now.   See details below.
    Error: Import failed for project 'LS041' because its meta-data cannot be interpreted. Please contact support.

    Here is the process.
    Dell Vostro Core_i7 / 3.4GHz / 8GB / 900GB_HDD (400GB free)
    I have uninstalled all Texas Instruments drivers & apps from win10.

    after that,
    I installed CCS5.5.0.00077_win32 in win7 compatible mode.
    Install C6747_BIOSPSP_01_30_01 in vista compatible mode.
    Install EDMA3_LLD_BIOS5_01_11_00_03 in vista compatible mode.

    When importing a source file set, I was asked to set the compiler to 8
    Install ti_cgt_c6000_8.3.1_windows_installer.exe    and set the selection in General.

    When importing a source file set, this time meta-data_error occurs.

    readMe_eng.txt 
    Deployment when installing CCS4 by default

�E Under My Documents \ workspace
???LS041 (Correlation operation program)
???boot2nd (Startup program)
???FROM (Flash ROM rewrite program)
???Copy folders

�E Install BIOS
???DSPBIOS5_41_03_17                         ( Built in ccs_5.5  because ccs_9 does not support bios )
???C6747_BIOSPSP_01_30_01
???EDMA3_LLD_BIOS5_01_11_00_03
???Run and install the setup in each folder

�E Copying DSP initialization setting file at ICE startup
???Copy evmc6747_dsp.gel to the C: \ Program Files \ Texas Instruments \ ccsv4 \ emulation \ boards \ evmc6747 \ gel folder
???Note: Since the evmc6747_dsp.gel file already exists in the copy destination folder, backup it if necessary.

C: \ ti \ ccsv5 \ ccsv5 \ ccs_base \ emulation \ boards \ evmc 6747 \ gel       was replaced 2019/07/29

    The attached four files are as follows.
    *ReadMe_eng.txt  :  Translation of Readme.txt by developer 9 years ago. (Added some changes.)
    *ccs55_comp.png  :  Compiler switching setting
    *ccs_v55_incl.png  :  Installed components
    *ccs_v55_meta-data_error.png  :  Error message

    17: 30 @ japan

  • 0 in reply to user6063296
    TI__Guru** 114420 points

    I am closing this issue since you have created newer E2E threads regarding this setup.

    Regards,

    Rahul