• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 774 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problems with TMDSDSK6713 and daughter card TMDSFDCAFS86

Anatoliy Aframeew
Prodigy 40 points

Good day! Hi! I'm from Russia!

I work with the program Code Composer Studio 3.1. Problems with TMDSDSK6713 and daughter card TMDSFDCAFS86.

i built project BYTwithFADT_v1_0.pjt in CCS 3.1. I Load program of the compiled project, that is file BYTwithFADT_v1_0.out

After,clicked to "run".

Execute program BioscryptApiDemo.exe (..FADT2\BioscryptFADTdemo\PC_Demo_DSK6713\)

Clicked to "Enroll" and after few minutes i received error.

Trouble Halting Target CPU:
Error 0x80000020/-1070
Fatal Error Execution.
An unknown error prevented the emulator from accessing the processor in
a timely fashion. is recommended to RESET EMULATOR. This will
disconnect each target from the emulator. The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.
Reset emulator options

I need help.

Thanks!!!

Anatoliy!!!

  • 0
    TI__Guru* 84110 points

    Perhaps in this Floating Point Forum there may be some who are more familiar with the C6713. I have questions and comments that may show my lack of familiarity with it.

    • It is highly recommended that you upgrade to CCS 3.3. There are many bug fixes and enhancements. Even CCS 3.3 is at update 12 (SR12).
    • Where did BYTwithFADT_v1_0.pjt come from? I do not have a copy of it locally nor could I find it through google.
    • Where did BioscryptApiDemo.exe come from? Is "Enroll" something related to this exe?

    When you get an error message like the one you show above, it means something has gone very badly with the DSP such that the emulator cannot even access the CPU well enough to stop it from running. Unfortunately, there are a lot of conditions that might cause this and we cannot tell what other steps you have taken up to this point to validate your DSK with CCS.

    If you have just begun working with this DSK and this installation of CCS, I will recommend you work up from simpler projects. Write a simple a + b program and load & run it to verify that you can get something to work from the simplest level.

    Then move to your larger project and decide how you want to debug it. One idea would be to single-step some of BYTwithFADT_v1_0, but I cannot tell if that would be practical to do. Another way would be to set breakpoints at a few places to see what lines of code you are reaching before the failure - this can help you to narrow down to exactly where the failure occurs.

    But there are just too many things to try to list all that could go wrong: emulation wiring faults, DSP code branches into illegal memory, a peripheral or memory is stuck in a wait-state, and so on.

  • 0 in reply to RandyP
    Prodigy 40 points

    I have just updated my CCS 3.1 to CCS 3.3. thanks, problem solved, But now i have get  message:

    Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.

    BYTwithFADT_v1_0.pjt - this file from CD FINGERPRINT PRODUCT DEVELOPMENT Support for TI DSPs. Part #TMDSFDCAFS86

    CD INCLUDES: - Image capture drivers for AuthenTec FingerLoc AFS8600 sensor

                                 - Bioscrypt fingerprint verification algoritm for TMS320C67x(tm) DSP

                                - BIOSSCRYPT FADT demo for host interface (GUI for PC) = BioscryptApiDemo + BYTwithFADT_v1_0

                               - TMDSFDCAFS86 sensor board schematics

                              - User guides and software license agreements

    BioscryptApiDemo.exe - yes, It is buttons to this exe...

     

    In THE CD i have found in THE "Readme_FADT2.htm".

    There i have readed:

    IMPORTANT NOTE

     

    This FADT kit has been developed and tested to work with Code Composer Studio (CCS2.21) that comes with TMDSC6713 DSK Product Version 2 ONLY.

    Users of this kit, who have a Product Version 1 DSK 6713 board with Code Composer Studio (CCS2.20), can download the software patch to update their Code Composer Studio (CCS2.21).

     

    To update to CCS2.21, users can visit the Spectrum Digital DSP Starter Kit (DSK) for TMS320C6713 product webpage.

    On this page click on the FAQ (present on the top left hand side) and follow the instructions provided in order to download the software patch.

     

    BUT, i work with Code Composer Studio  CCS3.1 and  with Code Composer Studio  CCS3.3.

    And difference DSP/BIOS version.

    My project - DSP/BIOS V.4.82.150

    In CCS3.1/CCS3.3 my configuration file (i.e. BYTwithFADT_v1_0.cdb)  convert to cdb (DSP/BIOS v.4.90.270) / tcf(5.f31.02)...

    Memmory map differense too...

    (((

     

     

     

  • 0 in reply to Anatoliy Aframeew
    TI__Guru* 84110 points

    Anatoliy Aframeew said:

    I have just updated my CCS 3.1 to CCS 3.3. thanks, problem solved, But now i have get  message:

    Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.

    There are several things which can affect the memory utilization for your project. I will only make suggestions since I do not have this project to examine myself.

    • The DSP/BIOS configuration defines what memory elements exist and what parts of your program should be placed into the different memory areas. The DSP/BIOS configuration must match the physical memory available on your device and your board, so you should compare the configuration to the datasheet and the board technical documentation.
    • The linker command file (.cmd) is usually just the file that is generated by the DSP/BIOS builder during the project build. In some cases, there may also be additional linker command files added to support software-defined sections that are not the default ones known by DSP/BIOS. It is possible to define additional memory locations here, also, so these must match with the hardware, too.
    • There is often a memory map defined within CCS that tells CCS what addresses are valid locations for reading and writing. You can view the current memory map from the CCS toolbar under Options->MemoryMap. Here you can turn off memory mapping or edit the memory map. There are advantages to having the memory map turned on, so the best option is to leave it on and just make sure it is correct.
    • The memory map is most often defined in a GEL script that is loaded for your CCS workspace or from CCSetup. You can examine this GEL file from the Project pane on the left side of the CCS window. If you edit it, be sure to save it and then reload it. The GEL_MapAdd() commands will define all valid memory areas.
    • The .map file is usually located in the Debug or Release folder, but this is determined by your Project Build options. The map file has a summary at the top that shows how much space is used in each of the available memory areas. It also has detailed information on which memory areas to which each software section and component is placed. You can compare this to what is physically available to see if there is a conflict somewhere.

    The loader error sounds like it will be related to either the CCS Memory Map from your GEL file, or from the linker command file putting some software section into ROM or non-existent memory space. For either, comparing them with your map file and datasheet/board-spec will be helpful.

    Anatoliy Aframeew said:

    BUT, i work with Code Composer Studio  CCS3.1 and  with Code Composer Studio  CCS3.3.

    And difference DSP/BIOS version.

    My project - DSP/BIOS V.4.82.150

    In CCS3.1/CCS3.3 my configuration file (i.e. BYTwithFADT_v1_0.cdb)  convert to cdb (DSP/BIOS v.4.90.270) / tcf(5.f31.02)...

    Memmory map differense too...

    The memory map differences may go a long way to explaining your loader problem. Please examine those difference and you may find your problem.

  • 0 in reply to RandyP
    Prodigy 40 points

    Problem was solved for CCS 3.1.

    But, in the CCS.3.3 program not work.

  • 0 in reply to Anatoliy Aframeew
    TI__Guru* 84110 points

    If you are happy to continue with CCS 3.1, great. If not, there may be more information for you.

    Since the original project was designed for CCS 2.x and DSP/BIOS 4.8x, you may need to make accomodations for upgrading to a new version of DSP/BIOS when you upgrade to a newer version of CCS.

    The TI Embedded Processors Wiki has an article on migrating from BIOS 4.9 to 5.x. The top of the Wiki is at http://wiki.davincidsp.com/index.php?title=Main_Page . Under Software, click on DSP/BIOS and see all the article titles in alphabetical order.

  • 0 in reply to RandyP
    Prodigy 40 points

    To you it is very grateful for the help. Thanks. It that I searched.

  • 0 in reply to Anatoliy Aframeew
    Prodigy 130 points

    Hi,

    I am getting the same error message that you originally posted on the forum about. I am using CCS 3.1 and Bios 4.90.02.10 (according to the About window) and of course using a different source code program with the DSP/Bios configuration files. Can you remember what and where the problem was in the project and what it was you did to fix?

     

    Thanks!