If your purpose is to see the message prints, you do not need the USB stuff. Message printing on arc will be routed to the same uart port as x86. No extra thing is needed. I strongly suggest you to

Re-send with updated email address for Bogdan...

On 29 November 2016 at 21:54, Davidoaia, Bogdan M <bogdan.m.davidoaia(a)intel.com> wrote: Hi Bodan, > If we want to define specific value types for each channel type, then we might as well have the

Right, USB device functionality in general is supported only on the x86 side of C1000, consequently USB UART is only available there and not on the ARC side. Thanks Sent: Tuesday, January 3, 2017

Hi all, I have a few questions/discussion points related to the new networking stack in context of Ethernet driver development. 1. Currently Ethernet drivers are by default initialized before the

Tidy(chunhua) Jiang <tidyjiang(a)163.com> wrote (on Tuesday, January 03, 2017 10:59PM): Zephyr doesn't really have a facility for device-specific modifications to linker scripts at the moment. The

NEW JIRA items within last 24 hours: 6 [ZEP-1505] extend sanitycheck to support ARC simulator https://jira.zephyrproject.org/browse/ZEP-1505 [ZEP-1511] Add Support for Multiple Simultaneous

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/9608 : [DO NOT MERGE] doc: move documetnation context to root directory - https://gerrit.zephyrproject.org/r/9639 : doc: support

Hello, I'm porting zephyr to TI's CC2538 device family, but there is a special user case —— customer configuration area(CCA/CCFG). CCA is placed in the uppermost flash page, so the linker

Hi Both As you said I have tried to compile directly using arc and its compiling I thought to route the debug prints through UART over usb. But I think the current version supports UART over usb

OR, the ARC can utilize SPI too and talk to the accelerometer directly. It just depends upon which CPU you want to OWN which resource. -Chuck Sent: Tuesday, January 03, 2017 5:09 AM To:

Sorry. Typo. Top of the tree. Sent: Tuesday, January 3, 2017 10:06 AM To: Mahendravarman Rajarao (RBEI/EAA3) <Mahendravarman.Rajarao(a)in.bosch.com>; devel(a)lists.zephyrproject.org Subject: [devel]

Zephyr drivers for SPI and GPIO were updated recently to allow ARC to directly access GPIO including AON_GPIO and SPI. You do not need x86 at all. Please see the updated driver and sample app for

Hello, TCP support is planned for Zephyr 1.7: https://jira.zephyrproject.org/browse/ZEP-791 So it must be ready before the merge window,

NEW JIRA items within last 24 hours: 1 [ZEP-1501] Where to find Auto-PTS source code https://jira.zephyrproject.org/browse/ZEP-1501 UPDATED JIRA items within last 24 hours: 3 [ZEP-810]

how many weeks do you think it will take to have some code available in a development branch - just enough to check MQTT connectivity to a broker?

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/9576 : bluetooth: controller: Split events into normal and priority - https://gerrit.zephyrproject.org/r/9586 : sanitycheck: reduce

Hello, TCP-based sample code will be submitted once TCP is ready. Regards, Flavio

Hi, You can use IPM API to send data from one core to another. See include/ipm.h Your accelerometer implements sensor API I guess? So it can trigger a callback, which in turn would send the

Hi We have connected an Accelerometer to the x86 core of C1000 (Quark_se) through SPI interface. Interrupt line of accelerometer is also connected to the AON_GPIO_3 Now I need to route the SPI