RE: NRF3540: Duty cycle accuracy

trink — Wed, 30 Apr 2025 18:25:35 GMT

I believe this ticket can be marked as resolved! I was able to find a different example in zephyr that fixed my issue. For others who may be experiencing a similar issue, the solution I found had to do with how the clock was being controlled. I found this solution to be my fix, but if you search for various parts of this solution through the zephyr library, you can find other examples.

static int err;
static int res;
static struct onoff_manager *clk_mgr;
static struct onoff_client clk_cli;

static void clock_init(void)
{

 clk_mgr = z_nrf_clock_control_get_onoff(CLOCK_CONTROL_NRF_SUBSYS_HF);
 if (!clk_mgr) {
 printk("Unable to get the Clock manager\n");
 return;
 }

 sys_notify_init_spinwait(&clk_cli.notify);

 err = onoff_request(clk_mgr, &clk_cli);
 if (err < 0) {
 printk("Clock request failed: %d\n", err);
 return;
 }

 do {
 err = sys_notify_fetch_result(&clk_cli.notify, &res);
 if (!err && res) {
 printk("Clock could not be started: %d\n", res);
 return;
 }
 } while (err);

 printk("Clock has started\n");
}

RE: NRF3540: Duty cycle accuracy

trink — Tue, 29 Apr 2025 17:00:15 GMT

Up to 50.07%*