Adrian,

 

You were right about the linker error; I had not renamed the LIBS line…

 

As for the template warning, here is my relevant configuration lines:

 

    router.ethdriver_attributes = "1";

    router.ethdriver_global_endpoint = "router_ep";

    router.ethdriver_mac = [00, 0x0A, 0x35, 0x02, 0xFF, 0x1E];

 

 

 

From: Adrian.Danis@data61.csiro.au [mailto:Adrian.Danis@data61.csiro.au]
Sent: Tuesday, January 17, 2017 10:22 PM
To: Chris Guikema <Chris.Guikema@dornerworks.com>; devel@sel4.systems
Subject: Re: [seL4] CAmkES Templates

 

Hi Chris,

For the 'pbuf_alloc' linker error can you confirm that the component is having 'lwip' added as a LIBS dependency. For example in the camkes-vm in projects/vm/components/UDPServer/UDPServer.mk there is the line
UDPServer_LIBS := sel4camkes ethdrivers lwip sel4vspace
This is what actually causes lwip to be linked into the component, and not just be provided as a build dependency for header staging

With the template error can you confirm that you are provided the attributes for router.ethdriver? For example in apps/cma34cr_singlevm/vm.camkes the connection
connection seL4Ethdriver eth_driver0(from udpserver0.ethdriver, to ethdriver.client)
Has some associated configuration for udpserver0.ethdriver of
        udpserver0.ethdriver_attributes = "1";
        udpserver0.ethdriver_shmem_size = 0x1000;
        udpserver0.ethdriver_global_endpoint = "udpserver0_endpoint";
        udpserver0.ethdriver_mac = [06, 00, 00, 12, 13, 14];

Adrian

On Wed 18-Jan-2017 6:10 AM, Chris Guikema wrote:

Hello,

 

I am working on a CAmkES application attempting to build a seL4 Network Stack. I am basing this on the CAmkES-VM and utilizing UDP Protocol with the lwIP library.

 

During my build process, I get quite a few linking errors like this:

 

undefined reference to `pbuf_alloc'

 

This is odd, because in the templates, the proper header files are being linked in. There are also warnings like this:

 

Warning: no template for ethdriver_1.to.source

 

Even though the connection does exist:

 

connection seL4Ethdriver eth_driver(from router.ethdriver, to ethdriver.client);

 

Is there something obvious I am doing wrong?

 

Thanks

Chris




_______________________________________________
Devel mailing list
Devel@sel4.systems
https://sel4.systems/lists/listinfo/devel