SDK17 TWI (i2C) problem

RE: SDK17 TWI (i2C) problem

Karl Ylvisaker — Thu, 23 Sep 2021 13:01:05 GMT

[quote user="Enrico"]ok, i will go back on NCS SDK, and i think that i will stay there.[/quote]

I think this is a great choice - the nRF Connect SDK has production support for the nRF52 series already, so there should be no problem using it as it is currently.
As an added bonus to the nRF Connect SDK we just launched the Visual Studio Extension pack too, so you may use Visual Studio code for your development! :)

[quote user="Enrico"]NCS powering on is 0.5 seconds slower than NRFSDK power on. So doesn't matter it is just a consideration.[/quote]

That is strange, 0.5 seconds is quite a lot when it comes to extra time powering up. I will make a note of this and have a look to see if I can replicate it on my end as well.
Thanks for the headsup!

Please do not hesitate to open another ticket if you should encounter any issues or questions in the future.

Good luck with your development!

Best regards,
Karl

RE: SDK17 TWI (i2C) problem

Epasta — Thu, 23 Sep 2021 12:34:56 GMT

Hello Karl,

ok, i will go back on NCS SDK, and i think that i will stay there.

What I saw is that:
NCS powering on is 0.5 seconds slower than NRFSDK power on. So doesn't matter it is just a consideration.

Thanks again
Best regards

RE: SDK17 TWI (i2C) problem

Karl Ylvisaker — Thu, 23 Sep 2021 11:53:59 GMT

[quote user="Enrico"]thanks for your time and the reply.[/quote]

No problem at all, I am happy to help! :)

[quote user="Enrico"]- i read that nrf5 sdk is more stable. Is this not true?[/quote][quote user="Enrico"]Do you suggest to me to continue with NCS SDK?[/quote]

I recommend that you read through the blogpost I referenced about this before you make your decision, but to summarize; the nRF5 is our most mature SDK, having existed for a decade already. The nRF5 SDK is currently going into maintenance mode, meaning that it will no longer receive any new features, only bugfixes and security patches. The nRF Connect SDK is our new SDK, which we are actively developing and adding new features to. All coming BLE features will be added to the NCS SDK. The NCS SDK is also RTOS based (Zephyr) which is a great advantage of it as well.
So, while the nRF5 SDK is the 'tried and true' SDK - and a good choice still - it will not feature anything that is not in it already, so new developments that wish to be able to make use of all the new BLE features and improvements should develop with the NCS SDK.

Personally, I would recommend that all new developments happens on the NCS SDK.

[quote user="Enrico"]I saw also that on powering on, NRFSDK is faster than NCS[/quote]

Could you elaborate on this? To my knowledge the SoC will have approximately equal startup time when used with either SDK.

Best regards,
Karl

RE: SDK17 TWI (i2C) problem

Epasta — Thu, 23 Sep 2021 11:39:59 GMT

Hello,

thanks for your time and the reply.
- No i do not have any errors during runtime.

"If I may ask, why are you moving from a Zephyr project onto using the nRF5 SDK?"
- i read that nrf5 sdk is more stable. Is this not true? I saw also that on powering on, NRFSDK is faster than NCS

Do you suggest to me to continue with NCS SDK? If yes I stop develop on NRF5 SDK and I will continue on NCS SDK

Thanks again for your time
Best regards

RE: SDK17 TWI (i2C) problem

Karl Ylvisaker — Thu, 23 Sep 2021 11:12:53 GMT

Hello,

Are you seeing any errors on runtime when you run your nRF5 SDK code?
Could you show me exactly what you log says when you run this function?
Do you have access to a logic analyzer? It would be very helpful to see what is happening on the lines here.

For future reference I recommend that you make use of the TWIM driver directly if this is a new development. With the TWIM driver you should call nrfx_twim_xfer with a TXRX descriptor to first do a TX and then an RX.

[quote user=""]But I can't have the same result with SDK17.[/quote][quote user=""]I have implemented TWI with zephyr i do not have any problem, it works perfectly.[/quote]

If I may ask, why are you moving from a Zephyr project onto using the nRF5 SDK?
As detailed in this blogpost we recommend that all new development now happens on the NCS SDK instead.

Best regards,
Karl