You can build posix simulator and launch it on linux. It simulates HW parts such a RF, storage, timer, uart etc. So, you can't run the simulator on HW platforms directly. But the same source can be cross compiled and launched on any HW platform supported by openthread. For this reason the Makefile I've provided in the path shall be adopted to desire platform.
On Thu, Nov 23, 2017 at 10:51 AM, Khaled Elsayed <[email protected]> wrote: > This is a large footprint. EFR should be adequate. > So, is this posix simulator used across platforms? I mean it would run > directly on supported platforms such as EFR or Sam. > On Nov 22, 2017 23:23, "Oleksandr Grytsov" <[email protected]> wrote: > >> openthread has posix simulator. I'm using it for test. >> I have Atmel samr21 modules which have 256k FLASH but the iotivity + >> openthread required about ~320k. >> I plan to use some Silabs EFR32 modules for test on real HW soon. >> >> On Wed, Nov 22, 2017 at 11:45 AM, Khaled Elsayed <[email protected]> >> wrote: >> >>> Interesting. I just saw the announcement on the mailing list of src code >>> availability. Yes, it needs to be submitted on gerrit. >>> I am interested to test it over Zolertia Z1 and similar constrained >>> devices. What platform have you used for testing? >>> >>> Best regards >>> >>> Khaled >>> >>> >>> On Thu, Nov 16, 2017 at 4:14 PM, Oleksandr Grytsov <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Yes, it works. It is not fully tested yet and still under development >>>> but basic flow works with openthread posix build. >>>> openthread dosn't have underlying OS. It has some primitives as >>>> tasklets, timers etc. but actually all >>>> processing is done in the main loop. So far it it enough for >>>> iotivity-constrained. >>>> >>>> I don't consider to add any RTOS. It would be convenient in some cases. >>>> But my target is really constrained devices >>>> and don't have enough resources. >>>> >>>> On Thu, Nov 16, 2017 at 2:42 PM, Khaled Elsayed <[email protected]> >>>> wrote: >>>> >>>>> This is interesting. So, I am just curious you would have iotivity >>>>> running over openthread stack? Doew openthread depend on the underlying >>>>> OS? >>>>> So, is the architecture would be something like this? >>>>> >>>>> ------------------------ >>>>> | Iotivity | >>>>> ----------------------- >>>>> >>>>> ------------------------ >>>>> | open thread | >>>>> ----------------------- >>>>> >>>>> ------------------------ >>>>> | RTOS | >>>>> ----------------------- >>>>> >>>>> >>>>> >>>>> On Tue, Oct 24, 2017 at 8:53 PM, Oleksandr Grytsov <[email protected]> >>>>> wrote: >>>>> >>>>>> Unfortunately I don't have expertise with Contiki (I've mentioned it >>>>>> as example). >>>>>> >>>>>> I'm trying to port iotivity on openthread. >>>>>> >>>>>> BTW If someone is looking or working on iotivity over thread it would >>>>>> be good to collaborate. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Tue, Oct 24, 2017 at 6:38 PM, Maloor, Kishen < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Thanks for pointing this out. The error was introduced >>>>>>> very recently in a different change. It has now been >>>>>>> fixed. >>>>>>> >>>>>>> By the way, the Contiki port hasn’t been tested much, so >>>>>>> if you have expertise with Contiki and requisite hardware >>>>>>> to test, your feedback would be very welcome. >>>>>>> >>>>>>> >>>>>>> - >>>>>>> Kishen Maloor >>>>>>> Intel Open Source Technology Center >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: <[email protected]> on behalf of >>>>>>> Oleksandr >>>>>>> Grytsov <[email protected]> >>>>>>> Date: Tuesday, October 24, 2017 at 7:50 AM >>>>>>> To: "[email protected]" < >>>>>>> [email protected]> >>>>>>> Subject: [dev] iotivity-constrained build failed >>>>>>> >>>>>>> >>>>>>> Hi All, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I was playing with iotivity-constrained for investigating what is >>>>>>> OCF and >>>>>>> found that >>>>>>> >>>>>>> iotivity-constrained build fails for client in case OC_BLOCK_WISE is >>>>>>> not >>>>>>> defined (for example >>>>>>> >>>>>>> >>>>>>> contiki port) with following error message: >>>>>>> >>>>>>> ../../api/oc_ri.c: In function ‘oc_ri_invoke_client_cb’: >>>>>>> ../../api/oc_ri.c:1126:9: error: ‘response_state’ undeclared (first >>>>>>> use in >>>>>>> this function) >>>>>>> response_state = NULL; >>>>>>> >>>>>>> >>>>>>> response_state is input parameter for oc_ri_invoke_client_cb >>>>>>> function only >>>>>>> in case >>>>>>> >>>>>>> >>>>>>> OC_BLOCK_WISE is defined. >>>>>>> >>>>>>> >>>>>>> I was not able to create a bug in the bugzilla due to >>>>>>> iotivity-contrained >>>>>>> project doesn't have >>>>>>> >>>>>>> components defined which is required to create the bug. >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best Regards, >>>>>>> Oleksandr Grytsov. >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Best Regards, >>>>>> Oleksandr Grytsov. >>>>>> >>>>>> _______________________________________________ >>>>>> iotivity-dev mailing list >>>>>> [email protected] >>>>>> https://lists.iotivity.org/mailman/listinfo/iotivity-dev >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Oleksandr Grytsov. >>>> >>> >>> >> >> >> -- >> Best Regards, >> Oleksandr Grytsov. >> > -- Best Regards, Oleksandr Grytsov.
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
