A few questions about OpENer

[dcl...@humatics.com]

1. Has anyone successfully compiled OpENer for ARM architecture? If so, I'd like to learn how to go about doing this or obstacles you had to overcome.
2. How should one use the sample application? It appears like it is just a collection of functions without a main.
3. Has anyone taken this stack through the ODVA conformance testing? If so, I would like to hear your experiences with this process and if you encountered any issues along the way.

[Alois Zoitl]

On Fri, 2019-02-08 at 07:43 -0800, dcl...@humatics.com wrote:
> Has anyone successfully compiled OpENer for ARM architecture? If so, I'd like to learn how to go about doing this or obstacles you had to overcome.

Yes this has been done. But it strongly depends on your operating system. Are you talking about small systems (e.g., freeRTOS based) or larger (e.g.,
RaspberryPI with linux). The latter is pretty straight forward for the first it strongly depends on your system and general rules are are eard.

> How should one use the sample application? It appears like it is just a collection of functions without a main.

The sample application is definitly a good starting point as it sets up OpENer such that a view assembly objcets and connection targets are available for
testing. The main that brings everything together can be found a directory below. Furthermore the methods of the sample application are needed as they are
called by the stack at the right poitns during start-up and shutdown.

> Has anyone taken this stack through the ODVA conformance testing? If so, I would like to hear your experiences with this process and if you encountered any issues along the way.

I know that products have been gone through conformance testing. AFAIK also successfully.


> --
> You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-open...@googlegroups.com.
> To post to this group, send email to eip-stack-grou...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/0e60bd18-2353-4dbe-89f5-4ba81ec30eaa%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[justin stark]

I will be trying to get it to work on the stm32f7 with freertos + tcp port here in the next few weeks. I can let you know how that goes, but if anyone has any pointers that would be great too.

> To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/a2aa6d32492165f3ab7b1c390aaa7e460d628048.camel%40gmx.at.

[Matthew Prestine]

It should not be difficult to get it working with the STM32 platform.  I have been using it in a professional setting for a few years with great success.  It will cost you about ~2k to get the ODVA lic and id.  My design is based off STM32F4xx or STM32F7xx coupled with FreeRTOS/LWIP.  Industrial network scan times of <1ms can be achieved.  The configurations of FreeRTOS and any network stack can set one back so be prepared to dig your heals in for those as that is were all the work is.

Matt

On Saturday, February 9, 2019 at 5:41:38 PM UTC-6, Justin Stark wrote:

I will be trying to get it to work on the stm32f7 with freertos + tcp port here in the next few weeks. I can let you know how that goes, but if anyone has any pointers that would be great too.

> On Feb 9, 2019, at 2:28 PM, Alois Zoitl <alois...@gmx.at> wrote:
>
>> On Fri, 2019-02-08 at 07:43 -0800, dcl...@humatics.com wrote:
>> Has anyone successfully compiled OpENer for ARM architecture? If so, I'd like to learn how to go about doing this or obstacles you had to overcome.
> Yes this has been done. But it strongly depends on your operating system. Are you talking about small systems (e.g., freeRTOS based) or larger (e.g.,
> RaspberryPI with linux). The latter is pretty straight forward for the first it strongly depends on your system and general rules are are eard.
>
>> How should one use the sample application? It appears like it is just a collection of functions without a main.
> The sample application is definitly a good starting point as it sets up OpENer such that a view assembly objcets and connection targets are available for
> testing. The main that brings everything together can be found a directory below. Furthermore the methods of the sample application are needed as they are
> called by the stack at the right poitns during start-up and shutdown.
>
>> Has anyone taken this stack through the ODVA conformance testing? If so, I would like to hear your experiences with this process and if you encountered any issues along the way.
> I know that products have been gone through conformance testing. AFAIK also successfully.
>
>
>> --
>> You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.

>> To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-opener-users+unsub...@googlegroups.com.

>> To post to this group, send email to eip-stack-grou...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/0e60bd18-2353-4dbe-89f5-4ba81ec30eaa%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-opener-users+unsub...@googlegroups.com.

[dcl...@humatics.com]

Thanks everyone for your responses! This was very helpful. As for the details of my system, I am running Arago Linux on the TI Sitara AM5728. I have successfully been able to run OpENer in an Ubuntu 16.04 docker container on my system, I just have not been able to run it (or compile it for that matter) natively in Arago. I believe however, that this is a problem unique to our setup, mostly due to the fact that we do not have a package manager installed, so I have been trying to figure out how to install all the dependencies without apt which I have been unsuccessful. It is good to know that folks have successfully ported this to ARM without issue, and I think my Docker arrangement works for what I need it for.

[Alois Zoitl]

On Mon, 2019-02-11 at 06:42 -0800, dcl...@humatics.com wrote:
> Thanks everyone for your responses! This was very helpful. As for the details of my system, I am running Arago Linux on the TI Sitara AM5728. I have successfully been able to run OpENer in an Ubuntu 16.04 docker container on my system, I just have not been able to run it (or compile it for that matter) natively in Arago. I believe however, that this is a problem unique to our setup, mostly due to the fact that we do not have a package manager installed, so I have been trying to figure out how to install all the dependencies without apt which I have been unsuccessful. It is good to know that folks have successfully ported this to ARM without issue, and I think my Docker arrangement works for what I need it for.

