PDM hardware exception

RE: PDM hardware exception

octvargas — Tue, 20 Aug 2019 14:38:23 GMT

Thanks Håkon,

I no longer get a hardware exception.

I'm sure I'll continue having questions about PDM, but for now I'll close this ticket.

Thanks again!

RE: PDM hardware exception

Håkon Alseth — Tue, 20 Aug 2019 13:24:26 GMT

In main.c. Sorry, should have been more clear on that 🙂

Let me know how it goes.

Kind regards,

Håkon

RE: PDM hardware exception

octvargas — Tue, 20 Aug 2019 13:18:58 GMT

Hi Håkon,

Maybe a dumb question but here it goes, where/what file am I supposed to add those lines to?

Thanks

RE: PDM hardware exception

Håkon Alseth — Tue, 20 Aug 2019 07:33:29 GMT

Hi,

Sorry for not seeing this before. The interrupt handler must be declared within the OSes options.

If you add these lines, the program should run:

ISR_DIRECT_DECLARE(pdm_isr_handler)
{
	nrfx_pdm_irq_handler();
	ISR_DIRECT_PM(); /* PM done after servicing interrupt for best latency
			  */

	return 1; /* We should check if scheduling decision should be made */
}

void main(void)
{
	IRQ_DIRECT_CONNECT(PDM_IRQn, 0,
			   pdm_isr_handler, 0);
	/* Rest of main */

I'll add these observations to the internal task.

[quote user=""]P.S. Also, the datasheet seems to indicate that the nrfx_pdm_stop command is automatically carried out when the buffer is full, is that correct? [/quote]

When the buffer end is reached (either reading or writing), it will give the event EVENTS_END. You can abort the process by sending the TASKS_STOP, which will finish the ongoing transfer transaction, then send the END event to the application.

Kind regards,

Håkon