Asset Tracker v2, using I2C instead of LEDs with UI module

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

Hakon — Thu, 05 Sep 2024 16:02:45 GMT

[quote user="Sakari S"]Would creating an event or module etc. that would execute this be a more 'correct' way?[/quote]

Creating a module would probably be the way to go then. Then in the event handler of that module you would perform the actions on the I2C based on the event received. You can take a look at this for reference https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/libraries/others/app_event_manager.html#code_example .

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

zachary_z — Fri, 23 Aug 2024 07:55:06 GMT

I am still lost on this. I was looking into other ways to do this and read about the Application Event Manager. To rephrase my problem, my goal is to perform an action on an I2C device depending on what the chip is doing within the Asset Tracker program. Would creating an event or module etc. that would execute this be a more 'correct' way?

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

Hakon — Fri, 02 Aug 2024 11:23:10 GMT

[quote user="Sakari S"]Do you have any recommendations on where to start modifying the code to either bypass the high level APIs[/quote]

If you want to "bypass the high level API" you can just set the GPIO pins directly, which is what is done in the sample I provided. But you said that the LED driver uses I2C to access the LEDs, which means you probably need to write your own functions for communicating with the LEDs.

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

JONATHAN LL — Thu, 18 Jul 2024 12:49:44 GMT

Håkon will be back next week, pardon the delay, summer vacation in Norway.

Regards,
Jonathan

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

zachary_z — Wed, 10 Jul 2024 12:25:09 GMT

Do you have any recommendations on where to start modifying the code to either bypass the high level APIs or on how to make the I2C compatible with this API?

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

Hakon — Mon, 10 Jun 2024 15:22:51 GMT

[quote user="Sakari S"]For example, I cannot find any instance of gpio_pin_configure_dt being called in Asset Tracker.[/quote]

That's most probably because Asset Tracker is using a more high level API to access the LEDs. This sample uses a more low level approach and accesses the LEDs directly.

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

zachary_z — Thu, 06 Jun 2024 14:01:48 GMT

This example is familiar to me. My problem is that I cannot find the piece of code that uses any of these functions from the Asset Tracker's code. For example, I cannot find any instance of gpio_pin_configure_dt being called in Asset Tracker.

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

Hakon — Thu, 06 Jun 2024 13:14:01 GMT

Have you looked at this sample? https://github.com/nrfconnect/sdk-zephyr/blob/main/samples/basic/blinky/src/main.c

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

zachary_z — Thu, 30 May 2024 08:02:02 GMT

I'm currently having difficulty figuring out what functions actually control the LEDs, for example the actual functions that drive the GPIO pins. My idea was to just modify these. Any tips on where to start?

RE: Asset Tracker v2, using I2C instead of LEDs with UI module

Hakon — Wed, 24 Apr 2024 13:54:40 GMT

Hello,

if you have a LED driver that uses I2C then of course you need to use I2C to communicate with it and not GPIO.

[quote user=""]Is there a simple way to program this or would it be much more time-consuming?[/quote]

I don't know. What type of LED driver is it? Do you have a data sheet for it? I can't imagine it being a hard task.