Zephyr Devs, I am working on the project that requires a number of floating point operations to take place on the ARC core in the Intel Quark SE microcontroller. As such, it would be great to fully ut

Hello, I am working off of Zephyr 1.5 in the nanokernel configuration on a custom Intel Curie board. We have a number of fibers running on both cores, but seem to be having trouble with fibers on the

I do have CONFIG_ARC_STACK_CHECKING enabled as well have examined the _nanokernel and all the struct tcs's for each fiber (I did have a stack overflow on x86 before and noticed that the struct tcs for

Ben, Just to update you and the mailing list; I think the issue is one you solved for 1.6. However, its not tracked on JIRA or in the release notes so I didn't realize such a critical bug was not fixe

Zephyr Devs, Weve started moving our project from Zephyr 1.5 to Zephyr 1.7. One big change (aside from the really big ones like unified kernel and all that) is that the APIs for timers and others seem

While Im not sure Im 100% convinced, having negative numbers just be the number in ticks as it was in the old API should be fine. Im curious though why you went for ns when most system wouldn't be abl

You can, just be aware that there isn't any builtin mutual exclusion between the x86 and ARC cores in the OS, so if both cores are trying to access the same SPI controller, there will likely be concur

Jun, You can use CONFIG_STACK_USAGE to have the build system generate the .su files which summarize the stack usage (if computable at compile time) of all the functions in all the files. You can use t

Max, If your library has a name other than libxxxx.a, you can still you the ALL_LIBS and LDFLAGS_zephyr as they are used in samples/application_development/static_lib/hello_world/Makefile in order to

Jie, Curie boards generally flash in one of two ways: over JTAG or over USB. In typical uses, they actually flash over the Curie USB interface (using the USB DFU protocol; via dfu-util). That’s why yo

Jie, If you flashed your Zephyr application over USB, it should now be in the device’s flash memory and should be loaded and run on every reboot. If you are not seeing the application load when you ru

Jun, I don’t see much other way unfortunately; I think it would be nice is Zephyr added Fault hooks per thread so you could set a function to be called on a thread faulting. Otherwise, you can always

Jun, As we discussed, you can use the following to do what you have below in the new cmake system: set(CONF_FILE “defconfig_1”) list(APPEND CONF_FILE “defconfig_2”) list(APPEND CONF_FILE “defconfig_3”

Sebastian, As the line I suggested changing just does a replace of space with semicolon, either "a b c" or "a;b;c" should work (and any combo should work too, like "a b;c". The reason I suggest we loo

Hey, In Zephyr’s devicetree, there are two separate concepts when it comes to naming a node with a unique name: label property and node label. Is there a design reason why these two have been kept sep

I havent done it yet sorry; I was hoping to get a better understanding of the reason they are separate before going with one solution (just make node label available as a string separately or change i