• State
  • Locked Locked
  • Replies 17 replies
  • Subscribers 99 subscribers
  • Views 2117 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.

TMS320C6748 LCDk Dev. Kit - Ethernet Port

Yacob Hassidim
Intellectual 645 points

Other Parts Discussed in Thread: TMS320C6748, OMAP-L138

Hello,

I am working on TMS320C6748 Dev. Kit (LCDK), (see http://www.ti.com/tool/tmdxlcdk6748?DCMP=dsp-anniv-120901&HQS=dsp-anniv-em-sw1).
 
I am trying to operate the Ethernet channel of the board.
 
I installed all the necessary drivers and succeeded to build the network examples mentioned in the drivers (NDK and NSP and their documents).
 
I don't have emulator and I burn the applications.
 
I debug the applications via USB-UART port.

I receive the message:  "NO PHY CONNECTED".

Can you please advise me?

Can you please refer me to someone that worked with this board and succeeded to operate the Ethernet port?

Sincerely, 

Yacob Hassidim.

 

  • 0
    TI__Intellectual 1585 points

    Hi Yacob,

     

                Kindly let us know which project you are building and flashing?

    Is it one of the Starterware enet examples or is it a project you have developed?

     

    Regards

    Iyshwarya G

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your response.

    I tried the CFGDEMO and CLIENT examples of NDK/NSP packages. I didn't see any response from Dev. Kit (also Wireshark didn't show any message from the Dev. Kit).

    I developed an application as explained in the document spru523_ug.pdf, section 3.3.3.1 "Constructing a Configuration for a static IP and gateway".

    I debug via USB-UART channel.

    I receive the message: "NO PHY CONNECTED".

    My host is Windows 7 and I disable the Firewall.

    Sincerely,

    Yacob Hassidim.

     

  • 0 in reply to Yacob Hassidim
    TI__Intellectual 1585 points

    Yacob,

    Kindly let us know the ndk version details you have used so that we can debug your issue with it.

    Also ensure the CFGDEMO example you have used is for C6748 or evm6748. The evm6748 example may not give you results in the C6748 LCDK board.

     

    Regards

    Iyshwarya

    If this answers your question, please click the Verify Answer button below. If not, please reply back with more information

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your response.

    How can I know CFGDEMO is for C6748 or evm6748?

    I continued to debug the application I developed in accordance to spru523_ug.pdf, section 3.3.3.1 "Constructing a Configuration for a static IP and gateway".

    I found no PHY is alive. The ALIVE register is 0.

    See: module: csl_mdio.c, function MDIO_timerTick, case PHYSTATE_MDIOINIT, the statement: ltmp1 = MDIO_REGS->ALIVE.

    I tried on another Dev. Kit board and I get the same message: "NO PHY CONNECTED".

    Can you please advise what is the reason the PYH is not ALIVE?

    Sincerely,

    Yacob Hassidim.

     

  • 0 in reply to Yacob Hassidim
    Intellectual 645 points

    Hello (again) Iyshwarya,

    I checked the REVision register of MDIO. The value was 0 (should be 0x00070104)! It may me means that the MDIO was not enabled/operated.

    I am sure that function MDIO_open is called and performed.

    Can you please check what is the reason the MDIO does not respond?

    Sincerely,

    Yacob Hassidim.

     

     

  • 0 in reply to Yacob Hassidim
    Intellectual 645 points

    Hello Iyshwarya,

    I received the emulator XDS100v2 and I succeeded to operate the Ethernet component (Ping command) via Code Composer.

    Can you please advise how can I burn the application and the Ethernet component will work in one of the following options:

     a) Code Composer and the Emulator (I didn't found the burning Flash option)

     b) AISgen (as you know I succeeded to burn but the Ethernet component did not work)

    Sincerely,

    Yacob Hassidim.

     

     

  • 0 in reply to Yacob Hassidim
    TI__Intellectual 1585 points

    Hi Yacob,

     

                For your question on burning the application into C6748LCDK, kindly refer the following wiki link that specifies the method to flash the binaries using both CCS and serial flasher utility.

    http://processors.wiki.ti.com/index.php/LCDK_User_Guide#NAND_Flashing

     

    Note: check whether you are using the correct LCDK config file in your AIS gen utility. If not the link to download the correct .cfg file for LCDK is available in the above link.

     

    Regards

    Iyshwarya

     If this answers your question, please click the Verify Answer button below. If not, please reply back with more information

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your answer.

    I tried all the possible burning options. Following the status of them:

    1) UART Boot Host (GUI application): The burning is stopped because of "I/O Error in read". following the log of the burning:

    (File IO): Read 429312 bytes from file C:\DspApplication.bin.

    (Serial Port): Opening COM3 at 115200 baud...

    (AIS Parse): Read magic word 0x41504954.

    (AIS Parse): Waiting for BOOTME... (power on or reset target now)

    (AIS Parse): BOOTME received!

    (AIS Parse): Performing Start-Word Sync...

    (AIS Parse): Performing Ping Opcode Sync...

    (AIS Parse): Processing command 0: 0x5853590D.

    (AIS Parse): Performing Opcode Sync...

    (AIS Parse): Executing function...

    (AIS Parse): Processing command 1: 0x5853590D.

    (AIS Parse): Performing Opcode Sync...

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (Serial Port): Read error: The operation has timed out.

    (AIS Parse): I/O Error in read!

    (AIS Parse): Opcode Sync failed after 11 consecutive I/O failures.

    (AIS Parse): Boot aborted.

    (Serial Port): Closing COM3.

    2) sfh_OMAP-L138.exe (command line): I run the following commands:

         sfh_OMAP-L138.exe -erase -targetType C6748_LCDK -flashType NAND -p COM3

         sfh_OMAP-L138.exe -flash_noubl -targetType C6748_LCDK -flashType NAND -p COM3 Application.bin

    The burning is succeeded and most of periferals are working (e.g. GPIO, USB-UART, timers) but the Etherent does not work.

    3) NANDWriter_DSP (via CCS and Emulator): I changed to NANDWIDTH_16 and build the program anf run via Emulator.

        I entered the filename Application.bin.

       The burning succeeded but nothing started to run.

    The application loaded via Emulator runs perfectly.

    Attached please find the cfg file I use for AISgen (ver 1.9) utility:

    1884.LCDK_AISGen_Config.cfg

    Sincerely,

    Yacob Hassidim.

     

     

  • 0 in reply to Yacob Hassidim
    TI__Intellectual 1585 points

    Hi Yacob,

                 Following are some pointers to debug the errors you are facing.

    1. Ensure whether the Application.bin file you are using is the bin file obtained from the AISGen utility(when the binary file is given as the input file and LCDK AISgen.cfg file is loaded) which you are using in the serial flasher utility.
    2. Kindly attach us the .bin files you are using to check from our side about your error on Ethernet port.
    3. Through CCS method, ensure whether you reboot the board after the flashing is done.

     

    Regards

    Iyshwarya

     

    If this answers your question, please click the Verify Answer button below. If not, please reply back with more information.

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your response.

    1. I am sure about the bin and cfg files

    2. Attached the bin file of CLIENT example. The CLIENT example runs perfectly with CCS and Emulator. (I changed the extension from bin to txt because the uploader didn't allow bin file):

    6403.ndk_evm6748_elf_client.txt

    3. I reboot the board number of times.

    Sincerely,

    Yacob Hassidim.

  • 0 in reply to Yacob Hassidim
    TI__Intellectual 1585 points

    Hi Yacob,

                The example program you have attached is of the evmC6748 which as I have mentioned earlier will not yield you results on your C6748LCDK board.

    If you are interested in working on the Ethernet port of the C6748 LCDK board kindly take a look at the C6748_StarterWare_1_20_03_03\build\c674x\cgt_ccs\c6748\lcdkC6748\enet_echo example.

    Regards,

    Iyshwarya

    If this answers your question, please click the Verify Answer button below. If not, please reply back with more information

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your answer.

    I tried the enet_echo example (static IP).

    Running of it under CCS and emulator: I received UART message but the Ethernet does not respond.

    Burning of example: No UART message but the Ping succeeded. I have other problems with this example e.g.:

    - BIOS is not supported

    - There is no way to shutdown the Ethernet (I need it in order to use the SPI channel that is pin multipexed with Ethernet)

    Returning to NDK and NSP examples: they running perfectly under CCS and Emulator so it seems they are compatible to C6748LCDK.

    The Release Notes of NDS (attached) mention that release is validated usnig the LCDK platform:

    Fullscreen 7506.nsp_1_10_00_03_release_notes.html Download 
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><!-- 
 *  Copyright (c) 2010, Texas Instruments Incorporated
 *  All rights reserved.
 *
 *  Redistribution and use in source and binary forms, with or without
 *  modification, are permitted provided that the following conditions
 *  are met:
 *
 *  *  Redistributions of source code must retain the above copyright
 *     notice, this list of conditions and the following disclaimer.
 *
 *  *  Redistributions in binary form must reproduce the above copyright
 *     notice, this list of conditions and the following disclaimer in the
 *     documentation and/or other materials provided with the distribution.
 *
 *  *  Neither the name of Texas Instruments Incorporated nor the names of
 *     its contributors may be used to endorse or promote products derived
 *     from this software without specific prior written permission.
 *
 *  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 *  AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 *  THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 *  PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 *  CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 *  EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 *  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
 *  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 *  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
 *  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 *  EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 * 
-->


    
    
    
  

  
  

  <title>NDK Support Package (NSP) 1.10.00.03 GA Release Notes</title><!-- For now, we use the doxygen style sheet --><link type="text/css" rel="stylesheet" href="docs/doxygen.css"><!-- doxygen's css .memproto's all have tables for a little extra pad...
         don't like tables, so give 'em a little extra pad ourselves
    -->


    
    
  
  <style type="text/css">
    .memproto {
        padding: 3;
    }
    </style></head>
<body>


<table width="100%">


  <tbody>


    <tr>


      <td bgcolor="black" width="1">
        <a href="http://www.ti.com">
          <img src="docs/tilogo.gif" alt="Texas Instruments" border="0">
        </a>
      </td>


      <td bgcolor="red">
        <img src="docs/titagline.gif" alt="Technology for Innovators(tm)">
      </td>


    </tr>


  
  
  </tbody>
</table>



<h1 align="center">NSP 1.10.00.03 GA Release Notes</h1>


<h2 align="center">January 05, 2012</h2>



<p>
This NSP Release contains ethernet driver support for the evmOMAPL138
ARM9 and and the evm6748 C674X DSP. It also provides&nbsp;SYS/BIOS 6.x
network examples which run on both the evm6748 C674X DSP and the
evmOMAPL138 ARM9 processor.
</p>


<p align="center">
<a href="#Introduction">Introduction</a>,
<a href="#Documentation">Documentation</a>,
<a href="#Whats_New">What's New</a>,
<a href="#Upgrade_Info">Upgrade Info</a>,
<a href="#Compatibility">Compatibility Information</a>,
<a href="#Device_Support">Device Support</a>,
<a href="#Validation">Validation Info</a>,
<a href="#Known_Issues">Known Issues</a>,
<a href="#Examples">Examples</a>,
<a href="#Rebuilding_driver_libs">Rebuilding The Driver Library</a>,
<a href="#Version">Version Information</a>,
<a href="#Support">Technical Support</a>.
</p>



<hr>

<h2><a name="Introduction">Introduction</a></h2>



<p>The Network Development Kit Support Package (NSP)
contains&nbsp;ethernet driver code, libraries and network examples for
various TI
platforms. &nbsp;It is meant to supplement the Network Development Kit
(NDK), which consists of the platform independent networking code.</p>
<p>The NSP includes demonstration software which showcases
the&nbsp;OMAPL138 DSP's capabilities across a range of network enabled
applications, including SYS/BIOS 6.x.</p>
<p>The NDK examples found in this NSP can serve as a rapid prototype platform
for the development of network and packet processing applications, or to add
network connectivity to existing applications for communications,
configuration, and control. Using the components provided in the NDK and NSP,
developers can quickly move from development concepts to working
implementations attached to the network..
</p>



<hr>

<h2><a name="Documentation">Documentation</a></h2>


<p>
The following documents provide an overview of the NDK, the networking
programming API, and how to port the software to other platforms (The
following documents have not been updated to reflect changes in this
release).
</p>


<ul>


  <li>
    <a href="http://www-s.ti.com/sc/techlit/spru523.pdf">NDK User's
    Guide</a>: Documents the NDK basics, and describes how to develop or
    port a network-enabled application. It also describes how to customize
    the network environment to fit your embedded environment. 
  </li>


  <li><a href="http://www-s.ti.com/sc/techlit/spru524.pdf">NDK Programmer's
  Reference Guide</a>: Describes the NDK library API calls in detail.
  It also includes a description of the stack's internal object based
  API functions. 
  </li>


  <li><a href="http://www-s.ti.com/sc/techlit/sprufp2.pdf">NDK Support
    Package Ethernet Driver Design Guide</a>: 
    Describes the NIMU based architecture of the Ethernet Drivers
    packaged in the NSPs. 
  </li>


</ul>



<p>
In addition, users are encouraged to monitor (and contribute to!) the
<a href="http://tiexpressdsp.com">TI Embedded Processors Wiki</a>.
</p>



<p>
Release notes from previous releases are also available in the <a href="http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/index.html">
release website.</a>
</p>



<hr>
<h2><a name="Whats_New">What's New</a></h2>



<h3>New Features</h3>


<ul>


  <li>This release no longer provides examples for DSP/BIOS 5.x. &nbsp;The examples are designed for SYS/BIOS 6.x only.</li>
  
  <li>Added libraries for&nbsp;C674X ELF support</li>
  <li>Example zip files have been renamed for COFF and ELF variants.</li>
  <li>CCSv5.1 example projects</li>
</ul>




<h3>Bug Fixes</h3>
   <ul>
        <li style="font-family: Times New Roman;">SDOCM00086412 [NSP] NSP examples do not build out of the box with NDK 2.21</li><li style="font-family: Times New Roman;">SDOCM00085287 [NSP] need to add ELF support for NSP driver libs</li><li><span style="font-family: Times New Roman;">SDOCM00085286 [NSP] Freon NSP must be updated to work with CCSv5.1</span></li></ul>

<hr>
<h2><a name="Upgrade_Info">Upgrade Information</a></h2>
None.<br>
<hr>
<h2><a name="Compatibility">Compatibility Information</a></h2>
<p>
This release must be used with&nbsp;following component versions (or higher):
</p>

<ul>
  <li>SYS/BIOS <b>6.33.01.25</b></li><li>CCS <span style="font-weight: bold;">5.1</span></li><li>NDK&nbsp;<span style="font-weight: bold;">2.20.06.35</span></li><li>XDCtools <span style="font-weight: bold;">3.23.00.32</span></li><li>C674X: C6000 Code Generation Tools <span style="font-weight: bold;">7.3.1</span></li><li>ARM9: TMS470 Code Generation Tools <span style="font-weight: bold;">4.9.1</span></li>
</ul><span style="font-weight: bold;"></span><ul>
</ul>



<hr>
<h2><a name="Device_Support">Device Support</a></h2>

<p>
This release supports the following devices:
</p>

<ul>

  <li>C674x:&nbsp; COFF and ELF
  </li>
  <li>ARM9: ELF format only
  </li>

</ul>

<hr>
<h2><a name="Validation">Validation</a></h2>


<p>
This release was built and validated against using the following software
components:
</p>



<ul>


  


  <li>SYS/BIOS&nbsp;<b>6.33.01.25</b></li>
  <li>NDK<b>&nbsp;</b><span style="font-weight: bold;">2.20.06.35</span></li>


  

  <li>CCS&nbsp;<span style="font-weight: bold;">5.1</span></li>


  <li>XDCtools&nbsp; <span style="font-weight: bold;">3.23.00.32</span><b></b></li>


  

  <li>Red Hat Enterprise Linux 4 (SMP)</li>


  <li>Pre-built binaries (example applications) were built with the following toolchains:</li><ul><li><span style="font-weight: bold;"> </span>C674X: C6000 Code Generation Tools<span style="font-weight: bold;"> 7.3.1</span></li><li><span style="font-weight: bold;"> </span>ARM9: TMS470 Code Generation Tools<span style="font-weight: bold;"> 4.9.1</span></li></ul><li>Pre-built binaries (libraries) were built with the following toolchains:</li>
  <ul>
          <li><span style="font-weight: bold;"> </span>C674X: C6000 Code Generation Tools<span style="font-weight: bold;"> 7.0.0</span></li>
          <li><span style="font-weight: bold;"> </span>ARM9: TMS470 Code Generation Tools<span style="font-weight: bold;"> 4.9.0</span></li>
  </ul> 

</ul>



<p>
This release was validated using the following hardware platforms:
</p>



<ul>


  <li>OMAP-L138 EVM</li><li>LCDK</li>



  

</ul>



<hr>
<h2><a name="Known_Issues">Known Issues</a></h2>


<p>
</p>

<ul>


  <li>None.
  </li>

  
</ul>


<p></p>



<hr>
<h2><a name="Examples">Examples</a></h2>



<p>NDK examples&nbsp; may be found in the "packages/ti/ndk/examples"
directory&nbsp;.  The examples are stored as CCSv5.1 archive files that are meant to be imported into CCSv5.1.<br><br>The
following set up examples archives are currently shipped with the NSP.
You should choose one of the following archives depending on the
hardware platform (evmOMAPL138 or evm6748)&nbsp;you are using:
</p>
<ul>
        <li><b>ndk_evm6748_coff_examples.zip</b>&nbsp;- C674X DSP examples which build using SYS/BIOS 6.x for COFF</li><br>
        <li><span style="font-weight: bold;">ndk_evm6748_elf_examples.zip</span>&nbsp;-&nbsp;C674X DSP examples which build using SYS/BIOS 6.x for ELF</li><br>
        <li><b>ndk_omapl138_arm9_examples.zip</b> - ARM9 examples which build using SYS/BIOS 6.x</li><br>
</ul>

<p style="font-weight: bold;"><span style="font-family: Times New Roman;">Importing The NDK Example Projects Into CCSv5.1</span></p>

<p>Before following the steps in this section, please ensure that all dependent software that is listed in the section <a href="#Compatibility">Compatibility Information</a> has been installed.
</p><ul>
  <li>Open CCSv5.1 and create a new workspace.</li>
  <br>
  <li>From within the <span style="font-weight: bold;">CCS Edit</span> View, select the menu option "Project -&gt; Import Existing CCS/CCE Eclipse Project"</li>
  <br>
  <li>In the window that appears, click "Select Archive File", then click the "browse" button.</li>
  <br>
  <li>Navigate
to the location where you installed the nsp_1_10_00_03. &nbsp;If you
installed the NSP into C:\Program Files\Texas Instruments, then
navigate to:</li>
  <br>
  <ul>
    <li style="font-family: Courier New;">C:\Program Files\Texas Instruments\<b>nsp_1_10_00_03\</b>packages\ti\ndk\examples</li>
    <br>
  </ul>
  <li>Once in the examples directory, you will see the set of examples archives:</li><br>
  <ul>
        <li>ndk_evm6748_coff_examples.zip</li><br>
        <li>ndk_evm6748_elf_examples.zip</li><br>
        <li>ndk_omapl138_arm9_examples.zip</li><br>
  </ul>
  <li>Choose the archive file which correpsonds to your setup and click open</li><br>
  <li>Under
"Discovered Projects" you should see the examples listed that come from
the archive(s) you selected. Click "Finish" to import the examples.</li><br>
  <li>You may now build the NDK examples within CCSv5.1</li>
  <br>
 
 <li><b>NOTE</b>: if a project with the
same name as the NDK examples already exists in the workspace, then it
will not be found in the above steps. &nbsp;Therefore, it is
recommended that a new workspace is used for the above steps.</li>
</ul>
<p>
</p>




<hr>
<h2><a name="Rebuilding_driver_libs">Rebuilding The Driver Library</a></h2>
<p>The NDK Support Package includes the EMAC driver source files and a
RTSC build files that allow you to modify the driver sources and
rebuild the EMAC library. You can rebuild the EMAC driver sources in
order to modify, update or add functionality. If you edit any of the
driver source code and/or RTSC build files, you must rebuild the EMAC
library in order to incorporate these changes into it.
</p>
<p>The instructions on this page are intended for rebuilding the EMAC
driver library on Microsoft Windows in a DOS shell using the xdc
command. However, this library may also be re-built on Linux using the
xdc command that comes packaged with XDCtools. Linux users should
substitute any Windows specific copy, explorer, or DOS shell
instructions or commands with the Linux equivalents in the steps that
follow.
</p>
<p>
<b>Warning:</b> This section provides details about rebuilding the EMAC
driver source code. We strongly recommend that you copy the NSP
installation to a directory with a different name and update and
rebuild that copy, rather than rebuilding the original installation. </p>

<p style="font-weight: bold;"><span style="font-family: Times New Roman;">Making A Backup Copy Of The NSP Installation</span></p>

  <ul>
          <li>Create
a new directory on your computer. You will use this directory to store
a copy of the NSP installation. This directory will act as a container
for your NSP modifications. The full path to this directory <b>cannot contain any spaces</b>.<br><br>
For example, we recommend creating a directory called "C:/MYNSPBUILDS"
rather than using a location in the "My Documents" directory tree. </li><br>
          <li>Using Windows Explorer, copy the
entire NSP installation to the directory you just created. For example,
if you installed the NSP in the default installation location, then you
should copy the C:/PROGRAM FILES\TEXAS INSTRUMENTS\nsp_1_10_00_03
folder and all of its contents to the C:/MYNSPBUILDS folder. After this
step, the C:/MYNSPBUILDS folder should contain the nsp_1_10_00_03
folder, which is a copy of your NSP installation.</li><br>
     
        <li>Rename
the folder that contains the copy of the NSP installation. For example,
rename the C:/MYNSPBUILDS\nsp_1_10_00_03 directory to
C:/MYNSPBUILDS\CUSTOM_nsp_1_10_00_03 </li><br>
  </ul>
        
<p style="font-weight: bold;"><span style="font-family: Times New Roman;">Updating The config.bld File</span></p>
  <ul>
          <li>Using Windows Explorer, move to the C:/MYNSPBUILDS\CUSTOM_nsp_1_10_00_03/packages/ti/drv/omapl138 directory.  </li><br>
          <li>In this directory, find the file called "config.bld.default". Rename this file to be "config.bld".  </li><br>
          <li>Open the config.bld file for text editing.  </li><br>
          <li>Make
sure that the paths to the NDK 2.20 installation, XDCtools, and Code
Generation Tools are correct. For example, if you have installed NDK
2.20 and CCSv5.1 into the default locations, then the default values of
the following variables in config.bld should be correct. If you have
installed these components into different locations, then you must
update these variables to point to the correct installation locations: </li><br>
        <ul>
                <li><code>var xdctoolsInstallDir = "C:/Program Files/Texas Instruments/xdctools_3_23_00_32";</code></li>
                <li><code>var ndkInstallDir = "C:/Program Files/Texas Instruments/ndk_2_20_06_34";</code></li>
                <li><code>C674.rootDir = "C:/Program\ Files/Texas\ Instruments/ccsv5/tools/compiler/c6000"</code></li>
                <li><code>armElfTargets.Arm9.rootDir = "C:/Program\ Files/Texas\ Instruments/ccsv5.1/tools/compiler/tms470";</code></li><br>
        </ul>

        <li>Near the end of the file, look for the array called <code>Build.targets</code>.
This array contains the list of targets for which the EMAC driver
should be built. Make sure that the target for which you want the
driver built is uncommented. To build for all targets, this array
should look like the following: </li><br>
        <code>
                &nbsp;&nbsp;Build.targets = [<br>
                        &nbsp;&nbsp;&nbsp;&nbsp;C674,<br>
                        &nbsp;&nbsp;&nbsp;&nbsp;C674_big_endian,<br>
                        &nbsp;&nbsp;&nbsp;&nbsp;armElfTargets.Arm9,<br>
                &nbsp;&nbsp;];
        </code><br><br>

        <li>Save and exit the file.</li><br>
  </ul>
        
<p style="font-weight: bold;"><span style="font-family: Times New Roman;">Re-building The EMAC Driver</span></p>

  <ul>
          <li>In a DOS shell, navigate to the location of the copy of the NSP installation:</li><br>
          <code>&nbsp;&nbsp;&nbsp;&nbsp;cd C:\MYNSPBUILDS\CUSTOM_nsp_1_10_00_03\packages\ti\drv\omapl138</code><br><br>
          <li>Run the XDC command to rebuild the driver library</li><br>
          <code>&nbsp;&nbsp;&nbsp;&nbsp;xdc</code><br><br>
          <li>Or, if your XDCtools installation location is not on your path, type:</li><br>
          <code>&nbsp;&nbsp;&nbsp;&nbsp;"C:\Program Files\Texas Instruments\xdctools_3_23_00_32"\xdc</code><br><br>
<li>The driver rebuild should begin</li><br>
</ul>

<hr>
<h2><a name="Version">Version Information</a></h2>


<p>
This product's version follows a version format, <b>M.mm.pp.bb</b>,
where <b>M</b> is a single digit Major number, <b>mm</b> is 2 digit
minor number, <b>pp</b> is a 2 digit patch number, and <b>b</b> is an
unrestricted set of digits used as an incrementing build counter.
</p>



<p>
To support multiple side-by-side installations of the product, the
product version is encoded in the top level directory,
ex. <b>nsp_1_10_00_03</b>.
</p>



<p>
Subsequent releases of patch upgrades will be identified by the patch
number, ex. NSP 1.00.01 with directory <b>nsp_1_00_01</b>.
Typically, these patches only include critical bug fixes.
</p>



<hr>
<h2><a name="Support">Technical Support</a></h2>


<p>

</p>

<ul>


  <li>
  <a href="http://support.ti.com">Technical support resources</a>
  </li>


  <li>
  Forum-based technical support is available through the TI E2E Community in
  the <a href="http://e2e.ti.com/support/embedded/f/355.aspx">BIOS forum</a>
  </li>


  <li>
  <a href="http://tiexpressdsp.com/wiki/index.php?title=Category:NDK">Wiki-based documentation</a>
  </li>

  <li>
  <a href="http://focus.ti.com/general/docs/techdocsabstract.tsp?abstractName=spraax4">Getting
  Started with the C6000 Network Developer's Kit (NDK)</a>
  </li>


</ul>


<p></p>



<p>
Check
the <a href="http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/index.html">NDK
    website</a> for updates.
</p>



<hr>
<p>
Last updated: January 05, 2012 Build Ver: nsp_1_10_00_03 Rev: 
</p>


</body></html>
</body>
</html>

    The problem is running of them from Flash. It seems a problem with generating of the bin file.

    I attach again the CFG file I use with AISGen tool.

    4377.LCDK_AISGen_Config.cfg

    Can you please look at the CFG file and may be you find the problem?

    Alternatively: Can you please advise how can I use the ent_echo example (StartWare environment) with the following issues:

    - BIOS environment (Nice To Have)

    - The option of Ethernet shutdown and re-running (must)

    I appreciate your help.

    Sincerely,

    Yacob Hassidim.

  • 0 in reply to Yacob Hassidim
    Intellectual 645 points

    Hello Iyshwarya,

    I am waiting for your answer.

    By the way BIOS also is must.

    Thank you.

    Yacob Hassidim.

     

  • 0 in reply to Yacob Hassidim
    Intellectual 645 points

    Hello Iyshwarya,

    I am waiting for your answer.

    This is very urgent for me.

    I appreciate your support.

    Yacob Hassidim.

     

  • 0 in reply to Yacob Hassidim
    TI__Intellectual 1585 points

    Hi Yacob,

                 Kindly refer the LCDK config file from LCDK user guide wiki(link given below). From the comparison of your .cfg file there is mismatch in the Device type.

    http://processors.wiki.ti.com/index.php/LCDK_User_Guide#NAND_Flashing

    These are the examples we support right now for the LCDK kit and if some options are required you can customize your own code using these examples as the basis.

    You can refer the following wiki link for understanding the Starterware Ethernet design

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

    Regards,

    Iyshwarya

    If this answers your question, please click the Verify Answer button below. If not, please reply back with more information.

  • 0 in reply to Iyshwarya Gopalakrishnan
    Intellectual 645 points

    Hello Iyshwarya,

    Thank you for your answer.

    The device type of the original .cfg file is ARM while I am working with DSP device type (LCDK).

    I tried also with ARM device type but unfortunately I didn't receive any response from LCDK, while the LCDK works perfectly with emulator and CCS.

    Regarding to examples for LCDK: I didn't find them. Can you please link me exactly to them?

    Regarding to StarterWare: All of my project runs under PSP/BIOS and this is very important for me.

    Sincerely,

    Yacob Hassidim.

     

     

  • 0 in reply to Yacob Hassidim
    Prodigy 170 points

    Hi Yacob,


                I need an information about about this LCDK, It seems you worked on this LCDK. Which emulator you are using XDS100V2 with 20 pin or 14 pin? It will be very much helpful for me if you can respond to my post regarding this? Below is the link.

    http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/t/325048.aspx