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.

TCP_IP with CPSW not running

Other Parts Discussed in Thread: SYSBIOS, TMDSICE3359

Equipment: 

ICEv2.1 board,
CCSv6 vs 6.1.0.00104
TI XDS100v2 USB Emulator,
Windows7,
am335x_sysbios_ind_sdk_1.1.0.6
Compiler TI v5.2.4
PRU Compiler Tools 2.1.1
SYSBIOS(Target Content) 6.40.3.39

Hi,
so far I have been using the ICEV2 board with a project that has been derived from the EthernetIP example that came with SDK 1.1.0.6.
It runs fine with TCP/IP and PRUSS.
The industrial OEM board I would like to use later does not use PRUSS, instead the MII peripheral is connected to the transceiver.
Now as a first step I would like to run the ICE2v1 board with CPSW, but it does not work:
     Network_open_hook() is still reached and service status is DHCP.
     After quite a while DHCP is switched off and instead my default IP address 192.168.115.245 is set in the Network IP address Hook.
     But the client cannot connect to this IP.
     If the project is run without DHCP and a special IP is preset, the client can't connect either.
This is what I modified/tried:
1. #define USE_CPSW_DRIVER has been added.
2. Jumpers J18 and J19 have been set to RMII.
   (leaving them at MII didn't help either)
3. UTILsInitCpswIcssPorts(CPSW_SWITCH)
This function shall activate CPSW mode:
void UTILsInitCpswIcssPorts(unsigned char swicthType)
{
GPIOPinWrite(SOC_GPIO_3_REGS, 4,1);
if(ICSS_SWITCH == swicthType)
{
GPIOPinWrite(SOC_GPIO_3_REGS, 10,0);
GPIOPinWrite(SOC_GPIO_0_REGS, 7,0);
}
else
{
GPIOPinWrite(SOC_GPIO_3_REGS, 10,1);
GPIOPinWrite(SOC_GPIO_0_REGS, 7,1);
}
GPIOPinWrite(SOC_GPIO_0_REGS, 18,1);

UTILsResetPhys();
}
GPIO3_10 is MUX_MII_CTL1 to select the right mode. But looking at the scheme in Tmdsice3359_3h0013_sch_rev2_1a.pdf I cannot find out what GPIO3_7 and GPIO0_18 are used for.
 
4. Know issues
I am not connected with the EIP Tool, but could the known issue SDOCM00105257 be the reason for malfunction?
       "On ICEV2, Ethernet/IP application in CPSW mode doesn't connect with EIP Tool.
        (This is found to be problem with i2c communication to clock synthesizer which proivde clock to RMII ports)"
Did anybody ever get that TCP/IP example (derived from the EthernetIp example) running in CPSW mode?
Any ideas what to do?
Regards,
Martin H.
  • Martin,

    The example in ISDK should work in CPSW mode with the define USE_CPSW_DRIVER. This has been tested. Can you verify the changes coming within the define?

    We have a workaround for SDOCM00105257 , which is also in place in the code.

    Regards,
    Vinesh