How to solve twi "NRF_ERROR_INTERNAL"?

RE: How to solve twi "NRF_ERROR_INTERNAL"?

Mitch996 — Mon, 25 Dec 2017 01:53:46 GMT

Wow really? I've never thought of it as that... I mean what I encountered, if it were the fault of the driver's code, isn't it too glaring? There's no way nobody found out about this before me??

Also, does S130 which comes with the sdk 12.x enable cccd with "write" or "write request"? My Android device does not support write request, at all.

RE: How to solve twi "NRF_ERROR_INTERNAL"?

Jørgen Holmefjord — Fri, 22 Dec 2017 11:47:32 GMT

It seems that the driver have been rewritten for SDK 11. In general, I would recommend using the latest SDK version, as there is always bugfixes in new releases. As you notised, there is no support for s110 softdevice in SDK 11 or above. You could also try to port the TWI HAL/driver from SDK 12.3 to your SDK version.

RE: How to solve twi "NRF_ERROR_INTERNAL"?

Mitch996 — Thu, 21 Dec 2017 03:04:36 GMT

I'm using SDK 11, S110 softdevice.

Would you suggest I switch to something newer, because, I hate to hypothesize, the newer SDKs solved such problems???

And yes I'm working in blocking mode... more details here in this question.

Edit: my mistake it's not sdk11, but sdk10, where the last s110 device is still available.

RE: How to solve twi "NRF_ERROR_INTERNAL"?

Jørgen Holmefjord — Fri, 15 Dec 2017 10:15:17 GMT

What SDK version are you using? I cannot find this implementation of twi_transfer() in the TWI driver. I'm not sure what you mean by no event handler, typically this will mean that the driver operate in blocking mode. In general, non-blocking mode is recommended to allow the CPU to sleep and save power, but blocking mode should work just as fine.