Nucleo F767ZI + lwIP+ Cube MX issues

[Di Ci]

Posted on September 29, 2017 at 16:45

Hi all,

i'm a new nucleo user and I start to play with the F767ZI. I will usethe nucleo for send periodical http get request to a remote server, but till now i have some issues with the tools. I configure cube enabling ethernet (mii) and lwIP library.

I configure on cube static ip and all network parameters, enable ICMP request and then put MX_LWIP_Process() in while loop. However i can't ping the board from pc and wireshark doesn't see anything.

All the examples provided by the repository are made without cube and try to export that examples is hard for me. Anyone could help me? For the first step i'm happy if i can ping the board from the pc.

Thanks in advance

Davide

Note: this post was migrated and contained many threaded conversations, some content may be missing.

[Christopher Pappas]

Posted on September 29, 2017 at 17:39

I don't know what version of Nucleo board you are using, but I have two early rev boardswhere the entire ethernet interfaceworks very intermittently.

Check

https://community.st.com/0D50X00009XkgfISAR

out to see if your board is experiencing the same issue.

[Imen.D]

Posted on September 29, 2017 at 17:45

Hi,

Have a look to the errata sheet related to the STM32F767 devices, in the Ethernet peripheral limitationssection

to check if you have the same conditions.

T

here was an Ethernetlimitation

on STM32F767 devices revision A ,

using RMII and it was fixed in Revision Z, but

is not present in the MII mode

(see

/external-link.jspa?url=http%3A%2F%2Fwww.st.com%2Fcontent%2Fccc%2Fresource%2Ftechnical%2Fdocument%2Ferrata_sheet%2Fgroup0%2F23%2Fa6%2F11%2F0b%2F30%2F24%2F46%2Fa5%2FDM00257543%2Ffiles%2FDM002575pdf%2Fjcr%3Acontent%2Ftranslations%2Fen.DM002575pdf

for more details).

If you aren't in the same conditions as the errata sheet, you need to do farther investigation on your case and

I suggest you to debug,identify what is the problem that you see and when it occurs.

Then, you can share your code if this issue is not resolved.

Kind Regards

Imen

[respected]

Posted on October 01, 2017 at 21:17

I have same problem. I created new project with stm32F767ZI-Nucleo.  My project  tcp client but it works sometimes it doesn't work sometimes.  When i press reset button  if blink only orange led  it works after that again press button two leds blink and it doesn't work. 

https://drive.google.com/open?id=0B7UkCR4KRZoJZUl2WFd4MUJYOXc

 

[respected]

Posted on October 08, 2017 at 21:47

maybe it has ethernetif file problem. Because ethernet settings are there.

HAJJEM.Oussema

;

could you please examine my project?

[Oussema Hajjem_O]

Posted on October 09, 2017 at 11:32

Hello,

I updated your project (in the attached zip file) to useRMII interface and the correct ETH PHY device,

I hope this will help you

Best regards,

Oussema

________________

Attachments :

lwIP Test.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HyO8&d=%2Fa%2F0X0000000b6v%2FKhoCnxVfh9jazIQeyxVZepfNMhRotgJTYfTfK0iSJvo&asPdf=false

[respected]

Posted on October 09, 2017 at 13:25

Thanks for your helping. But this is not my problem. I configured stm32f7xx_hal_conf.h file. Now rj45 leds are blinking ( green and orange) and it works generaly. I think it has only time problem now. Because tcp sending delayed. 

If i can fix , i will share codes

[Di Ci]

Posted on October 09, 2017 at 15:41

Hi

ASIK.Mehmet

‌, could you please share your changes? They will bevery useful for me. Thanks!

[Matthew Staben]

Posted on October 12, 2017 at 20:34

I currently have a Nucleo-144 767ZI board walking/talking ethernet using the LWIP libraries.  I use Crossworks to develop with.

A couple of hints:

1. Set your PHY address to 0.

2. Set up your RAM placement so the Ethernet buffers are at the top.  In my Crossworks flash placement file, I do it like the below.  If I move the DecriptSection [sic] and arraySections to be below the other sections, the farther I push it, the worse my ethernet performance.  These four sections, including the everlasting spelling error, are instantiated in ethernetif.c.

<MemorySegment name='$(RAM_NAME:RAM);SRAM'>

<ProgramSection alignment='0x100' load='No' name='.vectors_ram' start='$(RAM_START:$(SRAM_START:))' />

<ProgramSection alignment='4' load='No' name='.RxDecripSection' />\

<ProgramSection alignment='4' load='No' name='.TxDescripSection' />\

<ProgramSection alignment='4' load='No' name='.RxarraySection' />\

<ProgramSection alignment='4' load='No' name='.TxarraySection' />\

<ProgramSection alignment='4' load='No' name='.fast_run' />

<ProgramSection alignment='4' load='No' name='.data_run' />

<ProgramSection alignment='4' load='No' name='.tdata_run' />

<ProgramSection alignment='4' load='No' name='.bss' />

<ProgramSection alignment='4' load='No' name='.tbss' />

<ProgramSection alignment='4' load='No' name='.non_init' />

<ProgramSection alignment='4' size='__HEAPSIZE__' load='No' name='.heap' />

<ProgramSection alignment='8' size='__STACKSIZE__' load='No' name='.stack' />

<ProgramSection alignment='8' size='__STACKSIZE_PROCESS__' load='No' name='.stack_process' />

</MemorySegment>

[Morgan.Doug]

Posted on November 01, 2017 at 16:13

I was also having major problems with the raw api working sporadically.    Changing the external PHY parameters in the HAL_Conf file as mentioned above seemed to fix my problems.  Note that this is with the 'Z' silicon version.   Is there some place that has an errata for Cube or the Nucleo boards?   I could have saved oodles of time if the answer was easier to find.

Thanks!