Timer/Counter configuration issues

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 22:52:15 GMT

Whats also puzzling is that upon debugging I can see that I am writing 800,000 dec to CC[1] which is 0xC3500 yet the register only gets 0x03500 which is indicative of TIMER_BIT_WIDTH being set to 16-bits but it is clearly configured to 32-bits.

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 22:46:32 GMT

I'm using Keil uVision. Thats likely bc the your directories are set up differently.

Also, NRFX_TIMER_DEFAULT_CONFIG_BIT_WIDTH? I don't see that #define anywhere in my Project. I have TIMER_DEFAULT_CONFIG_BIT_WIDTH and thats set to 3 in sdk_config.h

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 22:20:46 GMT

What SDK version are you using?

my value for NRFX_TIMER_DEFAULT_CONFIG_BIT_WIDTH is 0, which corresponds to 16 bit timer widths.

I don't know what the problem could be.

Jørgen Holmefjord Do you have any ideas on this?

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 22:14:26 GMT

nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG; already configures the bit width to 32-bits as this is the default configuration but I treid it anyway. Still no dice.

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 19:53:36 GMT

nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG;
timer_cfg.bit_width = NRF_TIMER_BIT_WIDTH_32;

put this in, then try it.

If the toggle time changes you'll have to do something similar to what was attempted in the timer handler with the kickout variable.

I was grabbing at straws which weren't even there in that last message.

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 19:45:11 GMT

How so? All I am doing is toggling a pin to verify how often the interrupt handler fires. With uint32_t time_ms = 50; //Time(in miliseconds) I should see pulse widths of 50ms not 4ms. Am I missing something? The interrupt handler words, just doesn't fire at the configured rate.

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 19:42:30 GMT

LINE 737 in Main,

Comment that out, and uncomment the same function inside the if statement, then reset the kickout value to 750, this should fix your problem.

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 19:26:28 GMT

Here we go: www.dropbox.com/.../ble_peripheral_test.rar

My implementation will be under \pca10028\s130\arm5_no_packs\ble_app_uart_pca10028_s130.uvprojx

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 19:24:10 GMT

I just meant your timer setup code, but you could upload it to dropbox and post a link, I guess.

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 19:21:36 GMT

Yes, is there a way I can post my zipped up project folder on this forum?

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 19:02:52 GMT

Could you post your code?

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 18:49:41 GMT

Negative, I have changed the second argument of the extended capture compare to point to CC[1]

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 16:19:17 GMT

Are you still checking CC[0]?

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 16:15:57 GMT

Yes, all 0's are 1's with Timer 1 enabled in the sdk_config.h file and still seeing the same erroneous result.

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 16:13:39 GMT

If you were to change all your code and replace the 0's with 1's where channels, timers, and counters are concerned I believe your code would work fine.

Assuming you have channel 1 enabled in the SDK config.h included in your project.

RE: Timer/Counter configuration issues

exgreyfox — Mon, 01 Oct 2018 15:07:41 GMT

I see. At this point, I cant see a path forward with this and it seems to be the same for you guys. I'm not sure if this is a bug in the silicon or a bug in the Nordic HAL driver layer but I have a Timer Counter I am configuring to bang away at 50ms and its doing so at 4ms. All this does is change the constant which dictates how many clock timer/counter interrupt handler firings to count for a while loop bailout that I am using so it should be ok. My only concern is if this discrepancy is indicative of some other more egregious bug.

RE: Timer/Counter configuration issues

tommy.lane — Mon, 01 Oct 2018 04:08:22 GMT

I'm not 100% sure on this as I haven't read every shred of the docs on this topic, however I have used the extended compare in the past. It's my understanding that the second parameter of the extended compare is the constant which indicates the physical timer channel to monitor for a true compare event.

RE: Timer/Counter configuration issues

exgreyfox — Wed, 26 Sep 2018 19:38:00 GMT

I am using Timer Counter 1 not 0. I was under the impression that the CC[n] register specifies capture compare value and you can have multiple compare registers per a single timer instantiation. In other words, CC[0] has nothing to do with Timer Counter 0. Or am I wrong and I misinterpreted the reference manual?

RE: Timer/Counter configuration issues

tommy.lane — Wed, 26 Sep 2018 19:29:52 GMT

Okay, perhaps the previous comments have been unclear.

You CAN NOT use timer 0 in any way whatsoever and expect the softdevice (blue tooth) to work.

you will have to change every single instance of 0 to 1, or something else depending on what other services are running.

RE: Timer/Counter configuration issues

exgreyfox — Wed, 26 Sep 2018 19:25:51 GMT

I am using channel 0

RE: Timer/Counter configuration issues

exgreyfox — Wed, 26 Sep 2018 15:51:05 GMT

haakonsh BITMODE register is set to 32-bits. Are there any other registers you would like me to verify? This is very puzzling, I don't understand why this isn't working. All of the configurations look properly set.

RE: Timer/Counter configuration issues

tommy.lane — Wed, 26 Sep 2018 13:48:07 GMT

nrf_drv_timer_extended_compare(&TIMER, NRF_TIMER_CC_CHANNEL0, time_ticks, NRF_TIMER_SHORT_COMPARE1_CLEAR_MASK, true);

nrf_drv_timer_extended_compare(&TIMER, NRF_TIMER_CC_CHANNELX, time_ticks, NRF_TIMER_SHORT_COMPARE1_CLEAR_MASK, true);

Change channel to proper channel (replace X with proper timer channel)

RE: Timer/Counter configuration issues

haakonsh — Wed, 26 Sep 2018 09:22:41 GMT

Yeah, I think the timer is configured for 16-bit only. What's the value of the BITMODE register?

RE: Timer/Counter configuration issues

exgreyfox — Tue, 25 Sep 2018 18:58:07 GMT

haakonsh I just took a look at the value of register CC[0] and as I stepped through the code while debugging, after executing the line

nrf_drv_timer_extended_compare(&TIMER, NRF_TIMER_CC_CHANNEL0, time_ticks, NRF_TIMER_SHORT_COMPARE1_CLEAR_MASK, true);

CC[0] appears to contain the value 0x00003500 which is 13,568 dec. So I guess this is the discrepancy that we are seeing here. I see that time_ticks equates to 800,000 and is being passed as the cc_value argument to be written to register CC[0]. 800,000 dec = 0xC3500 in hex and what is actually making it into CC[0] is 0x3500. Somehow the 0xC0000 is being dropped. I tried simply forcing the value of CC[0] with the following code:

NRF_TIMER_Type * p_reg;
p_reg->CC[0] = 0xC3500;
nrf_drv_timer_enable(&TIMER);

But I end up in the Hard fault Handler.

Any ideas?

RE: Timer/Counter configuration issues

exgreyfox — Fri, 21 Sep 2018 14:21:18 GMT

Yes I am using SoftDevice. I have made sure to switch to Timer 1 per your earlier instructions. I will get the value of CC[0] and get back to you.