I strongly recommend that you familiarize yourself with cross-compiling. This will make your live much easier.

>
> On Monday, February 11, 2019 at 9:25:10 AM UTC-5, Matthew Prestine wrote:
> > It should not be difficult to get it working with the STM32 platform. I have been using it in a professional setting for a few years with great success. It will cost you about ~2k to get the ODVA lic and id. My design is based off STM32F4xx or STM32F7xx coupled with FreeRTOS/LWIP. Industrial network scan times of <1ms can be achieved. The configurations of FreeRTOS and any network stack can set one back so be prepared to dig your heals in for those as that is were all the work is.
> >
> > Matt
> >
> >
> >
> >
> > On Saturday, February 9, 2019 at 5:41:38 PM UTC-6, Justin Stark wrote:
> > > I will be trying to get it to work on the stm32f7 with freertos + tcp port here in the next few weeks. I can let you know how that goes, but if anyone has any pointers that would be great too.
> > >
> > > > On Feb 9, 2019, at 2:28 PM, Alois Zoitl <alois...@gmx.at> wrote:
> > > >
> > > >> On Fri, 2019-02-08 at 07:43 -0800, dcl...@humatics.com wrote:
> > > >> Has anyone successfully compiled OpENer for ARM architecture? If so, I'd like to learn how to go about doing this or obstacles you had to overcome.
> > > > Yes this has been done. But it strongly depends on your operating system. Are you talking about small systems (e.g., freeRTOS based) or larger (e.g.,
> > > > RaspberryPI with linux). The latter is pretty straight forward for the first it strongly depends on your system and general rules are are eard.
> > > >
> > > >> How should one use the sample application? It appears like it is just a collection of functions without a main.
> > > > The sample application is definitly a good starting point as it sets up OpENer such that a view assembly objcets and connection targets are available for
> > > > testing. The main that brings everything together can be found a directory below. Furthermore the methods of the sample application are needed as they are
> > > > called by the stack at the right poitns during start-up and shutdown.
> > > >
> > > >> Has anyone taken this stack through the ODVA conformance testing? If so, I would like to hear your experiences with this process and if you encountered any issues along the way.
> > > > I know that products have been gone through conformance testing. AFAIK also successfully.
> > > >
> > > >
> > > >> --
> > > >> You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.

> > > >> To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-open...@googlegroups.com.

> > > >> To post to this group, send email to eip-stack-grou...@googlegroups.com.
> > > >> To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/0e60bd18-2353-4dbe-89f5-4ba81ec30eaa%40googlegroups.com.
> > > >> For more options, visit https://groups.google.com/d/optout.
> > > >
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.

> > > > To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-open...@googlegroups.com.

> > > > To post to this group, send email to eip-stack-grou...@googlegroups.com.
> > > > To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/a2aa6d32492165f3ab7b1c390aaa7e460d628048.camel%40gmx.at.
> > > > For more options, visit https://groups.google.com/d/optout.
>

> --
> You received this message because you are subscribed to the Google Groups "EIP Stack Group OpENer users" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to eip-stack-group-open...@googlegroups.com.

> To post to this group, send email to eip-stack-grou...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/3a354433-3983-4593-a38d-13906bd45016%40googlegroups.com.

[Ok]

I am using a custom board with TI Sitara AM335x and Arago Linux very simillar to BeagleBone EVM. Cross compiling OpENer for ARM (TI) is quite simple:

-  install TI Linux SDK to your Ubuntu PC

- install Cmake

- create a textfile e.g. my_toolchain.cmake with the following content:

set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR arm)
set(CMAKE_C_COMPILER _path_to_cross_compiler_ti_linux_sdk_/arm-linux-gnueabihf-gcc)
set(CMAKE_CXX_COMPILER _path_to_cross_compiler_ti_linux_sdk_/arm-linux-gnueabihf-g++)
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)

- go to OpENer/bin/posix and create a copy of setup_posix.sh e.g. cc_setup_posix.sh

- open cc_setup_posix.sh and extend the cmake call by -DCMAKE_TOOLCHAIN_FILE=_path_to_your_toolchain_file_/my_toolchain.cmake

- invoke cc_setup_posix.sh and you are done.

OpENer works great, but on ARM I am failing in CT-15 testcases "TCP/IP" and "Ethernet Link" right after "get_attributes_all" request. The reply is properly sent, but the very next request is not processed because the connection state is "0".  The connection ID itself matches the ID in the list, but state 3 is expected.

cpf.c line 184:

OPENER_TRACE_ERR(
	"notifyConnectedCPF: connection with given ID could not be found\n");

When re-compiling for x86 and running the code on Ubuntu 16.04 CT-15 is pass.

Best regards,

Oliver

[dcl...@humatics.com]

Thanks Oliver, that was very informative and helpful!