Hi Jinhyuck, Flashing to Arduino 101 with USB cable has been supported by Zephyr 1.4.0 and later versions. It works with the original ROM comes with the Arduino 101. If you already flashed the custom ROM to work with JTAG before, you would need to restore the original ROM.
Here is how to restore the original ROM: https://www.zephyrproject.org/doc/1.3.0/board/arduino_101.html#id5 And here is how to flash .bin file using the USB cable: https://www.zephyrproject.org/doc/1.7.0/boards/x86/arduino_101/doc/board.html#flashing Best regards, Kien From: Jinhyuck Park <jinhyuck83.park at samsung.com> on behalf of Jinhyuck Park <[email protected]> Reply-To: "jinhyuck83.park at samsung.com" <jinhyuck83.park at samsung.com> Date: Friday, April 7, 2017 10:04 To: Kien Dinh <kien.t.dinh at intel.com>, "iotivity-dev at lists.iotivity.org" <iotivity-dev at lists.iotivity.org> Subject: RE: [dev] iotivity-constrained: binding multiple types Dear Dinh I tried to run constrained iotivity sample in arduino101, so I bought arduino board for test but unlike FRDM-k64F board, arduino101 seems more complicated to bring up. I mean after zephyr build of Constrained iotivity(zephyr.bin for arduino101), and want to flash binary to arduino101. I cannot flash bin file directly to arduino101 board through usb cable. it looks arduino101 needs JTAG debugger and special equipments for flash zephyr bin. so my question is, is there any way to flash zephyr.bin(build arduino101) to arduino101 board without JTAG debugger? (in case FRDM-K64F, I could flash zephyr.bin through usb cable without JTAG debugger) Thanks and Best Regards PARK JIN HYUCK Engineer IOT Lab Software Center SAMSUNG ELECTRONICS CO.,LTD Mobile: +82-10-8719-8749 E-mail: jinhyuck83.park at samsung.com --------- Original Message --------- Sender : Dinh, Kien T <kien.t.dinh at intel.com> Date : 2017-04-05 22:21 (GMT+9) Title : [dev] iotivity-constrained: binding multiple types Hi, I?m using iotivity-constrained on an Arduino 101 board and trying to use multiple sensors. I would like to map each sensor to a standard type so that the device can have multiple resource types at the same time. However, so far it seemed that iotivity-constrained only allowed binding to one. I tweaked the ?apps/server_zephyr.c? as following to bind a new temperature type. However, I could only see the first one, which is ?oic.r.light?, when connecting to the device. If the ?oic.r.temperature? comes first, it will appear instead of the ?oic.r.light?. ---- static void register_resources(void) { oc_resource_t *res = oc_new_resource("/a/light", 2, 0); oc_resource_bind_resource_type(res, "oic.r.light"); oc_resource_bind_resource_type(res, "oic.r.temperature"); oc_resource_bind_resource_interface(res, OC_IF_RW); oc_resource_set_default_interface(res, OC_IF_RW); oc_resource_set_discoverable(res, true); oc_resource_set_periodic_observable(res, 1); oc_resource_set_request_handler(res, OC_GET, get_status, NULL); oc_resource_set_request_handler(res, OC_POST, post_status, NULL); oc_resource_set_request_handler(res, OC_PUT, put_status, NULL); oc_add_resource(res); } ---- It seems that the API oc_new_resource() allow multiple types. It uses the second parameter to determine the number. Has this feature already been implemented? If yes, please let me know what I am missing? Thanks Kien _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev [cid:image001.gif at 01D2AF88.3E529BE0] [http://ext.samsung.net/mail/ext/v1/external/status/update?userid=jinhyuck83.park&do=bWFpbElEPTIwMTcwNDA3MDEwNDE0ZXBjbXMxcDE0M2NmZDE1MzExNjdhOWQ2ZmQxMmRjYWIyNGU3YjY4ZSZyZWNpcGllbnRBZGRyZXNzPWtpZW4udC5kaW5oQGludGVsLmNvbQ__] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170407/ee3e36f3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13403 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170407/ee3e36f3/attachment.gif>
