A non-standard Q-SPI communication application

RE: A non-standard Q-SPI communication application

Jørgen Holmefjord — Tue, 04 Jun 2019 14:08:47 GMT

Did you manage to run it without softdevice first? Note that the softdevice will restrict access to the CLOCK peripheral when it is enabled, you will have to use the softdevice API to request HFCLK.

RE: A non-standard Q-SPI communication application

stanley_atc — Tue, 04 Jun 2019 13:58:27 GMT

How can it run with s132? I have tried to implement it in my peripheral initial. Nothing came out.

RE: A non-standard Q-SPI communication application

Jørgen Holmefjord — Tue, 04 Jun 2019 13:19:11 GMT

No, it is not possible to clock out data using this method, only toggle a clock signal. There is no way to get the data directly from RAM to GPIO using this method. An alternative solution could be to use PWM, which support EasyDMA, but we do not have any example code for this.

RE: A non-standard Q-SPI communication application

stanley_atc — Tue, 04 Jun 2019 13:06:59 GMT

Hi,

I checked the post you provided. Is possible I can put the data pins during the toggle edge as data in/out?

RE: A non-standard Q-SPI communication application

stanley_atc — Tue, 04 Jun 2019 01:24:39 GMT

Thanks, I will try.

RE: A non-standard Q-SPI communication application

Jørgen Holmefjord — Mon, 03 Jun 2019 13:38:56 GMT

Hi,

It is possible to toggle a GPIO at up to 8 MHz in nRF52832 using a TIMER, PPI and GPIOTE. See for instance this post.

Best regards,
Jørgen