• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 469 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.

Starterware 02.00.00.07 LWIP 1.4 issue when Ethernet Boot Mode

Christian Lambricht
Prodigy 110 points

Hello,

On the new Starterware version there is an issue when you attempt to boot your application (using LWIP 1.4) from Ethernet. (beaglebone)

After some investigation, the code freeze at CPSWCPDMATxIntEnable().... Interrupt issue due to the ROM Ethernet code executed before. (supposition)...

The solution I propose is to add CPSWCPDMAReset(cpswinst->cpdma_base) line 931 of cpwif.c.

Is it possible to look at this and tell me if I'm right and if there is a possible side effect?

Best regards,

Christian

  • 0
    TI__Intellectual 1480 points

    Hi,

    Is this case observed with bootloader or application?

    Kindly provide the steps followed at your end, so as to get clear picture of root cause.

    Thanking you,

    Ramesh D

     

  • 0 in reply to Ramesh Dandamudi
    Prodigy 110 points

    What I had before starting some experimentation of ethernet boot.

    The bootloader provided in starterware 02.00.00.06 (MLO with texas header)

    An application using starterware 02.00.00.07 (LWIP 1.4) (App with texas header)

    Both executed from an SD card.

    Beaglebone configured in a mode that never boot from Ethernet

    ==> Everything is OK

    When I put the beaglebone into a mode that allow the Ethernet boot, the application (not the bootloader) freeze at CPSWCPDMATxIntEnable().

    It seems that the ROM code initialize something in the Ethernet and that there is no correct reset in the LWIP code to reinit the Ethernet code....

    If you have a look at the demoPwrMgmnt.c example, you will see that there is a CPSWCPDMAReset after some other reset .... It is why I applied this on the LWIP code and it working know :) But I don't know if it is normal or not :)

    Best regards,

    Christian

  • 0 in reply to Christian Lambricht
    TI__Intellectual 1480 points

    Hi,

    It looks that your bootloader doesnot use CPSW and in application CPDMA is not reset during initilization of CPSW. So, your analysis looks to be perfect. The modifictions suggested are correct and will not have any side effects.

    Thanks for your valuable  time and inputs,

    Regards,

    Ramesh D