Hercules LwIP ethernet

Jason Pitteman

Other Parts Discussed in Thread: DP83640, HALCOGEN

Hi all,

I've implemented the LwIP on the Hercules HDK and it works fine.

Now I have designed a new PCB and connected the ethernet module to a port of a switch (chip). This port of the switchh is configured as MII so that it is possible to communicate with the microcontroller. I use the same code as I used with the original HDK for LwIP. I do receive ARP requests (checked while debugging) from my laptop. This means that the configuration is okay. Now the LwIP stack responds to the network. The problem is that it does not transmit the whole frame as it should be. I have measured the transmit signals from the HDK and the new PCB. And it is clearly visible that the software on the HDK responds with a larger frame (which is correct) than the new PCB. Does anyone have an idea of what could possibly be wrong?

Thanks in advance,

Jason

over 9 years ago

0 Szilard Lovas over 9 years ago

Expert 1425 points

Hi Jason,
Which type of MCU? 3137? 4357?

0 Jason Pitteman over 9 years ago in reply to Szilard Lovas

Prodigy 190 points

Hello there,
I am using the RM57L843ZWT.

0 Szilard Lovas over 9 years ago in reply to Jason Pitteman

Expert 1425 points

Hi,
Just an idea, it could be difference in the default settings between DP83640 and your switch chip?

0 Jason Pitteman over 9 years ago in reply to Szilard Lovas

Prodigy 190 points

Hello,
I selected in HALCoGen under EMAC global the custom PHY option. I do receive correct packets from my laptop. But when it wants to transmit a packet, it does not transmit all the bytes.

0 Szilard Lovas over 9 years ago in reply to Jason Pitteman

Expert 1425 points

I haven't see the new HalCoGen yet, but you should check, if you have to write your own custom function for handling switch chip and its registers like:

extern uint32 Dp83640IDGet(uint32 mdioBaseAddr, uint32 phyAddr);
extern void Dp83640Reset(uint32 mdioBaseAddr, uint32 phyAddr);
extern boolean Dp83640AutoNegotiate(uint32 mdioBaseAddr, uint32 phyAddr, uint16 advVal);
extern boolean Dp83640PartnerAbilityGet(uint32 mdioBaseAddr, uint32 phyAddr,uint16 *ptnerAblty);
extern boolean Dp83640LinkStatusGet(uint32 mdioBaseAddr, uint32 phyAddr,volatile uint32 retries);
...
see HL_phy_dp83640.h

0 Szilard Lovas over 9 years ago in reply to Szilard Lovas

Expert 1425 points

Just a short check, did try to disable cache?

0 Jason Pitteman over 9 years ago in reply to Szilard Lovas

Prodigy 190 points

Hi Szilard,
Thanks for your reply, I have not yet tried to disable cache. How can I do that?
Thanks in advance, Jason

0 Szilard Lovas over 9 years ago in reply to Jason Pitteman

Expert 1425 points

Hi Jason,

On R5-MPU-PMU subtab look for Enable Cache checkbox.

Regards: Szilárd

0 Jason Pitteman over 9 years ago in reply to Szilard Lovas

Prodigy 190 points

Hello Szilard,
Cache is now enabled, I will disable it and test if the ethernet interface is working.
Thanks

0 Anthony F. Seely over 9 years ago in reply to Jason Pitteman

TI__Guru 68920 points

If cache turns out to be the issue - instead of disabling cache you should change the attribute of the area of L2SRAM where you are storing your data buffers for EMAC to be 'write through' cache. That way as soon as you write the data it will be written to the L2RAM directly where the emac can then pick up the data for transmission. But you still get the performance gain of the instruction cache and data cache.

Arm-based microcontrollers

Arm-based microcontrollers forum

Hercules LwIP ethernet