• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 405 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.

LWIP and Halcogen

Martin Beakes
Intellectual 325 points
Other Parts Discussed in Thread: HALCOGEN

Hi, 

I download, install and build the LWIP project for RM48 HDK using the link below and everything works fine. 

However, when I modify the Halcogen project that comes with the LWIP demo to add pin mapping or drivers, the code generates lots of erros when building. 

I'm using Halcogen 4.05.02.  From what I noticed, it seems that the Halcogen LWIP project was also build using 4.05.02.

My idea is to use the LWIP demo code on our custom board to do a proof of concept. I taught that I could simply use the LWIP demo and modify the pin mapping to match our board. However, as soon as I generate the code (even without any change to the provided Halcogen project), the project does not build anymore and provide lot of errors (duplicate, function changes, etc...) 

Should I use another version of Halcogen ? 

processors.wiki.ti.com/.../HALCoGen_Ethernet_Driver_and_lwIP_Integration_Demonstration

  • 0
    TI__Guru 68920 points
    Martin,

    Not sure what to say - you'd need to post the errors so we can understand what they are.
  • 0 in reply to Anthony F. Seely
    Intellectual 325 points

    Hi Anthony, 

    When I simply re-generate the code in Halcogen and build it. I got the following errors: 

    It seems that my version of Halcogen generated code is really different from the code base of the LWIP Demo application.

    Or the LWIP demo code was modified and is no longer compatible with Halcogen. 

  • 0 in reply to Martin Beakes
    TI__Guru 68920 points
    It looks like your project settings may be wrong.

    For a bunch of these, you probably forgot to add the HalCoGen 'include' folder to the include path.
    Doing this will likely fix the errors from mibspi.c, can.c etc

    Try that.

    If there's anything left then that are the 'already declared in current scope' this is probably because you didn't
    exclude some of the sub-folders from the build inside lwIP.

    There's a top level file in the lwIP folder that #include 'C' source files [not header files!]
    It's meant as some sort of configuration file picking which protocols to support and which to keep out of the build.

    But it makes it nasty to build because if you #include the source and also compile the source separately when you link both files you get a duplicate declaration/definition ..

    Look at the example and see how it's got some folders excluded from the build under lwIP .. you'll want to do the same.