Full assembly listing in written to outdir/zephyr.lst. Having the address of instruction that trigger the fault, try looking it up in the listing and see if there's something obviously wrong. The

I'd encourage you to file a JIRA/bug so that we can track this and get someone looking at it.

Hi all, I am trying to use the PWM output on the K64 board. I have taken the sample/drivers/pwm_dw/src/main.c and modified it to use the CONFIG_PWM_K64_FTM_0_DEV_NAME and removed the CONFIG_PWM_DW=y

Hi Daniel, thanks for your feedback! See some comments inline: Quoting Dan Kalowsky (2016-03-21 14:10:43) Patch sent to gerrit. Fine by me. Patch sent to gerrit. There is no dependency so it can be

[Rev 1.2 - Added a parameter to .suspend() and .resume() functions indicating the power policy used by the PMA. This parameter will help driver take policy based optimized actions. Described in detail

Hi, trying the webmail reply for a first time. Be gentle. +1 +1 I would argue this should step 1. This can be and should be merged in before the close of the release window this week. So get

From: Simon Desfarges <simon.desfarges(a)intel.com> ASSERT are put each time the timer0 limit register or the timer0 count register is modified. Change-Id:

From: Simon Desfarges <simon.desfarges(a)intel.com> When exiting from tickless idle uppon an external IRQ, the TICK timer is set to fire at next TICK boundary. The current algorithm can lead to a

From: Simon Desfarges <simon.desfarges(a)intel.com> The timer counts from 0 to programmed_limit included. Change-Id: Ifc8585210c319f5452fafc911d4f6d72c4b91eaa Tracked-On:

Hi, quite well, with your patch, I got the output! Now I'm wondering how I can manually set the pins to FUNC_GPIO = K64_PINMUX_ALT_1 = (0x1 << 8). If I write something like #include

Got it working using minicom and no flowcontrol...

Hi Maureen and Idups I got UART output (printf) working using minicom. Don't know what the difference between screen and minicom is but using minicom I set it to not use flowcontrol 115200 8N1 and it

(Revised and incorporated feedbacks. The term "Tickless Idle" was found confusing to be used to refer to a PM policy. That is a specific term used for an optimized kernel idling mechanism saving

[Revised incorporating feedbacks. The changes are shown at the end] Problem Statement: Not all Zephyr kernel drivers provide the same interfaces. Why this is a

[Revised incorporating feedbacks so far] Problem Statement: Power management Kconfig flags are not consistent and hierarchy is not clear Why this is a problem: ----------------------------- The

Hi, I have posted version 13 of the patchset. As usual the series is avaialable in my github repo https://github.com/bboozzoo/zephyr/ in branch

Hello, Thanks for the answer, I will review my copy. BTW, the same test bench shows no jitter in the Quark TICK. So I would like to have the same behavior for ARC. Do you think it is achievable ? I

See [Peter]

Hi Simon, The macro _sys_clock_tick_announce() call _nano_sys_clock_tick_announce(_sys_idle_elapsed_ticks), so _sys_idle_elapsed_ticks might off, can you check the value of _sys_idle_elapsed_ticks

From: Simon Desfarges <simon.desfarges(a)intel.com> ASSERT are put each time the timer0 limit register or the timer0 count register is modified. Change-Id: