[FAQ] 66AK2E05: DHCP configuration for K2E and K2H family.

Rajarajan Uthayakumar

Expert 4314 points

Part Number: 66AK2E05

How o set up the DHCP network configuration for K2E and K2H family devices?

over 3 years ago

0 Rajarajan Uthayakumar over 3 years ago

TI__Expert 4314 points

To run the NIMU EMAC example for K2E devices make sure the pre-requisites are present.

Install CCS (https://www.ti.com/tool/download/CCSTUDIO/9.3.0.00012),
TI RTOS SDK
1. For K2E: Install PROCESSOR-SDK-RTOS-K2E (Version: 06_03_00_106, http://software-dl.ti.com/processor-sdk-rtos/esd/K2E/latest/index_FDS.html ),
2. For K2H: Install PROCESSOR-SDK-RTOS-K2HK 06_03_00_106 https://software-dl.ti.com/processor-sdk-rtos/esd/K2HK/latest/index_FDS.html
Generate the Example projects for PDK,
1. For K2E: (https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1040858/faq-66ak2e05-how-to-generate-the-ccs-pdk-examples-for-k2e?tisearch=e2e-sitesearch&keymatch=66AK2E05#).
2. For K2H: (https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1083353/faq-66ak2h14-how-to-generate-the-ccs-pdk-examples-for-66ak2h14---k2h-evm/4010024#4010024).

Now Import the CCS project into CCS and go on

To Import the project goto File -> Import -> "CCS projects" in "C/C++" -> Browse "Select Search-directory". make sure to uncheck the "Copy Projects into Workspace" (This is to avoid compilation errors only If TI-RTOS SDK was installed in a different location than "C:\ti\").
Now,
1. For K2E: we have a DSP example project ("NIMU_emacExample_EVMk2eC66BiosExampleProject") and ARM example project ("NIMU_emacExample_EVMk2e_armBiosExampleProject") (Do not open ARM and DSP examples at the same time, CCS will throw project out-of-sync error dialog).
  1. Both DSP and ARM project uses "HelloWorld.c" where NIMU IP configuration is stored. Same code changes are applicable for ARM and DSP projects.
2. For K2H: Now, we have a DSP example project ("NIMU_emacExample_EVMK2HC66BiosExampleProject") and ARM example project ("NIMU_emacExample_EVMK2H_armBiosExampleProject") (Do not open ARM and DSP examples at the same time, CCS will throw project out-of-sync error dialog).
  1. Both DSP and ARM project uses "HelloWorld.c" where NIMU IP configuration is stored. Same code changes are applicable for ARM and DSP projects.
3. Network configuration is,
4. Code changes are shown below,
```
//
// Main Thread
//
int StackTest()
{
    ...
    // If the IP address is specified, manually configure IP and Gateway
    #if defined(_SCBP6618X_) || defined (DEVICE_C6678) || defined(_EVMTCI6614_) || defined(DEVICE_K2H) || defined(DEVICE_K2K) || defined(DEVICE_K2L) || defined(DEVICE_K2E)

    /* SCBP6618x, EVMTCI6614, EVMK2H, EVMK2K always uses DHCP */
    if (0) // set it as 0 for DHCP IP configuration
    {
        //Manual IP configuration code
    }
    else
    {
        //DHCP IP configuration code
    }
    ...
}
```
5. For K2E:
  1. Output for DHCP for DSP core
  2. Verification
  3. Output for DHCP in the ARM core
6. For K2H:
  1. Output for DHCP for DSP core
  2. Verification
7. Unlike C665x and C667x examples, Telnet and HTTP service were not included in the source code. So, TCP Ports 23 and 80 remain closed and only verification can be done using the Ping utility.
8. Note: While connecting EVM with PC in static IP mode without a router (Kind of like Local LAN). The Ping between PC and EVM is not happening.

Thanks & Regards,

Rajarajan U

Processors

Processors forum

[FAQ] 66AK2E05: DHCP configuration for K2E and K2H family.